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

    Upgrade pfsense CE 2.7.0 to 2.7.1

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    89 Posts 24 Posters 34.6k 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Does DNS Lookup show success for all configured DNS servers? Including 127.0.0.1?

      R 1 Reply Last reply Reply Quote 0
      • R
        reberhar @stephenw10
        last edited by

        @stephenw10 Yes, all look well.

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Hmm, should be fine from any clients using it then. Perhaps the clients are not using Unbound in pfSense? Or perhaps that DNS traffic is being blocked by the firewall rules? Or forced out of gateway so it never reaches the LAN IP?

          R 1 Reply Last reply Reply Quote 0
          • R
            reberhar @stephenw10
            last edited by reberhar

            @stephenw10 Hi Steve,
            I thought about lots of things, secure DNS, etc. The thing is the rest of the bandwidth is intact. I finally disabled and re-enabled the DNS resolver from the gui and it came back for now. I thought about the cache but that seems like it can't be the problem. It won't resolve without the cache functioning. And dig finds the root and the name server.

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Unbound doesn't stop running? If it did then localhost should show no reply in DNS Lookup.

              R 1 Reply Last reply Reply Quote 0
              • R
                reberhar @stephenw10
                last edited by

                @stephenw10 Hi Steve, Yes 127.0.0.1 gives good and accurate response. This should not be possible. However, at other times in dealing with DNS I have seen nslookup function on the client computer before the pfSense DNS diagnostic tool. Not this time however.

                I am hoping that this just goes away. :)

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  Hmm, well I wouldn't expect it to but..... 🤞

                  R 1 Reply Last reply Reply Quote 0
                  • R
                    reberhar @stephenw10
                    last edited by

                    @stephenw10 I know better than to expect it to go away, but I can't think about it right now. I have other servers to (t)fry. If and when I figure it out I will post what I find. The hardest part is the disruptions for my users.

                    Thanks for your help.

                    R 1 Reply Last reply Reply Quote 0
                    • R
                      reberhar @reberhar
                      last edited by

                      @reberhar So Steve, I have a question.

                      We use Comcast which frequently has significant latency. During the latency times I note that DNS requests backup, causing latency reports because dpinger requests get lost in the pile. Buffer bloat, of course can be a problem. I have read articles about that mentioning that our desire to maintain network requests in a linear fashion might sometimes be misplaced.

                      So I use priq on my shaper. Is there someway to make that queue smaller? I do note that at the time of the recent problems there is no signficant latency reflected in the gui on the WAN. The logs do reflect very recent latency however. This doesn´t seem like it can be the problem because localhost is resolving DNS requests from the Diagnostics Lookup when I do the testing. And reqular non DNS traffic does not seem to be affected. Stuff that is already in the state table continues to work.

                      I am just trying to think outside of the box.

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