There are reports floating about regarding third-party DNS affecting downloads of movies and other media, particularly from iTunes.
So, if tweaking DNS settings used to be what all the cool kids are doing, maybe it’s about to become less trendy, thanks to advice circulating to ditch third-party, centralized DNS providers like Google and OpenDNS, because they “defeat the distributed nature of DNS itself.”
The answer of what DNS to use and why is more complex than that.
Unfortunately iTunes is using DNS to determine your geographic location. So if I’m using Google’s DNS while I’m sitting here in Missouri, iTunes can make some determinations about what datacenter to route me to based on the incorrect assumption that I’m in California.
It’s curious to me that Apple is doing this, as there are other ways besides DNS to determine location. They aren’t foolproof (from work, depending on the situation, I can appear to be in Texas, Alabama, or Ohio when my office is actually in Illinois). But, obviously, using DNS isn’t foolproof either. DNS is user-changeable, and there are legitimate reasons for the end user to change it.
I think Apple and other companies that want to make their living streaming content are going to have to do some more work on this. Until they do, end users may have a little work to do on their end.
Perhaps using a large, centralized DNS isn’t a good idea if you subscribe to iTunes. But there’s also a decent chance that large, centralized DNS wasn’t the best one for you to be using in the first place. It wasn’t for me.
So who’s fastest?
The temptation is to change your DNS, do a few things, then try to decide if it’s faster than it was. And that can be deceiving. For one thing, you could experience the placebo effect. For another, whatever you’re doing could indeed be faster after the change, but because you have some content cached.
And some servers are faster for some things than others.
The only objective way to measure DNS speed is to use software. And software can test far, far more servers than you’ll want to run through on your own. Steve Gibson’s DNSBench, for instance, will run through literally thousands of known DNS servers, find the 50 that are the most promising, then extensively benchmark those to tell you which ones are the fastest to use.
What I’ve found is that the fastest to use might very well be run by my ISP, but not one of the ones it passes down through DHCP.
For example, I’ve run DNSBench on both my PC at home and on my mother-in-law’s PC at her house. We both have AT&T. The 3 fastest DNS servers for her aren’t the same as the ones for me.
The fastest servers for me, in fact, are one each from AT&T, Level 3, and Sprint. For my mother-in-law, who’s not in a major metro area, a different server from AT&T and OpenDNS were better.
What good is a faster DNS, anyway?
Any time you visit a site, the computer has to translate the human-readable address into a numeric address that computers and networking equipment understand. The faster that happens, the faster the page can start to display. If you think of it like a sports car, faster DNS will do nothing to improve the car’s top speed. It’s more like a black magic that improves 0 to 60 performance. Whether it improves it dramatically depends on how good your ISP is, but there’s no way for me to tell you that.
For web browsing, the difference can be noticeable. When you visit a web site, the text can be stored on one server at one address, and images stored on other servers at different addresses. The faster all those lookups happen, the faster it all displays.
Now when you’re streaming media, it’s less important, since there’s only one lookup, followed by a long, continuous stream of data. DNS makes a bigger difference with lots of bursty data, like web pages. But, chances are, if you’re streaming a lot of media, you’re probably spending a lot of time on the web too. And who doesn’t like it when their Internet connection is faster, especially when that improvement doesn’t cost anything to do?
So what should I do?
If you changed over to Google DNS or OpenDNS, I recommend running DNSBench to get an objective third-party opinion of what DNS you should be using. Especially if you’re experiencing a slowdown with iTunes.
DNSBench will most likely find you something better to use. Try switching to what it suggests. If iTunes is still slow, try switching to the fastest servers it finds that are run by your ISP. Those are still likely to be faster than the addresses it doles out via DHCP, and also likely to be geographically close enough to you as to not confuse iTunes. For that matter, it’s possible those servers will be geographically closer to you than whatever your ISP hands out over DHCP.