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

    (SOLVED) Remote DNS not working over IPSec

    Scheduled Pinned Locked Moved DHCP and DNS
    2 Posts 1 Posters 4.9k 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.
    • P
      pvn
      last edited by pvn

      I have a IPSec tunnel between two offices:

      Office A:
      domain: a.mydomain.com
      LAN:    10.0.0.1/16
      
      Office B:
      domain: b.mydomain.com
      LAN:    10.1.0.1/16
      

      The machines in LAN A can ping and access the machines in LAN B and vice-versa by using IP address.

      In office A in DNS Resolver Domain Overrides I have:

      Domain:                   b.mydomain.com
      Lookup Server IP Address: 10.1.0.1
      

      In office B in DNS Resolver Domain Overrides I have:

      Domain:                   a.mydomain.com
      Lookup Server IP Address: 10.0.0.1
      

      The problem: The pfsense DNS server that is remote to the client does not work at all. A machine in LAN A cannot resolve anything in LAN B and vice-versa.

      From a machine in LAN A I can ping the DNS server in LAN B (10.1.0.1) and I can even telnet on port 53. But I cannot use it to resolve anything.
      For example: (The following is executed from a machine in LAN A)

      dig +short pfsense.b.mydomain.com @10.0.0.1 # this fails indicating that the Domain Overrides in the DNS Resolver does not work
      
      dig +short pfsense.b.mydomain.com @10.1.0.1 # this fails indicating that the remote DNS cannot resolve anything
      

      Trying to resolve internet domains using the remote DNS fails as well. The following is executed from a machine in LAN A:

      $ dig +short netgate.com @10.0.0.1 # <- this is LAN A pfsense
      208.123.73.73
      $ dig +short netgate.com @10.1.0.1 # <- this is LAN B pfsense over the IPSec tunnel
      $
      

      Any ideas?

      1 Reply Last reply Reply Quote 0
      • P
        pvn
        last edited by

        Problem solved.

        1. LAN A subnet must be added to DNS Resolver ACL on pfSense B and LAN B must be added to DNS Resolver ACL on pfSense A
          Services -> DNS Resolver -> Access Lists -> + Add
          The "Action" should be "Allow"

        2. The DNS Resolver "Outgoing Network Interfaces" in both pfSense must be set to "LAN" and "Localhost"
          https://forum.netgate.com/topic/103395/dns-server-domain-override-over-ipsec-vpn-not-working

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