Hacker News Reader

Hacker News

Comment by linuxlizard | Hacker News Reader

Full thread

linuxlizard

I'm now looking for recommendations for another DNS provider. USA or Europe preferred. Anyone have any?

View on HN

Some ideas:

Google's Cloud DNS: https://cloud.google.com/dns/pricing

Route 53: https://aws.amazon.com/route53/

Dns Made Easy: http://www.dnsmadeeasy.com/

Dnsperf.com is also a good resource to compare speed and reliability of DNS providers.

I've been using Route53 for the last 3 years, and I'll vouch for it. It's pretty sweet -- the UI is clear, but allows for a decent amount of configuration, and it's reliable. It also integrates with major registrars (GANDI's a big one) and lets you manage domain ownership via an AWS account -- and personally, I prefer unified bills.

I'll anti-vouch for Route53 for personal use. I use AWS pretty broadly, but with something like DNS, I like having a little bit more support if things go wrong. Amazon won't do much without a $upport contract.

It's fine for business use with a support contract.

Route53 is awesome. I personally wrap it in git - https://dns-api.com/ - and remove the per-query pricing to provide stability.

Not sure if it's the same service, but if you're using Google as your registrar, DNS seems to be included... would be surprised if it wasn't the same infrastructure.

I've heard good things about AWS Route53 as well.

Google support confirmed that their Domains DNS is the same infra as the Cloud DNS

Yeah... google domains' management tools are what got me to switch pretty much everything over to them... some domains you can move to them after registration, but can't get new ones for the given tld.

I can't say how happy I've been with their mostly out of the way tooling... the two times I needed support using the callback option worked out for me. Far easier than getting support for anything else google, but it's been great so far...

Even tried the dyndns for an a-record, which has worked well enough.

CloudFlare. It's free and bulletproof, even if you don't use their protective reverse proxy you can use their DNS service for free and it has a dynamic updating API.

Unlike other providers (looking at you Amazon with your handling of Wikileaks) they've also proven themselves willing to stand up for their customers, even free ones legally.

Cloudflare is not bulletproof. Had several times where cloudflare proxy plus my Nginx server got stuck in infinite loops making everything time out. No logical reason why. Switched to cloudCDN and 0 problems since.

Sounds like your app was doing something weird as I've not had any issues using a similar setup.

What's this cloudCDN thing? Can't find it on Google.

https://cloud.google.com/cdn/docs/

Check a checkbox, and your static stuff gets CDNed.

Seems a lot better than letting another service control you, perhaps put up CAPATCHAs, perhaps mess up your networking, etc.

> Seems a lot better than letting another service control you, perhaps put up CAPATCHAs, perhaps mess up your networking, etc.

Disabling the CAPTCHAs is trivial, just set the security features to low or off. This does basically the same thing in terms of "mess up your networking" though. All your traffic is just routed through Google instead of CloudFlare. No real difference there. You can also kick the CF security up if you get attacked.

Google's will however cost you a crapload if someone decides to run even a fairly primitive layer 7 attack against you. So you better just hope you don't get hit, unless I'm missing something excluding attack bandwidth?

Google does do some automatic DDoS protection for you: https://cloud.google.com/files/GCPDDoSprotection-04122016.pd...

I'm not sure if that addresses your concern, but hope this is helpful. Let me know either way.

I'm a PM on Google Cloud, but not working on either CDN or DDoS protection.

+1 for Cloudflare. For failover and such, I'm watching for how their traffic control and traffic manager features evolve. https://blog.cloudflare.com/cloudflare-traffic/

They will, however, acquire an SSL cert in your name for themselves when you use their DNS service.

What problems can that cause though?

(Alternatively - does anything stop me acquiring an SSL cert in your name, despite me not being Cloudflare and you not having an account with me?)

FWIW I like dnsimple . I've got domains on both services and I'll be moving my last stuff off dyn and onto dnsimple after this, no desire to be a customer of Oracle's.

NYC-based NS1: https://ns1.com

Ironically they're now down - https://news.ycombinator.com/item?id=13019858

I too am looking for alternatives. I moved to Dyn from ZoneEdit, I may look to go back.

Has anyone favourable experience with Route53?

> Has anyone favourable experience with Route53?

Yes, using it commercially(for work) and for personal domains. The pricing is incredibly low, and I haven't had an outage/hiccup since it launched.

Thanks, I might give this a go with a 'spare' domain to investigate it more.

Ugh, I definitely wouldn't recommend going back to ZoneEdit (now "easyDNS").

I didn't know they were bought out as well. Many years ago I ran my own DNS, perhaps I should look at doing it again.

I use a combination of DNS Made Easy and Route 53. Both have worked well for me.

This is a good thing to do. Rather than host all your DNS records at any one provider, split them across two.

That allows you to keep on running even if your provider suffers a DDos, or outage. (As Dyn famously did recently.)

We balance our domains across Dyn and UltraDNS. No complaints about UltraDNS so far. Has just worked, and they have a decent REST API which is nice (as does Dyn).

We were on UltraDNS for a few years. They started receiving nearly quarterly DDoS attacks and then tried to try to sell us DDoS scrubbing services. From there we moved to Dyn and have been happy. The DDoS that took out Dyn for a while would have take any single provider offline.

Yeah, definitely. The bigger takeaway is probably that you really want to have more than one DNS provider. Assuming whatever you're running is important enough to justify the cost.

If DNS ain't happy, ain't nobody happy ;)

I agree entirely.

namecheap work well for me.

We're in the process of migrating away from Namecheap. They've been having DNS issues lately, as recently as last week (16 November) their entire DNS infrastructure was unexpectedly down for several hours. [0] Took all our sites offline.

> $ host mydomain.com dns1.name-services.com

> ;; connection timed out; no servers could be reached

They're cheap, but have been experiencing some real reliability issues as of late. Other registrars offer pretty similar pricing and don't suffer from as frequent outages.

We were hardly the only people affected. Check their Twitter[1] for other people complaining of DNS outages.

Also, their new admin portal redesign sucks. Tons of white space and managing domains now requires many more clicks than it did before. Their zone management interface also frequently fails to update the zone.

Gandi's zone management interface is a million times better.

[0] http://status.namecheap.com/archives/28960

[1] https://twitter.com/namecheap

Hate to pile on, but the admin portal redesign was incredibly bad. So many things that were logically organized together in the old design are now spread across N > 3 pages that are no longer linked from one to another. Hate to impute motives but after I found that I "accidentally" bought the same product multiple times because I simply couldn't trivially figure out WHAT I'd bought and hadn't yet configured I realized it was probably a revenue maximization exercise. Still use them because I like their service, but very dark.

Reply on news.ycombinator.com