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

    pfsense dashboard show "Unable to check for update" via Quad9 DNS

    Scheduled Pinned Locked Moved General pfSense Questions
    28 Posts 4 Posters 1.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 stephenw10

      Does it work if you're not using DoT? Edit: Missed some replies 🙄

      Though that works fine for me using DoT to 8.8.8.8:

      Jul 13 21:49:55 	unbound 	23889 	[23889:1] info: resolving pfsense.org. A IN
Jul 13 21:49:55 	unbound 	23889 	[23889:1] info: processQueryTargets: pfsense.org. A IN
Jul 13 21:49:55 	unbound 	23889 	[23889:1] info: sending query: pfsense.org. A IN
Jul 13 21:49:55 	unbound 	23889 	[23889:1] debug: sending to target: <.> 8.8.8.8#853
Jul 13 21:49:55 	unbound 	23889 	[23889:1] debug: cache memory msg=16528 rrset=16528 infra=3280 val=0
Jul 13 21:49:55 	unbound 	23889 	[23889:1] debug: iterator[module 0] operate: extstate:module_wait_reply event:module_event_reply
Jul 13 21:49:55 	unbound 	23889 	[23889:1] info: iterator operate: query pfsense.org. A IN
Jul 13 21:49:55 	unbound 	23889 	[23889:1] info: response for pfsense.org. A IN
Jul 13 21:49:55 	unbound 	23889 	[23889:1] info: reply from <.> 8.8.8.8#853
Jul 13 21:49:55 	unbound 	23889 	[23889:1] info: query response was ANSWER
Jul 13 21:49:55 	unbound 	23889 	[23889:1] info: finishing processing for pfsense.org. A IN

      I don't actually see it trying to resolve anything in your logs.

      Steve

      M 1 Reply Last reply Reply Quote 0
      • M
        MaverickHL @stephenw10
        last edited by

        @stephenw10

        Which is the problem, nothing is coming up to help me determine the issue. I took a while to get back because I wanted to do the log capture at a time when less people are working so I can capture them. These are the log differences between Cloudflare and Quad9 and the fact it does not resolve in Quad9 at all is very weird.

        CloudFlare response after accessing System > Update page on pfsense:

        Jul 13 20:41:50 unbound 28884 [28884:0] info: 127.0.0.1 pkg01-atx.netgate.com. AAAA IN
        Jul 13 20:41:50 unbound 28884 [28884:0] info: 127.0.0.1 pkg01-atx.netgate.com. A IN
        Jul 13 20:41:50 unbound 28884 [28884:1] info: 127.0.0.1 pkg01-atx.netgate.com. AAAA IN
        Jul 13 20:41:50 unbound 28884 [28884:0] info: 127.0.0.1 pkg01-atx.netgate.com. A IN
        Jul 13 20:41:50 unbound 28884 [28884:0] info: 127.0.0.1 pkg01-atx.netgate.com. AAAA IN
        Jul 13 20:41:50 unbound 28884 [28884:1] info: 127.0.0.1 pkg01-atx.netgate.com. A IN
        Jul 13 20:41:50 unbound 28884 [28884:1] info: 127.0.0.1 _https._tcp.packages.netgate.com. SRV IN
        Jul 13 20:41:50 unbound 28884 [28884:0] info: control cmd: stats_noreset
        Jul 13 20:41:50 unbound 28884 [28884:0] debug: new control connection from 127.0.0.1 port 7536
        Jul 13 20:41:49 unbound 28884 [28884:0] info: 127.0.0.1 pkg00-atx.netgate.com. AAAA IN
        Jul 13 20:41:49 unbound 28884 [28884:2] info: 127.0.0.1 pkg00-atx.netgate.com. A IN
        Jul 13 20:41:49 unbound 28884 [28884:0] info: 127.0.0.1 pkg00-atx.netgate.com. AAAA IN
        Jul 13 20:41:49 unbound 28884 [28884:1] info: 127.0.0.1 pkg00-atx.netgate.com. A IN
        Jul 13 20:41:49 unbound 28884 [28884:1] debug: cache memory msg=231360 rrset=334815 infra=8306 val=124083
        Jul 13 20:41:49 unbound 28884 [28884:1] info: Verified that unsigned response is INSECURE

        Quad9 response after accessing System > Update page on pfsense:

        Jul 13 20:48:19 unbound 56545 [56545:1] debug: outnettcp got tcp error -1
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: cache memory msg=72336 rrset=81059 infra=8057 val=71562
        Jul 13 20:48:18 unbound 56545 [56545:3] info: validator operate: query 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: validator[module 0] operate: extstate:module_wait_module event:module_event_moddone
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: return error response SERVFAIL
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: configured stub or forward servers failed -- returning SERVFAIL
        Jul 13 20:48:18 unbound 56545 [56545:3] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] info: query response was THROWAWAY
        Jul 13 20:48:18 unbound 56545 [56545:3] info: reply from <.> 9.9.9.9#853
        Jul 13 20:48:18 unbound 56545 [56545:3] info: response for 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: iterator[module 1] operate: extstate:module_wait_reply event:module_event_reply
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: cache memory msg=72336 rrset=81059 infra=8057 val=71562
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: sending to target: <.> 9.9.9.9#853
        Jul 13 20:48:18 unbound 56545 [56545:3] info: sending query: 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] info: query response was THROWAWAY
        Jul 13 20:48:18 unbound 56545 [56545:3] info: reply from <.> 9.9.9.9#853
        Jul 13 20:48:18 unbound 56545 [56545:3] info: response for 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: iterator[module 1] operate: extstate:module_wait_reply event:module_event_reply
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: cache memory msg=72336 rrset=81059 infra=8057 val=71562
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: sending to target: <.> 9.9.9.9#853
        Jul 13 20:48:18 unbound 56545 [56545:3] info: sending query: 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] info: query response was THROWAWAY
        Jul 13 20:48:18 unbound 56545 [56545:3] info: reply from <.> 9.9.9.9#853
        Jul 13 20:48:18 unbound 56545 [56545:3] info: response for 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: iterator[module 1] operate: extstate:module_wait_reply event:module_event_reply
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: cache memory msg=72336 rrset=81059 infra=8057 val=71562
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: sending to target: <.> 9.9.9.9#853
        Jul 13 20:48:18 unbound 56545 [56545:3] info: sending query: 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] info: query response was THROWAWAY
        Jul 13 20:48:18 unbound 56545 [56545:3] info: reply from <.> 9.9.9.9#853
        Jul 13 20:48:18 unbound 56545 [56545:3] info: response for 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: iterator[module 1] operate: extstate:module_wait_reply event:module_event_reply
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: cache memory msg=72336 rrset=81059 infra=8057 val=71562
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: sending to target: <.> 9.9.9.9#853
        Jul 13 20:48:18 unbound 56545 [56545:3] info: sending query: 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: iterator[module 1] operate: extstate:module_wait_reply event:module_event_noreply
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: tcp error for address 9.9.9.9 port 853
        Jul 13 20:48:18 unbound 56545 [56545:3] debug: outnettcp got tcp error -1
        Jul 13 20:48:17 unbound 56545 [56545:0] debug: cache memory msg=72336 rrset=81059 infra=8057 val=71562

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

          If the query answer from " 9.9.9.9#853" is sympathetically "THROWAWAY" you can do 2 things :
          Stop using TLS or even stop using 9.9.9.9.

          You're sure nothing is filtered upstream ?
          I saw

          debug: tcp error for address 9.9.9.9 port 853

          As TLS over port 853 needs TCP, and TCP is bad, then 9.9.9.9 doesn't even receive your request correctly ( ? ) ....

          When the quad9 issues go away (thrown away ;) ) I advise you to look at other threads in this forum. Because this :

          @maverickhl said in pfsense dashboard show "Unable to check for update" via Quad9 DNS:

          Jul 13 12:34:45 dhcpleases 14363 Could not deliver signal HUP to process 45787: No such process

          is also a possible issue, and discussed a lot on the forum.
          It means unbound was in the process of getting restarted - and while it was restarting, it was informed to restart again.
          For now : how often does yours restart ?
          Go to the page and search for "info: start of service (unbound 1.15.0)." and count them.
          How many a day ? per hour ? even more ?

          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
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Still not seeing any logs for info: resolving. Everything in your logs appears to be reverse lookup for PTR. So I'd suggest it's not using Unbound for those lookups. Something is not configured as you expect it to be.
            However even if that is that case it's hard to explain why pkg update works but the dashboard check does not.
            Try to resolve ews.netgate.com in Diag > DNS Lookup. Make sure all the defined servers there can resolve it.

            Steve

            M 1 Reply Last reply Reply Quote 0
            • M
              MaverickHL @stephenw10
              last edited by

              @stephenw10

              ews.netgate.com does resolve returning an IP of 208.123.73.93

              I turned off DoT and the results are not any better and can't find any info: resolving lines during the update check:

              Jul 14 08:59:42 unbound 12183 [12183:0] info: control cmd: stats_noreset
              Jul 14 08:59:42 unbound 12183 [12183:0] debug: new control connection from 127.0.0.1 port 40927
              Jul 14 08:59:42 unbound 12183 [12183:0] debug: cache memory msg=158472 rrset=215935 infra=8306 val=95561
              Jul 14 08:59:42 unbound 12183 [12183:0] info: validator operate: query 4.4.8.8.in-addr.arpa. PTR IN
              Jul 14 08:59:42 unbound 12183 [12183:0] debug: validator[module 0] operate: extstate:module_wait_module event:module_event_moddone
              Jul 14 08:59:42 unbound 12183 [12183:0] debug: return error response SERVFAIL
              Jul 14 08:59:42 unbound 12183 [12183:0] debug: configured stub or forward servers failed -- returning SERVFAIL
              Jul 14 08:59:42 unbound 12183 [12183:0] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN
              Jul 14 08:59:42 unbound 12183 [12183:0] info: query response was THROWAWAY
              Jul 14 08:59:42 unbound 12183 [12183:0] info: reply from <.> 9.9.9.9#53
              Jul 14 08:59:42 unbound 12183 [12183:0] info: response for 4.4.8.8.in-addr.arpa. PTR IN
              Jul 14 08:59:42 unbound 12183 [12183:0] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN

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

                Mmm, so exactly what settings do you have in System > General Setup and in Unbound?

                M 1 Reply Last reply Reply Quote 0
                • M
                  MaverickHL @stephenw10
                  last edited by

                  @stephenw10

                  Nothing fancy, but here are the main things I have setup:

                  System General Setup:

                  Added DNS 9.9.9.9 and 149.112.112.112

                  Set DNS behavior to Use Local then remote (default)

                  DNS Resolver Settings:

                  Network Interface = All
                  Outgoing Network Interface = WAN
                  Domain Local Zone Type = Transparent
                  DNSSEC = FALSE
                  DNS Query Forward = TRUE
                  Use SSL/TLS = TRUE
                  DHCP Reg = TRUE
                  Static DHCP = TRUE
                  Advanced Config =

                  server:include: /var/unbound/pfb_dnsbl.*conf

                  server:
                  log-queries: yes

                  Advanced Tab:

                  Everything left default except when changing log level to 3.

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

                    Hmm, the only thing different I have is the custom entry you have:

                    server:
