News for hackers. Stuff that matters.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by akamaka on Thursday December 03, 2009 @04:15PM (#975243)
I tried using those servers, and they didn't work. If I do an nslookup or dig through them, it's fine, but when I use them as the default nameservers in my network configuration, they seem to reject my requests.

Anyone know why?

Re:Introducing Google Public DNS: A new DNS resolver from Go... by thaumaturgy on Thursday December 03, 2009 @07:31PM (#975523)
Try `nslookup -vc [hostname]` after setting your name servers to the Level3 IP.

Just a wild guess. I can't remember off the top of my head if nslookup or dig, when specifying an alternate server, use TCP or UDP. But, if it uses TCP for those, then it's possible that your ISP is blocking UDP DNS traffic that's not destined for their DNS servers. It wouldn't be the first time.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by akamaka on Friday December 04, 2009 @03:50PM (#977173)
Weird. It works now, unlike the last time I checked. Something must have changed, but I don't know what.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by pyre on Thursday December 03, 2009 @04:30PM (#975270)
Don't know. I usually set them as the default DNS servers for my router to hand out through DHCP.