Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Cloud DNS

developers.google.com

Post reply on HN
Print view View original

41–50 of 87 posts

Re: Google Cloud DNS

#41

Post by tedivm »

BorisMelnik wrote: post #39
tedivm wrote: post #29

Earlier quoted context omitted.

You're an Australian Internet User. You want to see hampsterdance.com 'cause fuck it, you like hamsters. Your computer asks your ISP's DNS server for the record. If your ISP has it cached you're golden, but it turns out it probably isn't. So your ISP needs to go to ask the hampsterdance.com DNS server directly. If that server is in the United States then you're stuck waiting 133ms in one direction, 133ms back- you've…

also DNS newb question here: is a query essentially an HTTP request?

Similar concept, different protocol. DNS is much more lightweight than HTTP, and also tends to run over UDP instead of TCP.

Re: Google Cloud DNS

#42

Post by nickpresta »

jread wrote: post #36

It's a start - barebones authoritative DNS only - no monitoring/failover, load balancing, Geo, LBR, etc - provisioning via API only. Route 53 started out this way, and has since added many of these features and now has almost 7% Alexa 10k marketshare and rapidly growing. I created a browser test that measures recursive DNS query times. You can test Google DNS query performance using this link: http://bit.ly/1nY4e60

My results, from Toronto:

http://i.imgur.com/hOayTQH.png

Re: Google Cloud DNS

#43

Post by BorisMelnik »

tedivm wrote: post #40
BorisMelnik wrote: post #38

Earlier quoted context omitted.

Thank you very much for this explanation. So for example I have a very basic website with CMS. I use a CDN just because I want to give the best possible experience to my users. I get about 50k users per month, a lot of them are new. Would adding a paid DNS or "DNS CDN" as you put it help my user experience enough to matter?

Honestly it depends on who your market is. If your users are mostly on the same continent as you it's probably not worth it, otherwise it could be. On the other hand, if your site makes you money and you've got competition then every edge you can get is worth while.

thank you and thank you. ok that really makes sense. my site is b2b and although transactions do not occur on the website every ounce of frustration I can save matters. we also get a ton of users from US/AU/EU/AS so even with that it would make sense.

Re: Google Cloud DNS

#44

Post by scott_karana »

tedivm wrote: post #29
vishnugupta wrote: post #28

Earlier quoted context omitted.

I understand how CDNs are advantageous by having contents served from locations that are closer to origin of requests (typically browsers spread across the world or a country etc.,). However, for DNS service to be of similar use does it mean application servers are going to be spread across geographically? For end customers it doesn't matter as they will always use the DNS configured for them by their ISP in most of…

You're an Australian Internet User. You want to see hampsterdance.com 'cause fuck it, you like hamsters. Your computer asks your ISP's DNS server for the record. If your ISP has it cached you're golden, but it turns out it probably isn't. So your ISP needs to go to ask the hampsterdance.com DNS server directly. If that server is in the United States then you're stuck waiting 133ms in one direction, 133ms back- you've…

You're point is solid, but can you clear up some confusion for me? I'm not sure whether:

1) Round-trip times from Australia to the USA are truly as bad as 266ms

2) You're confusing ping's RTTs with one-way trips

3) You're assuming DNS has a syn/ack, which it doesn't.

EDIT: I suspect you realize there's no syn/ack in DNS based on your other comments... :)

Re: Google Cloud DNS

#45

Post by scott_karana »

rdl wrote: post #20

I wish either AWS Route 53 or Google Cloud DNS would support being a BIND protocol secondary :(

No kidding. I love the local speeds, and no doubt Google and Amazon do a good job of redundancy, but I'm sure as hell not going to put all my eggs in one basket. Not with DNS.

I had the same problem earlier this year, and if Rackspace or Route53 had AXFR support, I would have used them in a heartbeat...

Re: Google Cloud DNS

#46

Post by tszming »

geekam wrote: post #7

Naïve question but what kind of organizations will benefit the most from this service? Or put it other way, the situations this service is needed for? Can anyone explain to me please?

When you need a reliable & low-latency DNS for your services, you need Anycast DNS - not the one bundled with your GoDaddy's domain, see the differences between Anycast DNS & Unicast DNS: http://dyn.com/blog/unicast-vs-anycast-dns-nameserver-routin...

Re: Google Cloud DNS

#48

Post by gibybo »

Their example for a 'high traffic' site struck me by surprise. With all the caching that goes on with DNS queries, 1.2B in a month seems incredibly high. I wouldn't have even imagined google.com getting that many requests to the authoritative name servers. Can someone with a better idea of how traffic corresponds to DNS queries give me some perspective? How many DNS queries are the name servers for a typical Alex top 10 domain getting?

Re: Google Cloud DNS

#49

Post by ithkuil »

gibybo wrote: post #48

Their example for a 'high traffic' site struck me by surprise. With all the caching that goes on with DNS queries, 1.2B in a month seems incredibly high. I wouldn't have even imagined google.com getting that many requests to the authoritative name servers. Can someone with a better idea of how traffic corresponds to DNS queries give me some perspective? How many DNS queries are the name servers for a typical Alex top…

if you need DNS based failover you want low TTLs , e.g Google.com A record is 100s

Re: Google Cloud DNS

#50

Post by gibybo »

ithkuil wrote: post #49
gibybo wrote: post #48

Their example for a 'high traffic' site struck me by surprise. With all the caching that goes on with DNS queries, 1.2B in a month seems incredibly high. I wouldn't have even imagined google.com getting that many requests to the authoritative name servers. Can someone with a better idea of how traffic corresponds to DNS queries give me some perspective? How many DNS queries are the name servers for a typical Alex top…

if you need DNS based failover you want low TTLs , e.g Google.com A record is 100s

Still though, aren't most consumers using their ISP's DNS servers, which will cache the same response for all of their customers in a region?
Post reply on HN