3
1
I have Netgear as router, NetGear itself has 8.8.8.8 set as prim dns. Windows is connected to NetGear and Ubuntu is, while I can
nslookup cf16.eu 8.8.8.8
(it goes on UDP/DNS) I get no response when do
dig @8.8.8.8 cf16.eu from Ubuntu. When +tcp flag is added and it goes on TCP/DNS there is a response.
What can be the problem here? I checked that I have always AD Bit flag set in Ubuntu queries, while this is not set on windows, and I cannot see any other differences in packet frames, ANY!. Does dnsmasq which is running on 127.0.1.1 (and it serves well direct requests on UDP) has something to do here?
4pie0
Posted 2013-05-08T19:10:06.560
Reputation: 353
1Google has explicitly stated that 8.8.8.8 was going to be their publicly available DNS. It should always "just work." – kmort – 2013-05-08T21:16:18.540
And it should hold an appropriately long cache and respond as resolver as fast as your local nameservers? I'm sure if the IETF thought that having a centralized public nameserver was best, they'd have wrote the DNS spec around a similar design. Long ago. But they haven't. Its not a good idea to use a distant resolver for all your DNS needs, even Google says its a good idea. – Nevin Williams – 2013-05-09T10:13:38.600
I don't recall them saying anything about speed. I think the idea was more that when your small ISP's DNS goes down, you're not dead in the water because there is an easy to remember DNS at 8.8.8.8. You are, of course, completely correct about caching and speed, but it should work in a pinch. – kmort – 2013-05-09T11:55:02.347
I'm also looking at the number of people having trouble with 8.8.8.8 in some manner or another. – Nevin Williams – 2013-05-09T12:59:23.030