6 ms·

Feeling the pain here too. What DNS providers do others use and like? Route53?

by showerst 11y ago

joejoebob 11y ago
Where I work we use Rotue53. For my personal domains I just use my registrar, Namecheap.
- dsp1234 11y ago
  For us, Route53 is painful. We host a few thousand zones, and due to rate limiting on APIs, doing something like "Show a list of domain names" or "Give all the domains matching some pattern" were particularly painful. Upwards of 30 seconds to do a simple list of domains meant we were forced to cache locally. A local cache, combined with the fact that zone names are not unique in their system (possible to create multiple abc.com entries, which differ only in an internal id and the list of NS entries) made it hard to ensure that our internal systems matched "reality". Then the administrative nightmare of 3-4 different NS entries for each zone means customized, rather than generic, instructions for validating NS settings at the individual registrars. All in all, it was not a fun experience with such a large volume of zones, but we knew we were an edge case.
  - tomschlick 11y ago
    You can contact amazon to get rate limits increased if you have the use case
rbritton 11y ago
The sites I have that are actually up right now are those routed through CloudFlare.
dboreham 11y ago
Bind, running on VMs. Not hard.
- SteveNuts 11y ago
  You run your own authoritative DNS servers?
  - z92 11y ago
    I ran my non-authoritative DNS server [bind] on a droplet for about a year. But the server crashed every few months. Why? Never figured out. A restart always fixed it. Later shifted to DO's DNS servers. Now that that one is down too, just shifted back to domain register's DNS. Everything is working now.
hornbaker 11y ago
dnsmadeeasy for around 8 years now
stevekemp 11y ago
Route53 is hard not to love; simple to develop against and very very reliable. I wrap it in git to make updates more straightforward for people unfamiliar with AWS, but even using it directly is very simple from multiple languages. (https://dns-api.com/ https://dns-api.com/)
tyingq 11y ago
This has always been a good resource to see who the front runners are: http://www.solvedns.com/dns-comparison/ http://www.solvedns.com/dns-comparison/

Feeling the pain here too. What DNS providers do others use and like? Route53?

joejoebob 11y ago

Where I work we use Rotue53. For my personal domains I just use my registrar, Namecheap.

dsp1234 11y ago
For us, Route53 is painful. We host a few thousand zones, and due to rate limiting on APIs, doing something like "Show a list of domain names" or "Give all the domains matching some pattern" were particularly painful. Upwards of 30 seconds to do a simple list of domains meant we were forced to cache locally. A local cache, combined with the fact that zone names are not unique in their system (possible to create multiple abc.com entries, which differ only in an internal id and the list of NS entries) made it hard to ensure that our internal systems matched "reality". Then the administrative nightmare of 3-4 different NS entries for each zone means customized, rather than generic, instructions for validating NS settings at the individual registrars. All in all, it was not a fun experience with such a large volume of zones, but we knew we were an edge case.
- tomschlick 11y ago
  You can contact amazon to get rate limits increased if you have the use case

rbritton 11y ago

The sites I have that are actually up right now are those routed through CloudFlare.

dboreham 11y ago

Bind, running on VMs. Not hard.

SteveNuts 11y ago
You run your own authoritative DNS servers?
- z92 11y ago
  I ran my non-authoritative DNS server [bind] on a droplet for about a year. But the server crashed every few months. Why? Never figured out. A restart always fixed it. Later shifted to DO's DNS servers. Now that that one is down too, just shifted back to domain register's DNS. Everything is working now.

hornbaker 11y ago

dnsmadeeasy for around 8 years now

stevekemp 11y ago

Route53 is hard not to love; simple to develop against and very very reliable. I wrap it in git to make updates more straightforward for people unfamiliar with AWS, but even using it directly is very simple from multiple languages. (https://dns-api.com/ https://dns-api.com/)

tyingq 11y ago

This has always been a good resource to see who the front runners are: http://www.solvedns.com/dns-comparison/ http://www.solvedns.com/dns-comparison/