pfsense dashboard show "Unable to check for update" via Quad9 DNS
-
Err... looks fine to me...
Updating repositories metadata...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Your system is up to date -
Hmm. Weird.
So if you set any other DNS servers the update works as expected?
I assume it's running 2.6?
-
I am currently running version 2.6 and yes it does work with other DNS service providers (Cloudflare). For testing purposes I only set the DNS servers to either Cloudflare or Quad9 and what I found is that the dashboard and the System > Update pages in pfsense gets back with the failing update message.
The command line troubleshooting all turn out fine based on what you provided which also makes it weird.
-
That is hard to explain.
Are there any errors logged?
-
Based on the documentation found here: https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html
I downloaded the upgrade logs from /conf/upgrade_log.latest.txt
And found no errors... so I am confused at what the DNS is doing to block pfsense update checks. For now I will probably stick with Cloudflare until I can find some way to figure out what domain is being hit for those updates since the logs show nothing -_-;
-
@maverickhl said in pfsense dashboard show "Unable to check for update" via Quad9 DNS:
I only set the DNS servers to either
What happens if you set these to 'none' ? That is : when you (re)set all the DNS settings as per Netgate
default settings ? Because these will work out of the box.It boils down to ditching forwarding mode, go back to resolving.
Because : when you forward, you use a single point of failure : if Quand9 has a hard day, your DNS is out.
Resolving uses what has been invented in the eighties : there are 13 core root top level domain servers on the Internet, and the resolver uses any of them. If one is down, the party isn't over, another one is used.
The day all 13 are down or not reachable, you can safely shut down pfSense, as quad9, 8888 etc use the same "big 13".I do presume that Quad9 doesn't have any issues. I'm just proposing "use default settings" as these will/should/must work. Try it for yourself.
-
If you set Unbound in forwarding mode, which I assume you already have. Set 9.9.9.9 in System > General Setup and leave DNS servers set to Use Local. Then you can turn up the logging in Unbound and see what's failing.
Steve
-
So set only 9.9.9.9 and set to use Local DNS and fall back to remote. Log Level on the DNS resolver was set to level 3 and these are the results when accessing the System > Update page:
Jul 13 12:35:00 sshguard 63076 Now monitoring attacks.
Jul 13 12:35:00 sshguard 40886 Exiting on signal.
Jul 13 12:34:48 kernel config_aqm Unable to configure flowset, flowset busy!
Jul 13 12:34:48 kernel config_aqm Unable to configure flowset, flowset busy!
Jul 13 12:34:47 check_reload_status 403 Reloading filter
Jul 13 12:34:47 php-fpm 55880 /system.php: NTPD is starting up.
Jul 13 12:34:45 dhcpleases 14363 Could not deliver signal HUP to process 45787: No such process.
Jul 13 12:34:40 root 92857 /etc/rc.d/hostid: WARNING: hostid: unable to figure out a UUID from DMI data, generating a new one
Jul 13 12:34:40 check_reload_status 403 Syncing firewall -
@maverickhl FWIW we use Quad9 and have never had an issue. I just checked a couple and they worked. One has 8.8.4.4 as the last DNS server, but the update check finished in about 1-2 seconds so that should be way faster than a DNS timeout through the other entries (2s each as I recall).
Quad9 has a lot of servers so it could be a regional issue? https://status.quad9.net/smap/ shows "20 in bypass, 1 in maintenance" which I would think means those are intentionally offline...
-
Make sure you see queries logged when you check Diag > DNS Lookup.
-
Sorry I think I just sent the generic logs not the DNS resolver logs. This is what came up a few moments ago attempting the System > Update page load:
Jul 13 15:07:01 unbound 14038 [14038:3] debug: cache memory msg=90265 rrset=95647 infra=8306 val=0 Jul 13 15:07:01 unbound 14038 [14038:3] debug: return error response SERVFAIL Jul 13 15:07:01 unbound 14038 [14038:3] debug: configured stub or forward servers failed -- returning SERVFAIL Jul 13 15:07:01 unbound 14038 [14038:3] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: query response was THROWAWAY Jul 13 15:07:01 unbound 14038 [14038:3] info: reply from <.> 9.9.9.9#853 Jul 13 15:07:01 unbound 14038 [14038:3] info: response for 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] debug: iterator[module 0] operate: extstate:module_wait_reply event:module_event_reply Jul 13 15:07:01 unbound 14038 [14038:3] debug: cache memory msg=90265 rrset=95647 infra=8306 val=0 Jul 13 15:07:01 unbound 14038 [14038:3] debug: sending to target: <.> 9.9.9.9#853 Jul 13 15:07:01 unbound 14038 [14038:3] info: sending query: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: query response was THROWAWAY Jul 13 15:07:01 unbound 14038 [14038:3] info: reply from <.> 9.9.9.9#853 Jul 13 15:07:01 unbound 14038 [14038:3] info: response for 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] debug: iterator[module 0] operate: extstate:module_wait_reply event:module_event_reply Jul 13 15:07:01 unbound 14038 [14038:3] debug: cache memory msg=90265 rrset=95647 infra=8306 val=0 Jul 13 15:07:01 unbound 14038 [14038:3] debug: sending to target: <.> 9.9.9.9#853 Jul 13 15:07:01 unbound 14038 [14038:3] info: sending query: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: query response was THROWAWAY Jul 13 15:07:01 unbound 14038 [14038:3] info: reply from <.> 9.9.9.9#853 Jul 13 15:07:01 unbound 14038 [14038:3] info: response for 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] debug: iterator[module 0] operate: extstate:module_wait_reply event:module_event_reply Jul 13 15:07:01 unbound 14038 [14038:3] debug: cache memory msg=90265 rrset=95647 infra=8306 val=0 Jul 13 15:07:01 unbound 14038 [14038:3] debug: sending to target: <.> 9.9.9.9#853 Jul 13 15:07:01 unbound 14038 [14038:3] info: sending query: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: query response was THROWAWAY Jul 13 15:07:01 unbound 14038 [14038:3] info: reply from <.> 9.9.9.9#853 Jul 13 15:07:01 unbound 14038 [14038:3] info: response for 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] debug: iterator[module 0] operate: extstate:module_wait_reply event:module_event_reply Jul 13 15:07:01 unbound 14038 [14038:3] debug: cache memory msg=90265 rrset=95647 infra=8306 val=0 Jul 13 15:07:01 unbound 14038 [14038:3] debug: sending to target: <.> 9.9.9.9#853 Jul 13 15:07:01 unbound 14038 [14038:3] info: sending query: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: query response was THROWAWAY Jul 13 15:07:01 unbound 14038 [14038:3] info: reply from <.> 149.112.112.112#853 Jul 13 15:07:01 unbound 14038 [14038:3] info: response for 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] debug: iterator[module 0] operate: extstate:module_wait_reply event:module_event_reply Jul 13 15:07:01 unbound 14038 [14038:3] debug: cache memory msg=90265 rrset=95647 infra=8306 val=0 Jul 13 15:07:01 unbound 14038 [14038:3] debug: sending to target: <.> 149.112.112.112#853 Jul 13 15:07:01 unbound 14038 [14038:3] info: sending query: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: query response was THROWAWAY Jul 13 15:07:01 unbound 14038 [14038:3] info: reply from <.> 149.112.112.112#853 Jul 13 15:07:01 unbound 14038 [14038:3] info: response for 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] debug: iterator[module 0] operate: extstate:module_wait_reply event:module_event_reply Jul 13 15:07:01 unbound 14038 [14038:3] debug: cache memory msg=90265 rrset=95647 infra=8306 val=0 Jul 13 15:07:01 unbound 14038 [14038:3] debug: sending to target: <.> 149.112.112.112#853 Jul 13 15:07:01 unbound 14038 [14038:3] info: sending query: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:3] debug: iterator[module 0] operate: extstate:module_wait_reply event:module_event_noreply Jul 13 15:07:01 unbound 14038 [14038:3] debug: tcp error for address 9.9.9.9 port 853 Jul 13 15:07:01 unbound 14038 [14038:3] debug: outnettcp got tcp error -1 Jul 13 15:07:01 unbound 14038 [14038:2] debug: cache memory msg=90265 rrset=95647 infra=8306 val=0 Jul 13 15:07:01 unbound 14038 [14038:2] debug: return error response SERVFAIL Jul 13 15:07:01 unbound 14038 [14038:2] debug: configured stub or forward servers failed -- returning SERVFAIL Jul 13 15:07:01 unbound 14038 [14038:2] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] info: query response was THROWAWAY Jul 13 15:07:01 unbound 14038 [14038:2] info: reply from <.> 9.9.9.9#853 Jul 13 15:07:01 unbound 14038 [14038:2] info: response for 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] debug: iterator[module 0] operate: extstate:module_wait_reply event:module_event_reply Jul 13 15:07:01 unbound 14038 [14038:2] debug: cache memory msg=90265 rrset=95647 infra=8306 val=0 Jul 13 15:07:01 unbound 14038 [14038:2] debug: sending to target: <.> 9.9.9.9#853 Jul 13 15:07:01 unbound 14038 [14038:2] info: sending query: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] info: query response was THROWAWAY Jul 13 15:07:01 unbound 14038 [14038:2] info: reply from <.> 9.9.9.9#853 Jul 13 15:07:01 unbound 14038 [14038:2] info: response for 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] debug: iterator[module 0] operate: extstate:module_wait_reply event:module_event_reply Jul 13 15:07:01 unbound 14038 [14038:2] debug: cache memory msg=90265 rrset=95647 infra=8306 val=0 Jul 13 15:07:01 unbound 14038 [14038:2] debug: sending to target: <.> 9.9.9.9#853 Jul 13 15:07:01 unbound 14038 [14038:2] info: sending query: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] info: query response was THROWAWAY Jul 13 15:07:01 unbound 14038 [14038:2] info: reply from <.> 9.9.9.9#853 Jul 13 15:07:01 unbound 14038 [14038:2] info: response for 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] debug: iterator[module 0] operate: extstate:module_wait_reply event:module_event_reply Jul 13 15:07:01 unbound 14038 [14038:2] debug: cache memory msg=90265 rrset=95647 infra=8306 val=0 Jul 13 15:07:01 unbound 14038 [14038:2] debug: sending to target: <.> 9.9.9.9#853 Jul 13 15:07:01 unbound 14038 [14038:2] info: sending query: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] info: query response was THROWAWAY Jul 13 15:07:01 unbound 14038 [14038:2] info: reply from <.> 149.112.112.112#853 Jul 13 15:07:01 unbound 14038 [14038:2] info: response for 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] debug: iterator[module 0] operate: extstate:module_wait_reply event:module_event_reply Jul 13 15:07:01 unbound 14038 [14038:2] debug: cache memory msg=90265 rrset=95647 infra=8306 val=0 Jul 13 15:07:01 unbound 14038 [14038:2] debug: sending to target: <.> 149.112.112.112#853 Jul 13 15:07:01 unbound 14038 [14038:2] info: sending query: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] info: processQueryTargets: 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] info: iterator operate: query 4.4.8.8.in-addr.arpa. PTR IN Jul 13 15:07:01 unbound 14038 [14038:2] debug: iterator[module 0] operate: extstate:module_wait_reply event:module_event_noreply Jul 13 15:07:01 unbound 14038 [14038:2] debug: tcp error for address 9.9.9.9 port 853 -
@maverickhl What if you uncheck "Use SSL/TLS for outgoing DNS Queries to Forwarding Servers"?
-
Wow.. that works... so why? I never had an issue enforcing TLS on DNS queries before? Not with Cloudfare at the very least....
-
Wait nvm lol... forgot to change it from Cloudflare for the test... ignore that previous post.
-
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 INI don't actually see it trying to resolve anything in your logs.
Steve
-
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 INSECUREQuad9 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 -
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 sawdebug: 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 ? -
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
-
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 -
Mmm, so exactly what settings do you have in System > General Setup and in Unbound?
