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

    Wrong DNS records

    Scheduled Pinned Locked Moved DHCP and DNS
    6 Posts 3 Posters 541 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
      samuellsk
      last edited by

      Hi

      When i do a nslookup from a linux machine i get a record / address that is not supposed to be there. I have tried to restart the dns service on the pfsense and tried to flush cache on linux client with no luck.

      ba83a878-0c32-471b-b570-2e0bef746af6-image.png

      the record for provisioner01 with ip 10.100.1.3
      the record for provisioner02 with ip 10.100.1.4

      are wrong. they shouldnt be there and they are not in the pfsense in services / dns resolver.

      Anyone have an idea what i should clear / restart in order to remove those records ?

      Thank you.

      johnpozJ 1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator @samuellsk
        last edited by

        @samuellsk those are rfc1918 - you need to look where you put those or where they are coming from. They would not return that if asking the internet, because for one they are not there, and 2nd they are rfc1918 and rebind protection would not allow those to be returned to the client without specific settings allowing that in pfsense - ie turning off rebind protection or setting the domain as private.

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.7.2, 24.11

        1 Reply Last reply Reply Quote 0
        • S
          samuellsk
          last edited by samuellsk

          I assumed that it was clear enough that the range is not the problem. So i ll try to be a little bit clearer this time. - maybe i ve got your answer wrong.

          1abcc6bc-52af-4532-8b88-5aea19f5cd08-image.png

          I ve asked, specifically dns at ip 10.100.1.254 whats the ip of the proviosioner01 and 02. And he replied with 20 days old ip addresses respectively ending with 1.3 and 1.4 (in RED squares , but in reality he should have replied only with the ones in GREEN squares ending 1.31 and 1.32 - like configured, cause if i dump the config and search for them, they are nowwhere). The question is simple , WHY ? Where are they if not in the cache of pfsense router ? Where is he getting them ? Tcpdump showed that he replied (not "something instead" of router).

          the whole zone is on the lan part of the router, so the upstream dns have no idea whats in there, so he cant be getting that from there.

          And yes the dns rebinding protection is enabled (the disable option is unchecked)

          johnpozJ S 2 Replies Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator @samuellsk
            last edited by johnpoz

            @samuellsk said in Wrong DNS records:

            Where are they if not in the cache of pfsense router ?

            did you actually restart unbound. There is no place to cache those.. If those are the records you have there, that is what would be returned if you asked unbound.

            did you remove the old records.. Your getting both back.

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.7.2, 24.11

            1 Reply Last reply Reply Quote 0
            • S
              SteveITS Galactic Empire @samuellsk
              last edited by

              @samuellsk What IS serving that rohp01.brightpick.ai domain and if you query that name server what do you get?

              pfSense would normally query public DNS (which doesn't resolve rohp01.brightpick.ai) or pfSense's DNS Resolver could be set to forward all queries to another DNS server (which could have the domain configured locally) or Resolver could have a domain or host override (which would set rohp01.brightpick.ai or a hostname to forward to specific DNS servers).

              As noted since there are two answers it's likely old records were not removed.

              Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
              When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
              Upvote 👍 helpful posts!

              1 Reply Last reply Reply Quote 0
              • S
                samuellsk
                last edited by

                figured it out, there was an old dhcp reservation on one of the carp routers that were not synchrnoised.

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