Why using Google DNS / OpenDNS is a bad idea

Dan Warne
19 May 2010, 4:48 PM


Think you're getting faster performance by using Google DNS or OpenDNS? Think again -- especially if you're outside the US.


A post at TUAW today recommends you change your DNS provider for faster performance. If you are located outside the US -- like I am, and like most APC readers are -- this is a bad idea. I only discovered why after experiencing slow download speeds for several months.

Like other tech enthusiasts, I jumped on the opportunity to switch my computer's domain name server settings away from my ISP's defaults to -- I assumed -- the much larger and faster Google DNS servers at 8.8.8.8 and 8.8.4.4 when they were first announced.

If you're not familiar with what exactly DNS servers do, they translate the web address you type into your browser into the actual IP address of the internet server you're connecting to at the other end. For example, a DNS server will convert "apcmag.com" typed into your browser address bar into "125.7.5.1", which is the IP address of our server at Macquarie Telecom's datacentre.

DNS servers can be one cause (among many) of slowness in your web browsing, if your ISP's DNS server is overloaded and responding slowly -- you may experience a delay of seconds each time you go to a web address that your computer hasn't seen recently (and therefore has to connect to a DNS server to find out the correlating IP address).

This is one of the problems that third-party public DNS providers like Google DNS and OpenDNS are supposed to fix -- faster, more reliable lookups.

However, it was Simon Hackett, CEO of Internode, who I bumped into at a function who warned me off using third party DNS servers located overseas, such as Google DNS or OpenDNS. (By the way, if I've got any of the technical details wrong in this article, it's much more likely to be my fault than Simon's...!)

The key reason they're bad is that they stuff up your computer's ability to find the closest Akamai server to you. Akamai is the worldwide system which places massive file servers inside ISP data centres worldwide -- so that when you download a big file like a Windows or Mac OS X update, or a TV show or movie from iTunes, it downloads from a server that's very close to you, and therefore pumps down your line as fast as your ADSL2+ can handle. (The primary selling point of Akamai is that it avoids server overload when everyone tries to download something at once, but a secondary selling point is that you're downloading a file from a local server inside your ISP or at least in your country, so that the trip between the file server and you is as short/fast as possible.)

If you use a US-based DNS server, your closest Akamai cache will instead be chosen as being in the US, and you'll get crummy download speeds as your file trickles over the international link.

In my case, this meant that iTunes downloads were coming down at a couple of hundred kilobytes per second, rather than the 1.9MB/s I was accustomed to before I changed my DNS servers to Google DNS and OpenDNS.

Don't get me wrong -- there are some distinct advantages to using reliable servers from companies that specialise in providing DNS, like much faster refresh of their DNS records when new domains are registered, or websites change their IP addresses, DNS-level blocking of known phishing sites and so on.

But when they claim you'll get faster speed by using them, they're conveniently forgetting to mention that if you're not located in the US, they could badly slow down your speed when downloading from distributed caches like Akamai.

