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

    Slow DNS after 22.05

    Scheduled Pinned Locked Moved DHCP and DNS
    270 Posts 31 Posters 140.4k 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.
    • J
      Jax
      last edited by

      Really, I think it's clear something broke in 22.05 and there's not any point in pretending it's a user problem. We've all experienced this and found some work arounds. Perhaps the maintainers should take a serious look at the code and try to figure out why so many users experienced the same phenomenon.

      johnpozJ 1 Reply Last reply Reply Quote 3
      • M
        Mikymike82 @tentpiglet
        last edited by

        @tentpiglet I think my solution might (temporarily) help you out with the DNS issues you and others in this topic are experiencing. 1,5 weeks of stable connection so far.

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

          @mikymike82 said in Slow DNS after 22.05:

          my dns resolution was a complete mess

          What about answering questions ?

          Btw : I used a bare bone system (old Dell desktop, added a Quad Intel NIC) for nearly 10 years.
          Since last Juin I'm using a SG 4100. Works great.
          I have DNS statistics.

          @jax said in Slow DNS after 22.05:

          why so many users experienced the same phenomenon

          120 thousand plus active users - all without DNS ?
          That is, I can tell that my DNS works. edit : showing another way to see the resolver restarting.

          @mikymike82 said in Slow DNS after 22.05:

          22.01 no problems and after upgrading to 22.05

          If you don't use IPv6, do what @johnpoz said.

          Btw : I never used 22.01 - 22.01 was pre installed on my 4100, but I upgraded the day I received the unit.

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

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

            @jax said in Slow DNS after 22.05:

            We've all experienced

            We are??? I am not having any issues..

            why so many users experienced the same phenomenon.

            So many users? like the handful posted here? Where are these users posting that they are having issues? The 1000's and 1000's of them that are running 22.05? All having issues? Some how I have seem to have missed that it was such a wide spread problem - very odd since I am on the board like all day pretty much every day.. And some how I have missed that its everyone having the issue..

            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.8, 24.11

            1 Reply Last reply Reply Quote 0
            • provelsP
              provels
              last edited by provels

              FWIW, I have had no problems on the VM and package set in my sig, clean built 2.6>22.01>22.05. I use IPv4/v6.

              Peder

              MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
              BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

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

                @provels But how can that be - we clearly all having issues, maybe your having an issue and just don't know it ;) hehehehe

                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.8, 24.11

                1 Reply Last reply Reply Quote 0
                • K
                  Kempain
                  last edited by

                  Managed to capture some nslookups when DNS bombed out.
                  It's really tricky to troubleshoot because it happens sporadically and randomly.

                  Interestingly requests to pfSense timed out twice, then it only returned an IPv6 address without IPv4, then it returned both IPv6 and IPv4. Maybe this adds some credence to the issue being related to IPv6 but who knows. IPv6 was returned first in this particular case so disabling IPv6 would have likely caused more harm.

                  I still want to check the unbound service to see how often that is restarting which I'll try do later to see if those 2 events line up.

                  pfSense DNS issue.png

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

                    @kempain said in Slow DNS after 22.05:

                    I still want to check the unbound service to see how often that is restarting which I'll try do later to see if those 2 events line up.

                    Also simple enough to just see how long its been running..

                    [22.05-RELEASE][admin@sg4860.local.lan]/root: unbound-control -c /var/unbound/unbound.conf status
                    version: 1.15.0
                    verbosity: 1
                    threads: 4
                    modules: 2 [ validator iterator ]
                    uptime: 333105 seconds
                    options: control(ssl)
                    unbound (pid 13952) is running...
                    [22.05-RELEASE][admin@sg4860.local.lan]/root: 
                    

                    So mine has been up 333K seconds, or getting close to 4 days.. Last time I posted it was like 10 days, another 6 days. I tend to restart it when doing something for some thread, where they need an option or something - think last one someone was asking how to block youtube, etc.

                    But you have no purposely restarted unbound/pfsense and your status shows that its only been up a short amount of time - something is wrong.

                    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.8, 24.11

                    K 1 Reply Last reply Reply Quote 1
                    • K
                      Kempain @johnpoz
                      last edited by

                      Cheers @johnpoz

                      So looks like mine is restarting relatively regularly.

                      dbdb9a92-dfdd-4159-9b5f-537e3ea23d6b-image.png

                      af33088e-4a2a-4d63-8268-ec48cf2b320d-image.png

                      Cool_CoronaC 1 Reply Last reply Reply Quote 0
                      • Cool_CoronaC
                        Cool_Corona @Kempain
                        last edited by

                        590ff612-b03d-4008-bf5e-b0cd5afba061-billede.png

                        Unbound on 2.5.2

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

                          @cool_corona @Kempain 300 some seconds unbound being up, doesn't bode well for caching name server ;)

                          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.8, 24.11

                          Cool_CoronaC 1 Reply Last reply Reply Quote 0
                          • Cool_CoronaC
                            Cool_Corona @johnpoz
                            last edited by

                            @johnpoz How to track all unbound restarts?

                            1 Reply Last reply Reply Quote 0
                            • T
                              tentpiglet @Gertjan
                              last edited by

                              @johnpoz said in Slow DNS after 22.05:

                              Do you have IPv6?

                              No. Although I think pfSense assigns a link local address to my wan and lan interface, my ISP does not provide me with a ip6 address.

                              @gertjan said in Slow DNS after 22.05:

                              22.05 or 2.6.0 ?

                              22.05-RELEASE (amd64)
                              built on Wed Jun 22 18:56:13 UTC 2022
                              FreeBSD 12.3-STABLE

                              UNstable means :
                              You found it 'not running', and no process 'unbound' was present when you list processes ?
                              Or the process unbound was there, but didn't answer ?
                              An nslookup from a PC on a LAN failed ?

                              unstable means I'm using a browser on a client and I get a "DNS_PROBE_FINISHED_NXDOMAIN" error (google chome), and when I hit the reload button a few moments later, the page will be found.

                              edit : how many times a day unbound restarts ?

                              grep 'start of service' /var/log/resolver.log | wc -l

                              64

                              first entry was at 10:21am local time this morning, so that's over the past 2 hours.

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

                                @tentpiglet said in Slow DNS after 22.05:

                                DNS_PROBE_FINISHED_NXDOMAIN

                                And what specific were you looking for - NX is not a dns failure, that is what you were looking for doesn't exist.

                                Also - browser errors are not troubleshooting dns problem - for all we know your browser is using doh and has zero to do with yoru local dns.

                                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.8, 24.11

                                T 1 Reply Last reply Reply Quote 0
                                • T
                                  tentpiglet @johnpoz
                                  last edited by

                                  @johnpoz said in Slow DNS after 22.05:

                                  And what specific were you looking for - NX is not a dns failure, that is what you were looking for doesn't exist.

                                  Randomly, any site I would go to. For example, the last time it happened when I said "enough is enough" and spun up a pihole container on my Proxmox server, it was "www.facebook.com".

                                  I'm pretty sure www.facebook.com exists.

                                  My wife was also reporting random disconnects from an online game she was playing, as well as getting similar site not found errors on her phone while reading reddit. Since moving DNS over to the pihole container, she's experienced no further issues.

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

                                    @tentpiglet said in Slow DNS after 22.05:

                                    I'm pretty sure www.facebook.com exists.

                                    A NX is a dns response that says that domain doesn't exist - why you got that error have no idea, but that is not a failure to talk to dns, that is whatever your dns was doing ended up with NX.. Maybe you would doing a query for www.facebook.com.org or www.facebook.com.somethingelse.tld

                                    Your browser trying to help you auto complete something etc..

                                    I would expect you have all kinds of issues if your local dns is restarting 64 times in less than 24 hours.. So yeah that would be problematic for sure..

                                    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.8, 24.11

                                    K T 2 Replies Last reply Reply Quote 0
                                    • K
                                      kvhs @johnpoz
                                      last edited by

                                      @johnpoz Like I described earlier I experienced this myself on duckduckgo.com when set as my primary search engine in the browser. Sometimes it would work othertimes not. Reloading a number of times would often work, but that could of course be an illusion if the cause was that some process was restarting.

                                      What would be the preferred test to demonstrate the problem, given its intermittent nature?

                                      johnpozJ 1 Reply Last reply Reply Quote 0
                                      • M
                                        Mikymike82
                                        last edited by

                                        @johnpoz @provels @Gertjan , maybe this is not a widespread problem.... but this seems to be an issue thats more than a single user/unit problem.
                                        Talking albout the so said thousends of other users that are not experiencing this problem is not helping in resolving this clear issue in version 22.05 as is clearly stated that even with a clean install i can clearly replicate the issue when upgrading to 22.05 from 22.01. The issue immideatly presents itself. The clients obviously can't resolve the domains hense the client(-s) getting the errors @tentpiglet was describing.

                                        @Kempain @tentpiglet ; have you tried my suggestion for sesolving the issue (although maybe a temporary resolution), as stated i im running 1,5 week without problems at this moment

                                        M T K 3 Replies Last reply Reply Quote 0
                                        • M
                                          Mikymike82 @Mikymike82
                                          last edited by

                                          btw, i'm not running in a virtualized environment.
                                          Running bare metal on the "same" mircoserver hardware as the SG-7100. Supermicro board with Atom C3758.

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

                                            and further; as i am not having the problem any more, i was just replying to help others out.... but.... my solution is not to my satisfaction as this should not be the resolution but more a workaround for a problem on which we do not have a clear cause (yet).

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