Live data from Hacker News

Google Cloud DNS

developers.google.com

31–40 of 87 posts

Re: Google Cloud DNS

#31
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?

We announced Cloud DNS at Cloud Platform Live on March 25th. It kind of got lost in the noise around the big price cuts.

Re: Google Cloud DNS

#32

Earlier quoted context omitted.

That and DNSSEC support. If they had DNSSEC support, I could see my organization moving to them.

You actually use DNSSEC in production?

Quite a few people do use DNSSEC in production.

An example of what can go wrong tho? http://blog.pagerduty.com/2013/12/outage-post-mortem-dec-11-...

Just a potential issue to keep in mind for people who do.

Re: Google Cloud DNS

#33
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.

Dnsmadeasy is also a good option for small to medium size requirements, in my opinion. I use it for my personal domains.

Re: Google Cloud DNS

#34
post #31
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?

We announced Cloud DNS at Cloud Platform Live on March 25th. It kind of got lost in the noise around the big price cuts.

Any chance of geographic and/or latency based views and edns-client-subnet support?

Re: Google Cloud DNS

#35
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…

"I'm wondering how Dyn is taking this. "

I use dyn as well as run several dns servers in different places [1]

My reason for not using this is that it's being offered by google and the obvious fear that they will decide one day to stop offering this, supporting it, or improving it. As I am experiencing now with google voice for example,

[1] Since the mid 90's actually learning from this book:

http://shop.oreilly.com/product/9781565920101.do

Re: Google Cloud DNS

#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

Re: Google Cloud DNS

#37
post #23

Earlier quoted context omitted.

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).

For my use cases, CloudFront beat out EdgeCast quite a bit in price. (~20 TB / month commit with a request mix heavily biased towards NA and Europe).

Re: Google Cloud DNS

#38
post #29

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…

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?

Re: Google Cloud DNS

#39
post #29

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…

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

Re: Google Cloud DNS

#40
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…

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.

Post reply on HN