Admittedly, part of the problem is the design of Akamai -- it is, to an extent, a 'hack' of the DNS system (not in the illegal sense; but in the sense that they're using the DNS system in a way it was not quite designed for initially.) I have contacted Akamai's senior PR people twice and asked if they're investigating any way of mitigating the problem when people use DNS servers outside their local geography, but I haven't heard back.

Of course, if Google DNS, OpenDNS or other public DNS providers put servers into Australia, the problem would be largely gone. But until they do, my advice is to stick with the DNS provided by your ISP. To their credit, OpenDNS is reasonably up-front about this problem (though it's not something they advertise on their homepage, so most users wouldn't be aware of it.)

UPDATE: Phil Sweeney from Whirlpool reminded me that using a third-party DNS service can also screw up your ISP's quota free downloads. For example, iiNet provides unmetered downloads from Apple's iTunes Store, which is great if you like to buy TV series and rent/buy movies on iTunes. However, if you change your DNS to OpenDNS or Google DNS, you'll be pulling the content from an Akamai server overseas, rather than the one in iiNet's network that is designated for free downloads. As a result, you will be charged for those downloads.

Post your comment



Comments

RSS feed Email alert

Rob_B (New user):

Not to mention that when you download from a CDN cache not located at your ISP, they generally will have pay for the data rather than leveraging peering agreements with the likes of Akamai

19 May 2010, 5:04 PM (3 years ago)report abuse Send to a friend reply

Proprioio (New user):

As far as i know (i'm an OpenDNS user with my home pc), ODNS has two European servers located in London and Amsterdam (8 other located in US).

For European users, the "longest path" should normally resolve in Netherland or UK... certainly not as fast as your ISP ones (unless you live in those countries), but not as slow as a connection to US.

Other continents could have the problem described here... until ODNS will open up a server there (the two European servers were broadly asked for before being finally opened).

19 May 2010, 5:46 PM (3 years ago)report abuse Send to a friend reply

Proprioio (New user):

Server status page can be found here: http://system.opendns.com/

19 May 2010, 5:46 PM (3 years ago)report abuse Send to a friend reply

niknah (New user):

I recently had problems resolving a domain with my ISP (tpg), but I added the google dns to the bottom of my dnses and it resolved fine again. That's what they could be used for, as a backup.

Not all content providers run their own DNS, a lot just depend on the ip address from the web request which still comes from your location.

DNS servers don't use much bandwidth or computer CPU, but they send lots of little packets and can use a lot of the router's power and some routers don't let you see the CPU usage or it's hidden somewhere in the snmp so a lot of ISPs aren't aware that their router's CPU is overloaded.


19 May 2010, 5:52 PM (3 years ago)report abuse Send to a friend reply

Rob_B (New user):

TPGs DNS is broken. I can't even get to the Microsoft Update server using it.

20 May 2010, 9:22 AM (3 years ago)report abuse Send to a friend reply

Ausman (New user):

Good to know. Thanks for the article. I'm changing my DNS back...

20 May 2010, 4:01 AM (3 years ago)report abuse Send to a friend reply

Ido Safruti (New user):

You are referring to a very important problem with such external DNS services, the problem being that it breaks CDN implementations which are heavily based on DNS decisions to assign a client to the closest CDN datacenter. And as you stated - this could be critical as CDN usage is very popular, not only for large files as you stated, but also for news sites, social media, and almost any website or online service.
This concern was discussed right after Google released their DNS service, and resulted in Google (with other companies) suggesting an ietf draft to extend the DNS protocol to include client IP information in the DNS request (see http://www.ietf.org/id/draft-vandergaast-edns-client-ip-00.txt). Such an implementation will enable globally distributed services such as CDNs to provide the best response based on the original requesting client, and not based on the caching DNS's address.
Until this is implemented, it will be wise to check where the closest caching DNS server is (using traceroute for instance) before using such a service, and not generalizing for specific locations, as the DNS providers are extending their service and may deploy servers in more locations.
This is important also in US and Europe where both Google and opendns has servers, as it could be that the granularity such a service provides is still coarse with respect to the granularity of the CDN (consider that the DNS provider has servers in London and Amsterdam, a user coming from Germany may be served from a CDN PoP in Germany, but if using the DNS service will be served from London or Amsterdam instead).


20 May 2010, 5:18 AM (3 years ago)report abuse Send to a friend reply

Vax (New user):

The second google dns is not 4.4.4.4 it is actually 8.8.4.4

20 May 2010, 7:38 AM (3 years ago)report abuse Send to a friend reply

Dan Warne (Regular user):

Thanks very much for the pickup! I have fixed the article.

20 May 2010, 9:05 AM (3 years ago)report abuse Send to a friend reply

ozpeter (New user):

that is all true for downloads - but for general web browsing opendns is giving me a *much* better experience (than bigpond)...would be nice to set different dns for browsing vs download but that is too much hassle.

20 May 2010, 1:04 PM (3 years ago)report abuse Send to a friend reply

skaifey02 (New user):

how ironic

i changed to open dns following a recommendation in a previous article of apc! and now we are being told the opposite

22 May 2010, 5:27 PM (3 years ago)report abuse Send to a friend reply

skaifey02 (New user):

how ironic

in a previous apc magazine you guys recommended open dns which would be better peformance but now we read the opposite!

22 May 2010, 5:27 PM (3 years ago)report abuse Send to a friend reply

sajal (New user):

Some benchmarks on how OpenDNS, Google and default nameservers compare : http://www.sajalkayan.com/in-a-cdnd-world-opendns-is-the-enemy.html

If your ISP's nameservers are broken you can set up your own caching recirsive nameserver quite easily...

27 May 2010, 1:29 AM (2 years ago)report abuse Send to a friend reply

friskydiscus (New user):

This is an interesting issue that I had no idea about. Unfortunately some of us live in countries with absurd ideas about web censorship (as well as the nature of e-commerce) and services such as OpenDns and GoogleDNS are one of the few ways that allow us to access websites such as youtube, grooveshark, and many of google's services such as Google Sites and Google Groups.
Interestingly, it is not illegal for me to access these sites, it is the ISP which is obliged to block access to these sites by court order. So I am not breaking the law by using another DNS server to connect to those sites. The current censorship orders are used in two ways, either by morons intent on taking offence to everything published by anyone ever, or as a means for the authorities to "punish" businesses that they feel have not paid them sufficient respect, the emphasis being on "paid".
Anyway, I doubt anyone here cares much about countries with such a mind-bogglingly stupid approach to the internet, however the author does question the efficiency of OpenDNS and Google DNS to users outside of the US so the article does very much concern me, and I raise my point more to argue that not all of us access these DNS services simply for speed. Still its good to know they are adding servers in other countries but it would be even more useful to keep track of where these are.
Does anyone know whether OpenDNS or GoogleDNS keep updated information on the location of their DNS servers?

18 October 2010, 8:32 PM (2 years ago)report abuse Send to a friend reply

Mr Qwerty (New user):

I don't take DNS advice from people who don't understand that 125.7.5.1 is a private network IP address.

12 October 2011, 7:55 PM (1 year ago)report abuse Send to a friend reply

Rob_B (New user):

You're funny. And without clue.

13 October 2011, 9:32 AM (1 year ago)report abuse Send to a friend reply

Aaron Manzano (New user):

Hi,

I am a log time OpenDNS user and just saw this article.

Within Windows Active Directory (DNS) Infrastructure, you can specify a specific DNS Server for exceptional domains under forwarders. This will provide both the benefits of OpenDNS and Google DNS will removing the issues with AKAMAI.

This however is not a solution for the general home users unless they are using a router that can support binding domains to specific DNS servers.

AARON

12 May 2012, 12:54 PM (1 year ago)report abuse Send to a friend reply

The.Thig (New user):

Your confusing dns hosting with client dns resolution. The is no reason you domain hosted at open dns or google DNA should effect your home dns client machines. Unless you've completely miss configured your home systems. What is likely to be a problem is if your hosting a domain that is being cache by a cdn. The silly thing is that if this was the case then yo must be seriously cheap not to fork out the $40usd average you would need to host it properly.

Please learn a thing or two about Dns before making recommendations like the.



18 August 2012, 9:18 PM (9 months ago)report abuse Send to a friend reply

JM from San Jose (New user):

Google DNS and Open DNS seem to have resolved this issue:

http://lifehacker.com/5835775/google-dns-and-opendns-users-are-getting-a-web-speed-boost

07 February 2013, 12:52 PM (3 months ago)report abuse Send to a friend reply

anonymous user Anonymous user