3 ms·

Is that really a big deal though? Register the domain, point the name servers, job done for 5 years.

slyall 6y ago
It isn't just one domain. Big companies can have hundreds or thousands. Having a few percent of these with another vendor means you have to have additional bills (and get those through accounts), logins and the like.
- capableweb 6y ago
  Probably a good idea to keep one service for DNS records and domain hosting, a service that specializes in just that, instead of trying to use one service for everything (like what AWS does). If you try to shoehorn everything into a "all-in-one" solution you often end up with poor solutions overall just to fit it, while if you pick one solution per problem, you end up with the best fit. See also: Unix Philosophy
  - _joel 6y ago
    Route53 also has deeper integrations into Amazon therefore you can 'tag' services in that might change IP (via Elastic IP for example). You could do that with CNAME or ALIAS between the DNS providers but it'd get messy. Otherwise if you rotate an IP then you'll have to manually update the other DNS or write your own glue, or hand over delegation for certain namespaces in the domain in a frankenstein fashion. See also: Keeping sanity whilst maintaining hundreds of moving parts
    - gog 6y ago
      Domain registrar and DNS provider are 2 separate things. If I understood the linked article correctly you can not register a domain through Amazon. That doesn't mean you can not use Amazon as a DNS for that domain.
  - chrisweekly 6y ago
    Agreed, in principle and in practice. For my own stuff, I've been happy with IWantMyName and DNSMadeEasy for registry + DNS per se, leaving me free to experiment with deploying to various providers (AWS, Digital Ocean, Vercel, Netlify...) without a hitch.
- tallanvor 6y ago
  Big companies with that number of domains tend to use a 3rd party services such as MarkMonitor to manage this.
swiley 6y ago
Now you have to remember to re register the domain in 5 years on a different registrar. Even large organizations struggle to do this with just one.

It isn't just one domain. Big companies can have hundreds or thousands. Having a few percent of these with another vendor means you have to have additional bills (and get those through accounts), logins and the like.

capableweb 6y ago
Probably a good idea to keep one service for DNS records and domain hosting, a service that specializes in just that, instead of trying to use one service for everything (like what AWS does). If you try to shoehorn everything into a "all-in-one" solution you often end up with poor solutions overall just to fit it, while if you pick one solution per problem, you end up with the best fit. See also: Unix Philosophy
- _joel 6y ago
  Route53 also has deeper integrations into Amazon therefore you can 'tag' services in that might change IP (via Elastic IP for example). You could do that with CNAME or ALIAS between the DNS providers but it'd get messy. Otherwise if you rotate an IP then you'll have to manually update the other DNS or write your own glue, or hand over delegation for certain namespaces in the domain in a frankenstein fashion. See also: Keeping sanity whilst maintaining hundreds of moving parts
  - gog 6y ago
    Domain registrar and DNS provider are 2 separate things. If I understood the linked article correctly you can not register a domain through Amazon. That doesn't mean you can not use Amazon as a DNS for that domain.
- chrisweekly 6y ago
  Agreed, in principle and in practice. For my own stuff, I've been happy with IWantMyName and DNSMadeEasy for registry + DNS per se, leaving me free to experiment with deploying to various providers (AWS, Digital Ocean, Vercel, Netlify...) without a hitch.
tallanvor 6y ago
Big companies with that number of domains tend to use a 3rd party services such as MarkMonitor to manage this.

swiley 6y ago

Now you have to remember to re register the domain in 5 years on a different registrar. Even large organizations struggle to do this with just one.