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

    DNS resolution doesn´t work

    Scheduled Pinned Locked Moved DHCP and DNS
    3 Posts 3 Posters 2.5k 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.
    • S
      speedy-luis
      last edited by

      Hello everybody!

      We use the Pfsense 1.2.3-RC1 (Uptime 253 days) and everything works fine.

      But we have one problem:
      The DNS resolution doesn´t work correctly.

      When I make a "nslookup" from clientA to clientB, the answer is:
      non authorized answer:
      name: clientB.mydomain.com
      adress: our external IP-Address

      Or when I make a "nslookup" from clientA to www.google.com, the answer ist:
      non authorized answer:
      name: www.google.com.mydomain.com
      adress: our external IP-Address

      How you can see, everytime "mydomain.com" is added and our external IP-Address is shown…

      What is going wrong here?

      Sorry for my bad english....

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        When testing with DNS tools, always end a fully qualified domain name with a "." - otherwise it will assume you want to append your system's search domain.

        So to lookup "www.google.com" you must use "www.google.com."

        The most common way that you see the behavior you are getting is if "mydomain.com" has wildcard DNS enabled, so it's responding to any query with the same reply.

        Due to the search domain being used, it ends up getting a response for a query that usually fails.

        So your problem could be solved by disabling wildcard DNS on your domain name.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • M
          matejnjiri
          last edited by

          @jimp:

          When testing with DNS tools, always end a fully qualified domain name with a "." - otherwise it will assume you want to append your system's search domain.

          So to lookup "www.google.com" you must use "www.google.com."

          The most common way that you see the behavior you are getting is if "mydomain.com" has wildcard DNS enabled, so it's responding to any query with the same reply.

          Due to the search domain being used, it ends up getting a response for a query that usually fails.

          So your problem could be solved by disabling wildcard DNS on your domain name.

          try without www, don't use it at all.

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