log-queries: yes

                    But I see all the queries logged so I suspect you may have created a conflict there. Try removing that.

                    Steve

                    M 1 Reply Last reply Reply Quote 0
                    • M
                      MaverickHL @stephenw10
                      last edited by

                      @stephenw10

                      Sadly, nope same odd response back and no info: resolve lines -_-;

                      Jul 14 10:45:31 unbound 88800 [88800:0] debug: cache memory msg=68474 rrset=68889 infra=8306 val=0
                      Jul 14 10:45:31 unbound 88800 [88800:0] debug: return error response SERVFAIL
                      Jul 14 10:45:31 unbound 88800 [88800:0] debug: configured stub or forward servers failed -- returning SERVFAIL
                      Jul 14 10:45:31 unbound 88800 [88800:0] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN
                      Jul 14 10:45:31 unbound 88800 [88800:0] info: query response was THROWAWAY
                      Jul 14 10:45:31 unbound 88800 [88800:0] info: reply from <.> 9.9.9.9#853
                      Jul 14 10:45:31 unbound 88800 [88800:0] info: response for 4.4.8.8.in-addr.arpa. PTR IN
                      Jul 14 10:45:31 unbound 88800 [88800:0] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN
                      Jul 14 10:45:31 unbound 88800 [88800:0] debug: iterator[module 0] operate: extstate:module_wait_reply event:module_event_reply
                      Jul 14 10:45:31 unbound 88800 [88800:0] debug: cache memory msg=68284 rrset=68889 infra=8306 val=0
                      Jul 14 10:45:31 unbound 88800 [88800:0] debug: sending to target: <.> 9.9.9.9#853
                      Jul 14 10:45:31 unbound 88800 [88800:0] info: sending query: 4.4.8.8.in-addr.arpa. PTR IN
                      Jul 14 10:45:31 unbound 88800 [88800:0] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN
                      Jul 14 10:45:31 unbound 88800 [88800:0] info: query response was THROWAWAY
                      Jul 14 10:45:31 unbound 88800 [88800:0] info: reply from <.> 9.9.9.9#853
                      Jul 14 10:45:31 unbound 88800 [88800:0] info: response for 4.4.8.8.in-addr.arpa. PTR IN
                      Jul 14 10:45:31 unbound 88800 [88800:0] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN
                      Jul 14 10:45:31 unbound 88800 [88800:0] debug: iterator[module 0] operate: extstate:module_wait_reply event:module_event_reply
                      Jul 14 10:45:31 unbound 88800 [88800:0] debug: cache memory msg=68284 rrset=68889 infra=8306 val=0
                      Jul 14 10:45:31 unbound 88800 [88800:0] debug: sending to target: <.> 9.9.9.9#853
                      Jul 14 10:45:31 unbound 88800 [88800:0] info: sending query: 4.4.8.8.in-addr.arpa. PTR IN
                      Jul 14 10:45:31 unbound 88800 [88800:0] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN

                      I do think it is Quad9's issue and mostly likely regional. I had to send a few DNS resolution request for their upstream provider to fix since some websites were not resolving but was apparently accessible based on their domain checker.

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

                        Hmm. Weird that it's not showing queries in unbound though. Seems like however it's failing could be because it's not going via Unbound...

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