Weird DNS resolution issue
-
@Dashrender said in Weird DNS resolution issue:
Was there something else I should have tried?
When troubleshooting you can make DNS queries to specific DNS servers that doesn't use the clients DHCP originated default DNS servers.
For example:
nslookup mangolassi.it 8.8.8.8
or
nslookup mangolassi.it 8.8.4.4
It would be better than just pinging.
You also have
ipconfig
as a tool on Windows.
To clear the clients DNS cacheipconfig /flushdns
to force DHCP renewal
ipconfig /renew
or to check what DNS server it has been given.
ipconfig /all
And look for "DNS Servers"
-
@Pete-S said in Weird DNS resolution issue:
@Dashrender said in Weird DNS resolution issue:
I ran into this yesterday.
Client has cable modem to TP Link router, TP Link is DHCP for network.
DHCP provides DNS addresses pointing to Comodo Secure DNS (8.26.56.26 and 8/20.247.20)Some computers are able to get DNS resolution - others cannot.
All computers can ping 8.8.8.8 - so internet works.
All computers can ping the Comodo DNS servers.Yet some computers just won't get DNS resolution.
I fixed the issue by changing the DHCP to hand out 8.8.8.8 and 8.8.4.4, rebooted the clients - problem gone.
Anyone heard of an issue like this? where a DNS provider seemingly blocks some requests from a given IP, but not others?
Was there something else I should have tried?Sounds like it might have been the reboot that actually solved the problem.
All requests from the LAN will originate from the routers WAN IP address so it will be the same IP from the DNS servers point of view. In other words, it's unlikely it's some problem on the DNS servers.
nah - I rebooted the computers myself - still no go.
I didn't personally reboot the router, but they replaced the cable modem and the router - and things still didn't work - so they put the old router back - all before I arrived.
-
@Pete-S said in Weird DNS resolution issue:
All requests from the LAN will originate from the routers WAN IP address so it will be the same IP from the DNS servers point of view. In other words, it's unlikely it's some problem on the DNS servers.
Right - which is why it was so weird why some machines got DNS responses and some did not.
-
@Pete-S said in Weird DNS resolution issue:
@Dashrender said in Weird DNS resolution issue:
Was there something else I should have tried?
When troubleshooting you can make DNS queries to specific DNS servers that doesn't use the clients DHCP originated default DNS servers.
For example:
nslookup mangolassi.it 8.8.8.8
or
nslookup mangolassi.it 8.8.4.4
It would be better than just pinging.
Nice - thanks didn't know that.
I did all the ipconfig stuff - no change... at least not until I change the DNS in the DHCP server.
-
@Dashrender said in Weird DNS resolution issue:
@Pete-S said in Weird DNS resolution issue:
@Dashrender said in Weird DNS resolution issue:
Was there something else I should have tried?
When troubleshooting you can make DNS queries to specific DNS servers that doesn't use the clients DHCP originated default DNS servers.
For example:
nslookup mangolassi.it 8.8.8.8
or
nslookup mangolassi.it 8.8.4.4
It would be better than just pinging.
Nice - thanks didn't know that.
Well, I don't do it often enough so I always forget how to do it and then I have to look it up...everytime....
-
@Dashrender said in Weird DNS resolution issue:
Anyone heard of an issue like this? where a DNS provider seemingly blocks some requests from a given IP, but not others?
It happens. Can be based on a lot of factors. Can also happen from your router.
-
@Pete-S said in Weird DNS resolution issue:
All requests from the LAN will originate from the routers WAN IP address so it will be the same IP from the DNS servers point of view. In other words, it's unlikely it's some problem on the DNS servers.
Right, it's far more likely to be UDP flooding on a per client basis.
-
@Dashrender said in Weird DNS resolution issue:
@Pete-S said in Weird DNS resolution issue:
All requests from the LAN will originate from the routers WAN IP address so it will be the same IP from the DNS servers point of view. In other words, it's unlikely it's some problem on the DNS servers.
Right - which is why it was so weird why some machines got DNS responses and some did not.
Unlikely, but still possible. Keep in mind that each machine on your network gets its own session. And each session can be on a different server on the DNS provider's end. So it might have been different servers that they were reaching.
-
@Pete-S said in Weird DNS resolution issue:
I usually let the router act as a DNS forwarder or resolver and cache.
Always this.
-
@JaredBusch said in Weird DNS resolution issue:
@Pete-S said in Weird DNS resolution issue:
I usually let the router act as a DNS forwarder or resolver and cache.
Always this.
meh - 6 of one!
I suppose it's possible that would have resolved this specific issue as the router would have been the only device making connections to the external DNS... but then again - it could have caused all machines to go without DNS when the upstream server stopped responding...
I didn't dig into the acient TP link router they had - they didn't want me to replace it with the newer Netgear they had once I got it working.
-
@Dashrender said in Weird DNS resolution issue:
I suppose it's possible that would have resolved this specific issue as the router would have been the only device making connections to the external DNS... but then again - it could have caused all machines to go without DNS when the upstream server stopped responding...
Not very likely. Plausible, but not likely enough to avoid it.
-
@scottalanmiller said in Weird DNS resolution issue:
@Dashrender said in Weird DNS resolution issue:
I suppose it's possible that would have resolved this specific issue as the router would have been the only device making connections to the external DNS... but then again - it could have caused all machines to go without DNS when the upstream server stopped responding...
Not very likely. Plausible, but not likely enough to avoid it.
sure - but then again, I've never seen this situation before either - so I would have previously called it unlikely.