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

    DNS Resolver not working after config restore

    Scheduled Pinned Locked Moved DHCP and DNS
    16 Posts 2 Posters 1.3k 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
      SteveITS Galactic Empire @doxymoron
      last edited by

      @doxymoron well not every router will respond to pings but it looks like you connection dies at 74.125.50.194. Which apparently has no PTR record so not sure what that is.

      Ping 8.8.8.8 continuously, do you have packet loss?

      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!

      D 1 Reply Last reply Reply Quote 0
      • D
        doxymoron @SteveITS
        last edited by

        @steveits No, it's solid.

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

          @doxymoron Long shot but does it work if you reset to defaults? Can always restore again after.

          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!

          D 1 Reply Last reply Reply Quote 0
          • D
            doxymoron @SteveITS
            last edited by doxymoron

            @steveits I just completely installed 2.6 from scratch. I'm unable to resolve anything. Something isn't right...could there be some issue at the ISP level where they are blocking pfsense as a DNS resolver? I don't get what's going on.

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

              @doxymoron Can you “nslookup netgate.com 8.8.8.8” from your PC?

              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!

              D 1 Reply Last reply Reply Quote 0
              • D
                doxymoron @SteveITS
                last edited by

                @steveits Yes that works. But when I try to nslookup using pfsense, gives me DNS request timed out.

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

                  @doxymoron if you enable forwarding in the Resolver settings does it work?

                  I mean, I suppose it’s conceivable the ISP is blocking third party DNS but I would think they’d block Google before the root servers. Awfully uncommon though. Not sure I’ve heard of blocking DNS at the ISP level.

                  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!

                  D 1 Reply Last reply Reply Quote 0
                  • D
                    doxymoron @SteveITS
                    last edited by

                    @steveits So enabling forwarding worked on the fresh install. I have restored my config and made the same settings. It still did not resolve. I found this thread:

                    https://forum.netgate.com/topic/87141/can-t-access-internet-fresh-install/20

                    Which suggests doing this:

                    Go to Interface - WAN - Uncheck Block private networks.

                    I did this and now DNS Resolver is working. Interestingly, I went back and checked that box again, and it still continues to work. I really don't know why or how though...

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

                      @doxymoron Hmm that adds a rule to prevent incoming connections on the interface.

                      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!

                      D 1 Reply Last reply Reply Quote 0
                      • D
                        doxymoron @SteveITS
                        last edited by

                        @steveits I wonder if somehow unchecking that box reset something that was in my config causing it not to work correctly? Not sure...

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