Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    DNS with split tunnelling help

    Scheduled Pinned Locked Moved DHCP and DNS
    2 Posts 1 Posters 119 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • 4
      4o4rh
      last edited by

      My pfsense has 8 interfaces and I desire the dns response should be the interface address
      i.e. 192.168.10.10, 192.168.20.10, 192.168.30.10

      on my desktop, i am using the proton vpn client and i added a script /etc/NetworkManager/dispatcher.d/99-protonvpn-localroute to allow access to the local network and direct the dns to the pfsense interface the connection is on.

      • accessing internet for name or ip works
      • accessing local via ip works
      • accessing local via name e.g. on 30.10 returns the error using curl, connect to 10.10 from 30.55 failed. no route to host.

      why is it seeing the dns as 10.10 instead of 30.10 and how can i fix this

      4 1 Reply Last reply Reply Quote 0
      • 4
        4o4rh @4o4rh
        last edited by

        @4o4rh why doesn't it like match-clients

        server:

        Define views for each interface subnet

        module-config: "iterator"

        LAN clients

        view:
        name: "lan_view"
        match-clients: { 192.168.4.0/24 }
        local-zone: "net.lan" transparent
        local-data: "ipfw.eapenet.lan. 3600 IN A 192.168.4.5"

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.