Use Domain Override to have a site resolve with google instead of Unbound?
-
Just because you do not have it configured doesn't mean pfsense is not using it.. Does your isp hand you an ipv6 address on your wan?
Do simple query to their ns direct via dig or nslookup.. What is your response time? Do you get an answer.. keep in mind that www.aviationweather.gov is cname that points to
;; ANSWER SECTION:
www.aviationweather.gov. 120 IN CNAME aviationweather.ncep.noaa.gov.
aviationweather.ncep.noaa.gov. 300 IN CNAME aviationweather.cp.ncep.noaa.gov.
aviationweather.cp.ncep.noaa.gov. 86400 IN A 140.90.101.207 -
Does your isp hand you an ipv6 address on your wan?
Yes, if I turn on DHCP6 on WAN I get issued an ipv6 address, I had thought that if that was set to none that I wouldn't be using ipv6 over the internet?
Do simple query to their ns direct via dig or nslookup.. What is your response time?
Looks like ~77ms
[2.4.0-BETA][admin@netbox.netdomain]/root: dig 140.90.33.237 ; <<>> DiG 9.11.0-P3 <<>> 140.90.33.237 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42083 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;140.90.33.237. IN A ;; AUTHORITY SECTION: . 2213 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2017031801 1800 900 604800 86400 ;; Query time: 78 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sat Mar 18 10:56:30 PDT 2017 ;; MSG SIZE rcvd: 117 [2.4.0-BETA][admin@netbox.netdomain]/root: dig aviationweather.gov @140.90.33.237 ; <<>> DiG 9.11.0-P3 <<>> aviationweather.gov @140.90.33.237 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54013 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 7 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;aviationweather.gov. IN A ;; ANSWER SECTION: aviationweather.gov. 120 IN A 140.90.101.207 ;; AUTHORITY SECTION: aviationweather.gov. 120 IN NS ns-nw.noaa.gov. aviationweather.gov. 120 IN NS ns-mw.noaa.gov. aviationweather.gov. 120 IN NS ns-e.noaa.gov. ;; ADDITIONAL SECTION: ns-e.noaa.gov. 86400 IN A 140.90.33.237 ns-e.noaa.gov. 86400 IN AAAA 2610:20:8000:8c00::237 ns-mw.noaa.gov. 86400 IN A 140.172.17.237 ns-mw.noaa.gov. 86400 IN AAAA 2610:20:8800:8c00::237 ns-nw.noaa.gov. 86400 IN A 161.55.32.2 ns-nw.noaa.gov. 86400 IN AAAA 2610:20:8c00:8c00::2 ;; Query time: 76 msec ;; SERVER: 140.90.33.237#53(140.90.33.237) ;; WHEN: Sat Mar 18 10:56:50 PDT 2017 ;; MSG SIZE rcvd: 260 -
so that sure looks like it works to me.. So just make sure pfsense is not using ipv6 and you shouldn't have any issues. Set your wan to none.
Not sure why you think you need to do overrrides. Query that for www.avaiationweather.gov do you get an answer?
-
It was set to none and is now, I just turned it on so I could answer your question as to whether my ISP is providing an ipv6 address or not. My pfsense box had never used ipv6 though.
x@x-TPadT420:~$ dig aviationweather.gov ; <<>> DiG 9.10.3-P4-Ubuntu <<>> aviationweather.gov ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48639 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;aviationweather.gov. IN A ;; ANSWER SECTION: aviationweather.gov. 68 IN A 140.90.101.207 ;; Query time: 1 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Sat Mar 18 14:03:33 PDT 2017 ;; MSG SIZE rcvd: 64 x@x-TPadT420:~$ dig www.aviationweather.gov ; <<>> DiG 9.10.3-P4-Ubuntu <<>> www.aviationweather.gov ;; global options: +cmd ;; connection timed out; no servers could be reached -
";; SERVER: 127.0.1.1#53(127.0.1.1)"
That sure and the hell is not pfsense..
Query your pfsense directly.. You got a caching dnsmasq running on that box.. That is asking what??? Have no idea what its forwarding too..
Do a query to your pfsense directly - with your domain overrides removed!!!
like this..
dig @192.168.9.253 www.aviationweather.gov
; <<>> DiG 9.11.0-P3 <<>> @192.168.9.253 www.aviationweather.gov
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5562
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 3, AUTHORITY: 3, ADDITIONAL: 1;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.aviationweather.gov. IN A;; ANSWER SECTION:
www.aviationweather.gov. 120 IN CNAME aviationweather.ncep.noaa.gov.
aviationweather.ncep.noaa.gov. 300 IN CNAME aviationweather.cp.ncep.noaa.gov.
aviationweather.cp.ncep.noaa.gov. 67481 IN A 140.90.101.207;; AUTHORITY SECTION:
ncep.noaa.gov. 67481 IN NS ns-e.noaa.gov.
ncep.noaa.gov. 67481 IN NS ns-mw.noaa.gov.
ncep.noaa.gov. 67481 IN NS ns-nw.noaa.gov.;; Query time: 156 msec
;; SERVER: 192.168.9.253#53(192.168.9.253)
;; WHEN: Sat Mar 18 16:29:42 Central Daylight Time 2017
;; MSG SIZE rcvd: 200replace that 192.168.9.253 with whatever pfsense IP is on your lan/network your on..
-
x@x-TPadT420:~$ dig @192.168.1.1 www.aviationweather.gov ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @192.168.1.1 www.aviationweather.gov ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached x@x-TPadT420:~$ dig @192.168.1.1 aviationweather.gov ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @192.168.1.1 aviationweather.gov ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached x@x-TPadT420:~$ dig @192.168.1.1 www.google.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @192.168.1.1 www.google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32878 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;www.google.com. IN A ;; ANSWER SECTION: www.google.com. 3600 IN A 216.239.38.120 ;; Query time: 1 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Sat Mar 18 14:37:34 PDT 2017 ;; MSG SIZE rcvd: 59 -
And did you clear out the domain overrides you were messing with??
Can you talk to their NS directly - you did that previous.. So you got something else going on if you can still talk to them..
Troubleshooting.. What is your unbound log showing you when you up its verbosity? What is simple sniff on your wan showing you when you try and resolve this fqdn? I am having zero issues resolving this domain and that www record.
Its quite possible your having issues talking to their NS via something wrong with your isp, or your path to those networks.. Tracking that down is simple enough..
So what happens when you try and resolve it via pfsense diag, dns lookup?
-
And did you clear out the domain overrides you were messing with??
Can you talk to their NS directly - you did that previous.. So you got something else going on if you can still talk to them..
Yes, I deleted the domain override.
Here's an output that includes the NS:
; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> www.aviation.gov ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 60388 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;www.aviation.gov. IN A ;; AUTHORITY SECTION: gov. 3312 IN SOA a.gov-servers.net. nstld.verisign-grs.com. 1489943401 3600 900 1814400 86400 ;; Query time: 0 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Sun Mar 19 10:47:21 DST 2017 ;; MSG SIZE rcvd: 120 bash@DESKTOP:~$ dig aviation.gov ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> aviation.gov ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 397 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;aviation.gov. IN A ;; AUTHORITY SECTION: gov. 3308 IN SOA a.gov-servers.net. nstld.verisign-grs.com. 1489943401 3600 900 1814400 86400 ;; Query time: 0 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Sun Mar 19 10:47:25 DST 2017 ;; MSG SIZE rcvd: 116 bash@DESKTOP:~$ dig 140.90.33.237 ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> 140.90.33.237 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10308 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;140.90.33.237. IN A ;; AUTHORITY SECTION: . 1751 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2017031901 1800 900 604800 86400 ;; Query time: 15 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Sun Mar 19 10:47:29 DST 2017 ;; MSG SIZE rcvd: 117 bash@DESKTOP:~$ dig a.root-servers.net ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> a.root-servers.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54421 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 26 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;a.root-servers.net. IN A ;; ANSWER SECTION: a.root-servers.net. 3599961 IN A 198.41.0.4 ;; AUTHORITY SECTION: root-servers.net. 3599961 IN NS b.root-servers.net. root-servers.net. 3599961 IN NS f.root-servers.net. root-servers.net. 3599961 IN NS i.root-servers.net. root-servers.net. 3599961 IN NS a.root-servers.net. root-servers.net. 3599961 IN NS e.root-servers.net. root-servers.net. 3599961 IN NS g.root-servers.net. root-servers.net. 3599961 IN NS l.root-servers.net. root-servers.net. 3599961 IN NS m.root-servers.net. root-servers.net. 3599961 IN NS d.root-servers.net. root-servers.net. 3599961 IN NS c.root-servers.net. root-servers.net. 3599961 IN NS h.root-servers.net. root-servers.net. 3599961 IN NS j.root-servers.net. root-servers.net. 3599961 IN NS k.root-servers.net. ;; ADDITIONAL SECTION: b.root-servers.net. 516543 IN A 192.228.79.201 c.root-servers.net. 516543 IN A 192.33.4.12 d.root-servers.net. 516543 IN A 199.7.91.13 e.root-servers.net. 516543 IN A 192.203.230.10 f.root-servers.net. 516543 IN A 192.5.5.241 g.root-servers.net. 516543 IN A 192.112.36.4 h.root-servers.net. 516543 IN A 198.97.190.53 i.root-servers.net. 516543 IN A 192.36.148.17 j.root-servers.net. 516543 IN A 192.58.128.30 k.root-servers.net. 516543 IN A 193.0.14.129 l.root-servers.net. 516543 IN A 199.7.83.42 m.root-servers.net. 516543 IN A 202.12.27.33 a.root-servers.net. 516543 IN AAAA 2001:503:ba3e::2:30 b.root-servers.net. 516543 IN AAAA 2001:500:84::b c.root-servers.net. 516543 IN AAAA 2001:500:2::c d.root-servers.net. 516543 IN AAAA 2001:500:2d::d e.root-servers.net. 516543 IN AAAA 2001:500:a8::e f.root-servers.net. 516543 IN AAAA 2001:500:2f::f g.root-servers.net. 516543 IN AAAA 2001:500:12::d0d h.root-servers.net. 516543 IN AAAA 2001:500:1::53 i.root-servers.net. 516543 IN AAAA 2001:7fe::53 j.root-servers.net. 516543 IN AAAA 2001:503:c27::2:30 k.root-servers.net. 516543 IN AAAA 2001:7fd::1 l.root-servers.net. 516543 IN AAAA 2001:500:9f::42 m.root-servers.net. 516543 IN AAAA 2001:dc3::35 ;; Query time: 46 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Sun Mar 19 10:47:35 DST 2017 ;; MSG SIZE rcvd: 825I attached a screen of the pfsense diag lookup output.
Troubleshooting.. What is your unbound log showing you when you up its verbosity? What is simple sniff on your wan showing you when you try and resolve this fqdn? I am having zero issues resolving this domain and that www record.
Verb=5 was outputting a ton of stuff and filling up the 500 entries in less than a second.
I thought I'd be clever and clear out the resolver.log file so that I could just post the relevant stuff for you. (Diag>Edit File>Select All>Delete>Save)
Apparently that's not smart to do because now it doesn't put anything in there… :o
I tried restarting Resolver, rebooting, updating to latest BETA build, rm /var/log/resolver.log && touch /var/log/resolver.log
It still isn't logging anything.Way to go me.
-
Try this at a shell prompt:
rm /var/log/resolver.log
ls -l /var/log
Get the size of the other logs default is 511488
clog -i -s 511488 /var/log/resolver.log
chmod 600 /var/log/resolver.log
bounce unbound
-
Try this at a shell prompt:
rm /var/log/resolver.log
ls -l /var/log
Get the size of the other logs default is 511488
clog -i -s 511488 /var/log/resolver.log
chmod 600 /var/log/resolver.log
bounce unbound
Thanks! That did the trick! I had assumed that they were just ordinary text files but that makes a lot more sense haha.
Strangely enough….. now my DNS query return is different AND www.aviationweather.gov loads immediately with no problems... :o
The only thing I did different than the last post is accidentally screw up my resolver.log and then get it back up with Derelicts instruction.
Why would a log have any effect at all? Assuming it must have been something else but I can't imagine what? I had already restarted Unbound & rebooted the system a couple of times so that wasn't new.
dig is different now too:
bash@DESKTOP:~$ dig www.aviationweather.gov ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> www.aviationweather.gov ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26880 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 3, AUTHORITY: 3, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;www.aviationweather.gov. IN A ;; ANSWER SECTION: www.aviationweather.gov. 120 IN CNAME aviationweather.ncep.noaa.gov. aviationweather.ncep.noaa.gov. 7 IN CNAME aviationweather.cp.ncep.noaa.gov. aviationweather.cp.ncep.noaa.gov. 86107 IN A 140.90.101.207 ;; AUTHORITY SECTION: ncep.noaa.gov. 86107 IN NS ns-e.noaa.gov. ncep.noaa.gov. 86107 IN NS ns-mw.noaa.gov. ncep.noaa.gov. 86107 IN NS ns-nw.noaa.gov. ;; Query time: 115 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Sun Mar 19 12:26:55 DST 2017 ;; MSG SIZE rcvd: 200 bash@DESKTOP:~$ dig ns-e.noaa.gov ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> ns-e.noaa.gov ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44300 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 6 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;ns-e.noaa.gov. IN A ;; ANSWER SECTION: ns-e.noaa.gov. 86079 IN A 140.90.33.237 ;; AUTHORITY SECTION: noaa.gov. 86400 IN NS ns-e.noaa.gov. noaa.gov. 86400 IN NS ns-mw.noaa.gov. noaa.gov. 86400 IN NS ns-nw.noaa.gov. ;; ADDITIONAL SECTION: ns-e.noaa.gov. 86079 IN AAAA 2610:20:8000:8c00::237 ns-mw.noaa.gov. 86079 IN A 140.172.17.237 ns-mw.noaa.gov. 86079 IN AAAA 2610:20:8800:8c00::237 ns-nw.noaa.gov. 86079 IN A 161.55.32.2 ns-nw.noaa.gov. 86079 IN AAAA 2610:20:8c00:8c00::2 ;; Query time: 74 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Sun Mar 19 12:27:23 DST 2017 ;; MSG SIZE rcvd: 228
-
It wasn't the log. It is probably just resolving for you now.
-
May never know what what going on, since you can not seem to grasp how to do a directed query.. In all the nonsense you posted.. Not one of them was a query to one of the NS authoritative for that domain…
Just like you query @yourpfsenseIP
Do you query direct to one of their NS.. as I did in my example.. And why and the F are you doing a query for "www.aviation.gov"
Glad its working for you - since troubleshooting to where the problem actual is with what your posting would be fruitless..
-
May never know what what going on, since you can not seem to grasp how to do a directed query.. In all the nonsense you posted.. Not one of them was a query to one of the NS authoritative for that domain…
Just like you query @yourpfsenseIP
Do you query direct to one of their NS.. as I did in my example.. And why and the F are you doing a query for "www.aviation.gov"
Glad its working for you - since troubleshooting to where the problem actual is with what your posting would be fruitless..
Eh, yeah. I have literally zero background in IT or anything computer or networking related. If I haven't read it for fun or been told something, I don't know it. So it doesn't surprise me I got it wrong, I do apologize though, I appreciate that you've taken your time out to help me.
I was querying aviationweather.gov because it's the only site that I've ever had trouble with, and the reason I started this thread.
EDIT: reading back I see you mean why i mistyped "aviation.gov" instead of "aviationweather.gov" and posted that output, that was totally unintentional, I was tired!I thought that the following was the Name Server for aviationweather.gov (which is what I assumed you meant by NS?)since it was listed in the return for aviationweather.gov, and start with "ns".
bash@DESKTOP:~$ dig ns-e.noaa.govI don't even know what you mean by this?
Just like you query @yourpfsenseIP
I think the only IP i queried was:
bash@DESKTOP:~$ dig 140.90.33.237Network information
IP address 140.90.33.237
Reverse DNS (PTR record) ns-e.noaa.govIs that what you mean?
I'd be happy to learn if you're willing to educate me, but I also totally understand if you're no longer interested.
Either way, thank you for taking your time and I apologize for the frustration. -
"dig 140.90.33.237"
All that did was query you default dns for that IP..
Thee are 3 NS listed for this domain.. If you want to ask them directly then you would use the @
So
dig @140.90.33.237 then what you want to ask it..
so
dig @140.90.33.237 www.aviationweather.gov
dig @140.90.33.237 www.aviationweather.gov
; <<>> DiG 9.11.0-P3 <<>> @140.90.33.237 www.aviationweather.gov
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9718
;; flags: qr aa rd; QUERY: 1, ANSWER: 3, AUTHORITY: 3, ADDITIONAL: 7
;; WARNING: recursion requested but not available;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.aviationweather.gov. IN A;; ANSWER SECTION:
www.aviationweather.gov. 120 IN CNAME aviationweather.ncep.noaa.gov.
aviationweather.ncep.noaa.gov. 300 IN CNAME aviationweather.cp.ncep.noaa.gov.
aviationweather.cp.ncep.noaa.gov. 86400 IN A 140.90.101.207;; AUTHORITY SECTION:
ncep.noaa.gov. 86400 IN NS ns-mw.noaa.gov.
ncep.noaa.gov. 86400 IN NS ns-nw.noaa.gov.
ncep.noaa.gov. 86400 IN NS ns-e.noaa.gov.;; ADDITIONAL SECTION:
ns-e.noaa.gov. 86400 IN A 140.90.33.237
ns-e.noaa.gov. 86400 IN AAAA 2610:20:8000:8c00::237
ns-mw.noaa.gov. 86400 IN A 140.172.17.237
ns-mw.noaa.gov. 86400 IN AAAA 2610:20:8800:8c00::237
ns-nw.noaa.gov. 86400 IN A 161.55.32.2
ns-nw.noaa.gov. 86400 IN AAAA 2610:20:8c00:8c00::2;; Query time: 35 msec
;; SERVER: 140.90.33.237#53(140.90.33.237)
;; WHEN: Mon Mar 20 05:19:59 Central Daylight Time 2017
;; MSG SIZE rcvd: 332 -
OK, thank you! It is once again not working for me.
bash@DESKTOP:~$ dig @140.90.33.237 www.aviationweather.gov ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> @140.90.33.237 www.aviationweather.gov ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reachedI also attached the resolver log.
[dns resolver log.zip](/public/imported_attachments/1/dns resolver log.zip)
-
Well that dig command says you could not reach that NS
"connection timed out; no servers could be reached"
So its either down, or your isp is having issues talking to that network. I do not show any problems talking to any of them.. Try one of the 2 others ones..
ns-e.noaa.gov. 86400 IN A 140.90.33.237
ns-mw.noaa.gov. 86400 IN A 140.172.17.237
ns-nw.noaa.gov. 86400 IN A 161.55.32.2dig @140.90.33.237 www.aviationweather.gov +short
aviationweather.ncep.noaa.gov.
aviationweather.cp.ncep.noaa.gov.
140.90.101.207dig @140.172.17.237 www.aviationweather.gov +short
aviationweather.ncep.noaa.gov.
aviationweather.cp.ncep.noaa.gov.
140.90.101.207dig @161.55.32.2 www.aviationweather.gov +short
aviationweather.ncep.noaa.gov.
aviationweather.cp.ncep.noaa.gov.
140.90.101.207Simple solution would be prob to just put in a host override for www.aviationweather.gov to point to the IP 140.90.101.207, while they have a really short ttl 120 seconds, and then 300 seconds for that cname the IP has not changed since this thread has started 140.90.101.207..
edit: BTW I don't see anything in that log for aviationweather.gov
If you queried it directly unbound would not have any knowledge of that or log that..
-
Yeah it's down for me again. I don't get why I can't get to those DNS servers?
bash@DESKTOP:~$ dig @140.90.33.237 ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> @140.90.33.237 ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3772 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;. IN NS ;; ANSWER SECTION: . 77610 IN NS e.root-servers.net. . 77610 IN NS k.root-servers.net. . 77610 IN NS l.root-servers.net. . 77610 IN NS g.root-servers.net. . 77610 IN NS c.root-servers.net. . 77610 IN NS i.root-servers.net. . 77610 IN NS f.root-servers.net. . 77610 IN NS h.root-servers.net. . 77610 IN NS j.root-servers.net. . 77610 IN NS d.root-servers.net. . 77610 IN NS m.root-servers.net. . 77610 IN NS b.root-servers.net. . 77610 IN NS a.root-servers.net. ;; Query time: 0 msec ;; SERVER: 140.90.33.237#53(140.90.33.237) ;; WHEN: Tue Mar 21 10:55:07 DST 2017 ;; MSG SIZE rcvd: 239 bash@DESKTOP:~$ dig @140.172.17.237 ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> @140.172.17.237 ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41634 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;. IN NS ;; ANSWER SECTION: . 77590 IN NS e.root-servers.net. . 77590 IN NS k.root-servers.net. . 77590 IN NS l.root-servers.net. . 77590 IN NS g.root-servers.net. . 77590 IN NS c.root-servers.net. . 77590 IN NS i.root-servers.net. . 77590 IN NS f.root-servers.net. . 77590 IN NS h.root-servers.net. . 77590 IN NS j.root-servers.net. . 77590 IN NS d.root-servers.net. . 77590 IN NS m.root-servers.net. . 77590 IN NS b.root-servers.net. . 77590 IN NS a.root-servers.net. ;; Query time: 15 msec ;; SERVER: 140.172.17.237#53(140.172.17.237) ;; WHEN: Tue Mar 21 10:55:27 DST 2017 ;; MSG SIZE rcvd: 239 bash@DESKTOP:~$ dig @161.55.32.2 ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> @161.55.32.2 ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51936 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;. IN NS ;; ANSWER SECTION: . 77571 IN NS e.root-servers.net. . 77571 IN NS k.root-servers.net. . 77571 IN NS l.root-servers.net. . 77571 IN NS g.root-servers.net. . 77571 IN NS c.root-servers.net. . 77571 IN NS i.root-servers.net. . 77571 IN NS f.root-servers.net. . 77571 IN NS h.root-servers.net. . 77571 IN NS j.root-servers.net. . 77571 IN NS d.root-servers.net. . 77571 IN NS m.root-servers.net. . 77571 IN NS b.root-servers.net. . 77571 IN NS a.root-servers.net. ;; Query time: 15 msec ;; SERVER: 161.55.32.2#53(161.55.32.2) ;; WHEN: Tue Mar 21 10:55:46 DST 2017 ;; MSG SIZE rcvd: 239 bash@DESKTOP:~$ dig @140.90.33.237 www.aviationweather.gov +short ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> @140.90.33.237 www.aviationweather.gov +short ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached bash@DESKTOP:~$ dig @140.172.17.237 www.aviationweather.gov +short ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> @140.172.17.237 www.aviationweather.gov +short ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached bash@DESKTOP:~$ dig @161.55.32.2 www.aviationweather.gov +short ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> @161.55.32.2 www.aviationweather.gov +short ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached bash@DESKTOP:~$ dig 140.90.101.207 ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> 140.90.101.207 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 22888 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;140.90.101.207. IN A ;; AUTHORITY SECTION: . 3287 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2017032102 1800 900 604800 86400 ;; Query time: 31 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Tue Mar 21 10:57:50 DST 2017 ;; MSG SIZE rcvd: 118 -
If you can not get to those servers then yeah your not going to be able to resolve records they are authoritative for. And since the ttl they have on them are very short.. This problem is going to come up all the time..
Can you ping them??
-
No, I cannot ping them.
>ping 140.90.33.237 Pinging 140.90.33.237 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 140.90.33.237: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), >ping 140.172.17.237 Pinging 140.172.17.237 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 140.172.17.237: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), >ping 161.55.32.2 Pinging 161.55.32.2 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 161.55.32.2: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), >ping 140.90.101.207 Pinging 140.90.101.207 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 140.90.101.207: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), >ping 139.130.4.5 Pinging 139.130.4.5 with 32 bytes of data: Reply from 139.130.4.5: bytes=32 time=169ms TTL=114 Reply from 139.130.4.5: bytes=32 time=171ms TTL=114 Reply from 139.130.4.5: bytes=32 time=168ms TTL=114 Reply from 139.130.4.5: bytes=32 time=169ms TTL=114 Ping statistics for 139.130.4.5: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 168ms, Maximum = 171ms, Average = 169ms >ping 8.8.8.8 Pinging 8.8.8.8 with 32 bytes of data: Reply from 8.8.8.8: bytes=32 time=48ms TTL=60 Reply from 8.8.8.8: bytes=32 time=47ms TTL=60 Reply from 8.8.8.8: bytes=32 time=47ms TTL=60 Reply from 8.8.8.8: bytes=32 time=47ms TTL=60 Ping statistics for 8.8.8.8: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 47ms, Maximum = 48ms, Average = 47ms >ping 4.2.2.2 Pinging 4.2.2.2 with 32 bytes of data: Reply from 4.2.2.2: bytes=32 time=15ms TTL=55 Reply from 4.2.2.2: bytes=32 time=14ms TTL=55 Reply from 4.2.2.2: bytes=32 time=14ms TTL=55 Reply from 4.2.2.2: bytes=32 time=13ms TTL=55 Ping statistics for 4.2.2.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 15ms, Average = 14ms -
well that is a bad test - I should of tried pinging them first before suggesting that.. they don't seem to answer ping.. But not having any problems doing dns queries to them..
