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

    Diagnostic and resolve dns lookup

    Scheduled Pinned Locked Moved DHCP and DNS
    7 Posts 2 Posters 273 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.
    • frankzF
      frankz
      last edited by

      Hello everyone, in the pfsense diagnostics if I type a host that does not exist at the domain level it returns valid ips to me.
      Screenshot 2024-04-12 alle 12.03.01.png

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan @frankz
        last edited by Gertjan

        @frankz

        69.172.169.161 => 69-172-169-161.cable.teksavvy.com.

        pfSense version ?
        I presume you've changed the default DNS settings. Yes ? Why ?
        Possible that you get back to the default settings "the ones that work (better)" ?

        I managed to get the same result :

        b9f526e0-92cd-44ff-b22a-c2fd7ca33c59-image.png

        but why ?

        tell me how you did it, and I tell you how I did it 😊

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        frankzF 1 Reply Last reply Reply Quote 0
        • frankzF
          frankz @Gertjan
          last edited by

          @Gertjan Sorry but the translation eng ita does not make me understand. The settings are the standard 127.0.0.1 and forwarding to external dns . I have been using the DNS Resolver for years . But if I try from a client no error . Pf 2.7.2

          GertjanG 1 Reply Last reply Reply Quote 0
          • GertjanG
            Gertjan @frankz
            last edited by Gertjan

            @frankz said in Diagnostic and resolve dns lookup:

            and forwarding to external dns . I have been using the DNS Resolver for years

            That's the answer : you forward to some external DNS, and when you asked it : what is the IPv4 of "noexisthost.local.lan" it answered : 69.172.169.161

            The other answer was what I did :
            I created a host override for "noexisthost.local.lan" so it points to 69.172.169.161
            This is indeed problematic.

            Can you tell to who you forward ?

            @frankz said in Diagnostic and resolve dns lookup:

            But if I try from a client no error

            You mean : you get the NXDOMAIN error message ?

            C:\Users\Gauche>nslookup noexisthost.local.lan
            Serveur :   pfSense.bhf.tld
            Address:  2a01:cb19:907:dead:beef:77ff:fe29:392c
            
            *** pfSense.bhf.td "not succeeded to find"** noexisthost.local.lan : Non-existent domain
            

            ** translated from French to English.

            No "help me" PM's please. Use the forum, the community will thank you.
            Edit : and where are the logs ??

            frankzF 2 Replies Last reply Reply Quote 0
            • frankzF
              frankz
              last edited by

              )
              3.png 2.png
              Ok can you try from tools diagnostic > dnslooukp ?
              My client linux , using pfsense resolver read a correct response , but pfsense from diagnostic tools no .

              1 Reply Last reply Reply Quote 0
              • frankzF
                frankz @Gertjan
                last edited by

                @Gertjan dns default is localhost 127.0.0.1 and root server

                1 Reply Last reply Reply Quote 0
                • frankzF
                  frankz @Gertjan
                  last edited by

                  @Gertjan i resolv with change dns resolver trasparent in static

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