3 ms·
Thanks, this is useful. May I suggest trying different sets of public recursive resolvers for yourself to get the lowest query times? Just google "public DNS s
by seanp2k2 15y ago
Thanks, this is useful. May I suggest trying different sets of public recursive resolvers for yourself to get the lowest query times?
Just google "public DNS server" and start pinging them. For me, Verizon's name servers are the fastest; easy to remember too.
4.2.2.1
4.2.2.2
4.2.2.3
4.2.2.4
4.2.2.5
Opendns might work too but I've found it to be slow. Extra credit: set up a caching recursive resolver to serve your local net for web faster queries.
- pudquick 15y agoFor my iOS devices, the devices themselves are slow enough at rendering web content in MobileSafari that shaving a second or even two off the resolve is not so much a benefit. The real benefit for me was the CDN content coming through much much quicker for the App Store. iOS 5 has gotten so capable of managing content with iCloud and such that I rarely tether this to my laptop any more. As such, quickly downloading an app while on WiFi is very important, since anything over 20MB requires you be on WiFi to do it. I only came about this information by noticing that I was getting significantly higher download speeds from the App Store while at my parents' house on their WiFi than I was at home - yet we were both Comcast customers and I knew that I was paying for a slightly higher data package and had been able to perform 16Mbps sustained transfers on my laptop for non-App Store content routinely. So I copied down the Comcast DNS settings that my folks had and tried them out, manually, at home on my iPhone. The speed difference was almost immediately noticeable. Prior to that, I'd been using Google DNS servers 8.8.8.8 and 8.8.4.4. Just simply changing my DNS servers resulted in a much better performance. I'll have to shop around to see if I can tweak it even further :)
- X-Istence 15y agoAs far as I am aware; those are not Verizon's DNS servers but rather Level 3's anycast DNS servers. They are geographically located around the world and using anycast you go to whichever one happens to be closest to you. For most of America you end up in Dallas, TX, for the UK you end up in London, and for The Netherlands I was ending up in Amsterdam. I don't have access to more machines to do traceroutes to see what the last hops are, but you can easily check this for yourself with a traceroute and seeing what network it ends up at. Also, I was under the impression that their DNS servers technically require payment before use (as a commercial entity when handing out over DHCP) and are technically only for Level 3 customers. Everyone and their mother has started using them because they are easy to remember. Here is some more backstory of how the DNS server was originally set up: http://www.tummy.com/Community/Articles/famous-dns-server/ http://www.tummy.com/Community/Articles/famous-dns-server/
- burgerbrain 15y agoOpenDNS does NXDOMAIN fuckery, so there's really no point switching to them from comcast's default DNS servers. Edit: Downvotes or not, they still fuck with NXDOMAIN. Check for yourself.