DNS not resolving at all
Hi guys
I had a patch of time, where i was not getting DNS responses from nextdns.io.
it was so bad that I could not even open nextdns.io to see what the cause is.
times below from the log files from when I suspect the issue occurred
nslookup commands:
192.168.0.2 is my default gateway which has next DNS configured with a linked IP. no changes in nextdns configuration since last night.
Microsoft Windows [Version 10.0.19045.4170]
(c) Microsoft Corporation. All rights reserved.C:\Users\Erwin>nslookup www.google.com
Server: OPNsense.erwin.local
Address: 192.168.0.2*** OPNsense.erwin.local can't find www.google.com: Server failed
C:\Users\Erwin>nslookup www.google.com 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1Non-authoritative answer:
Name: www.google.com
Addresses: 2c0f:fb50:4002:809::2004
192.178.54.36C:\Users\Erwin>nslookup www.google.com 45.90.28.154
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 45.90.28.154DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-outC:\Users\Erwin>nslookup www.google.com 45.90.28.154
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 45.90.28.154DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-outC:\Users\Erwin>nslookup www.google.com 45.90.30.154
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 45.90.30.154DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-outC:\Users\Erwin>nslookup www.google.com 45.90.30.154
Server: dns2.nextdns.io
Address: 45.90.30.154Non-authoritative answer:
Name: www.google.com
Addresses: 2c0f:fb50:4002:812::2004
192.178.54.4
the weirder part is that the log file does not show then failed requests, even though I specifically targeted your DNS with nslookup.
Is there anything that could explain this behaviour?
I am looking to use nextdns in our company production environment, but having a few angry colleagues due to DNS failing to respond at all is not going to sell this implementation at all :)
Reply
Content aside
- 7 mths agoLast active
- 86Views
-
1
Following