Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS is not offering Austria's TLD .at for registration

forums.aws.amazon.com

Post reply on HN
Print view View original

21–30 of 69 posts

Re: AWS is not offering Austria's TLD .at for registration

#21

Post by 867-5309 »

fanf2 wrote: post #17
robertlagrant wrote: post #12

Earlier quoted context omitted.

Is domain registration a big part of your hosting world? Surely anyone can register a domain with anyone and point DNS?

Registrars generally have terrible APIs for managing DNS delegations and ownership details. There are also good reasons to be able to manage DNS zone contents, delegations, and ownership through a single coherent set of APIs.

First thing in I do when I register a domain is point its DNS to Digital Ocean nameservers (some registrars even offer this in the signup process - no login or further setup required). That way all my domains are managed under one account irrespective of where they were purchased. They offer every DNS setting you would ever need (unlike some registrars) and their propagation is always super fast. Their API is top notch. The best thing is it's a free service, and the only service of theirs I use. No need for their cloud services. Just amazing DNS.

Re: AWS is not offering Austria's TLD .at for registration

#22

Post by _joel »

capableweb wrote: post #20
slyall wrote: post #15

Earlier quoted context omitted.

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.

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

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

Re: AWS is not offering Austria's TLD .at for registration

#23

Post by shaicoleman »

Always register your domain with a different provider. A domain is one of the crown jewels of a company.

If you lose the domain, you lose everything (email, web, services, etc.), possibly permanently, with no option to migrate without losing your domain, branding, SEO position, etc.

e.g.

* Your server got hacked, and your entire account gets blocked

* You get a shock bill from AWS, and lose access to the account because the account is unpaid.

* Also it allows your hosting provider to hold you ransom to payment or you lose everything

Re: AWS is not offering Austria's TLD .at for registration

#24

Post by chrisweekly »

capableweb wrote: post #20
slyall wrote: post #15

Earlier quoted context omitted.

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.

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

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.

Re: AWS is not offering Austria's TLD .at for registration

#25

Post by tallanvor »

slyall wrote: post #15
PetahNZ wrote: post #10

Earlier quoted context omitted.

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

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.

Big companies with that number of domains tend to use a 3rd party services such as MarkMonitor to manage this.

Re: AWS is not offering Austria's TLD .at for registration

#26

Post by fanf2 »

867-5309 wrote: post #21
fanf2 wrote: post #17

Earlier quoted context omitted.

Registrars generally have terrible APIs for managing DNS delegations and ownership details. There are also good reasons to be able to manage DNS zone contents, delegations, and ownership through a single coherent set of APIs.

First thing in I do when I register a domain is point its DNS to Digital Ocean nameservers (some registrars even offer this in the signup process - no login or further setup required). That way all my domains are managed under one account irrespective of where they were purchased. They offer every DNS setting you would ever need (unlike some registrars) and their propagation is always super fast. Their API is top not…

It sounds like you are talking about a zone contents API, and I agree that it's important to have a good one. But it's also important to have a good API for managing a domain's delegation and ownership information, so that you can ensure all your domains are managed consistently. Just pointing the DNS for a domain at a good DNS provider doesn't help with managing its delegation if the registrar is crappy.

Re: AWS is not offering Austria's TLD .at for registration

#27

Post by mtkd »

shaicoleman wrote: post #23

Always register your domain with a different provider. A domain is one of the crown jewels of a company. If you lose the domain, you lose everything (email, web, services, etc.), possibly permanently, with no option to migrate without losing your domain, branding, SEO position, etc. e.g. * Your server got hacked, and your entire account gets blocked * You get a shock bill from AWS, and lose access to the account beca…

Also worth using a premium domain service like CSC -- if there is an issue you have a 24/7 contact and for overseas domains they usually have local agents who can hold the domain if rules change that would ordinarily disqualify you from holding that ccTLD

Re: AWS is not offering Austria's TLD .at for registration

#28

Post by ricardo81 »

renbef wrote: post #14

https://aws.amazon.com/route53/domain-registration-agreement... states that they use gandi.net and domainbox.com as registrars, both support .at. So i guess they just forgot about it. Would welcome a better explanation though.

Interesting, also there's no specific requirements for .at like requiring local residency or any kind of documentation requirements so it should be a straightforward implementation for CF as a reseller to those registrars.

Re: AWS is not offering Austria's TLD .at for registration

#29

Post by CydeWeys »

rococode wrote: post #4

Anyone have some insights on what a registrar usually needs to do to add a country's TLD? Sounds like it might be the kind of problem that's simple on paper but in practice requires jumping through all kinds of regulatory hoops for each new country. It does seem to be pretty common for registrars to be missing ccTLDs - .ai (for Anguilla), for example, is not supported by some registrars even though it's popular and a…

I'm in the industry, and there's no regulation or standardization on ccTLDs. Some of them have customized one-off web portals that an employee of the registrar has to log in to to manually register a domain. It's totally understandable why many registrars don't (yet?) support all ccTLDs. Contrast with gTLDs, which ICANN requires the use of standardized protocols for (see RFCs 5730-5734). Offering gTLDs is much easier; more work can be involved in signing the contracts with the registry operator than in configuring your system to point to an additional standardized API endpoint.

Re: AWS is not offering Austria's TLD .at for registration

#30

Post by gog »

_joel wrote: post #22
capableweb wrote: post #20

Earlier quoted context omitted.

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

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…

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.
Post reply on HN