6 ms·
iTunes Store Slowdowns With Google DNS
- 10smom 16y agoSo how do you turn off google DNS? (If it is even on)
- liuhenry 16y agoIt won't be on by default, you have to enable it (http://code.google.com/speed/public-dns/docs/using.html http://code.google.com/speed/public-dns/docs/using.html) You can check by opening a command line (Run -> cmd) and doing a "tracert random web site.com" (or Terminal, then traceroute in OSX/mtr in linux). If it doesn't come back with 8.8.8.8 or 8.8.4.4 as any of the servers (should be in the first few), you're not using Google's DNS servers. Otherwise, remove the servers and revert to automatic or ISP settings (instructions are at the bottom of Google's doc). EDIT: Sorry, confused DNS server with my ISP connection node. Check out the explanation by jonburs below.
- jonburs 16y agoThe traceroute family doesn't show DNS info; they show intermediate routers on the path the the resolved destination address. The early servers are the local routers in your ISP's topology, not the DNS server used to resolve the destination address. A tool such as dig, on the other hand, will show you what server you're using, and easily see the results from an alternate. For example, compare the results of 'dig www.apple.com' (configured DNS) to 'dig www.apple.com @8.8.8.8' (Google DNS).
- liuhenry 16y agoAh, whoops - thanks for the correction. Quick question: dig (with no @server argument) turns up my router's IP. Is there a way to get around that?
- jonburs 16y agoThat would happen if your router is providing DHCP services (common) and returning itself as the DNS server. A good reason for that configuration is so that you can resolve the names of other computers on your local network. If that's the case there's a good chance your router's admin interface will let you view and configure the DNS server its resolver is using.
- MetricMike 16y agoTo use Google's DNS servers you have to put their IP addresses manually into your network settings (http://code.google.com/speed/public-dns/docs/using.html http://code.google.com/speed/public-dns/docs/using.html). If you don't set these, or set them back to using the "default" you'll use your ISP's local DNS servers instead.
- jbrennan 16y agoI've always been a fan of: 4.2.2.1 and I believe it has a family of DNS servers in a similar range. Has never let me down (whereas my ISP, Rogers, has done so countless times).
- blasdel 16y agoI use Level3's DNS servers also, but they're also distributed with anycast routing and would likely suffer from the same interaction.
- evgen 16y agoIt is not the fact that they dns server is using anycast routing that is the problem, it is the fact that the dns provider does not have a widely distributed set of POPs. When you send out a dns query to google dns or opendns you are going to a small set of boxes, the anycast address will route you to the closest one in this set but it is unlikely that any of the POPs are actually close to you. Level3 has a widely distributed set of POPs and if you are going to use a dns service that is not provided by your ISP this is probably the one to use.
- deleted 16y ago[deleted]
- willscott 16y agoI don't understand this at all. Is there any reasonable theory for how the choice of DNS changes download speed this dramatically? I can see it taking longer to resolve the ip address of the download server, but that should only be a one-time thing - and the total impact should be a couple seconds at most. Unless the download is constantly flipping between servers, I don't see how DNS latency is going to make a noticeable difference in the time it takes to download / stream a movie.
- BigZaphod 16y agoI think the deal is that it's returning an IP from the lookup based on the IP of the DNS server that's making the request. This is so it returns a server that's closer to your network. If your DNS request is going through Google, it's going to return a server that's close to Google's DNS server and not your own ISP's DNS server (which would of course be much closer to you networkingly-speaking).
- cheald 16y agoCorrect. Using a DNS service like Google's can reduce throughput from location-aware CDNs, since you end up reading off of a CDN edge very far away from you.
- fleitz 16y agoIncorrect, the CDN is not location aware if it's using DNS. It's making a bunch of unnecessary assumptions about a DNS server's network proximity to the clients it serves. The root servers themselves run on Anycast so that you can get a 'root server' closest to your network location. A much better way of locating a resource on the network is its IP address, since this is what IP was designed to do and not what DNS is designed to do (resolve names to IP addresses) DNS is designed to be forwarded and cached. A much better way of optimizing network routes is to advertise a better route, since this is what routing was designed to do. (To pick the fastest way to get from your IP to a destination block. (aka. anycast.)) It's simply amazing how well things work when you use things for what they were intended for. Why reinvent the wheel at such a high level?
- nnutter 16y agoI can definitely attest to having this type of experience. My first time trying to rent a movie was quite miserable. I first tried renting it from iTunes like I do TV shows which apparently doesn't work. I then started streaming it from the Apple TV and was greeted with these wait times a couple times during the movie. I can't wait to try experimenting with this to see if that was indeed the cause.
- ajkirwin 16y agoMore pointless wittering from John Gruber. "Oh, well, it MUST be Google's DNS. It can't be a problem with my precious Apple and how they handle things with their CDN!"
- jacobbijani 16y agoMine says this with the default DNS settings too. It starts a few minutes later anyway.
- maguay 16y agoAnyone seen any problems with OpenDNS? iTunes Store has been running extremely slow for me over the last several days for no apparent reason...
- foobarbazetc 16y agoOpenDNS suffers from the exact same issue.
- the100rabh 16y agoSo Grubber found another problem with Google. Never finds flaws with Apple ever. Does he ?? Does he even care to explain why its happening. This is just shoddy blogging. DNS does not take more than a few secs and once the connection between servers is established, DNS Servers are out of the picture. So whose fault is it, Google or Apple ??? Not very difficult to guess I think
- beej71 16y agohttp://code.google.com/speed/public-dns/faq.html#locations http://code.google.com/speed/public-dns/faq.html#locations "Here are the subnets from which Google Public DNS sends requests to authoritative nameservers, and their associated IATA airport codes" So in theory, if you live in one of those cities, you shouldn't have this problem. Right? Some of the reported numbers are too astounding to be covered by this explanation, however. I wonder if something else is at work.
- petercooper 16y agoGoogle's DNS is a pain in the ass. They either go OTT with the caching or it's really slow to deal with nameserver changes as I've encountered this myself (when all other servers I tested were OK) and advised people on IRC with similar issues.