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

21–30 of 87 posts

Re: Google Cloud DNS

#21

Post by gtaylor »

tomschlick wrote: post #12
nodesocket wrote: post #6

DNS is so cheap, and Amazon Route53 has such an advantage with their latency based routing, health checks, and integrations with other AWS services. Honestly zones are $0.50 and $0.50 per million queries. You have to be pushing lots of DNS queries to have costs even exceed a tiny bill of $20 a month. It is the definition of a lot of engineers hours and infrastructure costs for literally no profit for the company. How…

Hopefully the lower cost from google causes aws to drop prices for this service as well.

Unless your app operates at a truly massive scale with a very specific set of characteristics, this won't save you even a minuscule fraction on your total budget. Route 53 is dirt freaking cheap.

Re: Google Cloud DNS

#23

Post by tedivm »

nodesocket wrote: post #18
tedivm wrote: post #10

I'm wondering how Dyn is taking this. These guys have been working on DNS for years, and were probably one of the first "managed DNS" or "enterprise DNS" services. Over time though they've failed to really innovate, or even keep up with standard (you can't use any of their value add services like the global traffic manager if you also want to use DNSSEC, for instance). Despite this their prices have remained ridiculo…

EdgeCast looks nice, but minimum of $50 a month. http://www.edgecast.com/services/route-managed-dns/ We pay around $2 a month at Route53.

Route53 is not a bad option. If you're using EdgeCast CDN as well you'll probably get a discount on DNS (and I will point out that the EdgeCast CDN is faster, and more importantly, a hell of a lot cheaper than Cloudfront is).

Re: Google Cloud DNS

#24

Post by bredman »

MBlume wrote: post #11

Was this announced by Google today, or is this on HN because of the XKCD? If the former, did Google push the announcement because of the XKCD?

This was released on March 28th:

http://googlecloudplatform.blogspot.com/2014/03/announcing-g...

Guess this is just on the front page because of XKCD about the other Google DNS product?

Re: Google Cloud DNS

#28

Post by vishnugupta »

tedivm wrote: post #15
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?

The same type of people who use CDNs. If you want great performance globally it helps to have primary DNS services near by, rather than having lookups cross the world.

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 the cases unless one is tech savvy and tries to use some other DNS such as Google etc.,?

Please help understand what am I missing here?

Re: Google Cloud DNS

#29

Post by tedivm »

vishnugupta wrote: post #28
tedivm wrote: post #15

Earlier quoted context omitted.

The same type of people who use CDNs. If you want great performance globally it helps to have primary DNS services near by, rather than having lookups cross the world.

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 now added a quarter of a second to that page loaded.

Using a DNS CDN means that 266ms ends up being 15ms (keep in mind that these guys also peer with local ISPs to make things even faster).

Re: Google Cloud DNS

#30

Post by [deleted] »

vishnugupta wrote: post #28
tedivm wrote: post #15

Earlier quoted context omitted.

The same type of people who use CDNs. If you want great performance globally it helps to have primary DNS services near by, rather than having lookups cross the world.

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…

[deleted]
Post reply on HN