Live data from Hacker News

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

forums.aws.amazon.com

61–69 of 69 posts

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

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

> Anyone have some insights on what a registrar usually needs to do to add a country's TLD?

ccTLDs are the Wild West. It's hard to generalize -- practically every ccTLD does something weird that makes it difficult to support, though.

A few examples of areas where ccTLDs behave significantly differently from gTLDs are:

• Many ccTLDs require registrants to have some form of personal or business presence in the country. The requirements for how the registrant must prove that presence can vary.

• Some ccTLDs have unusual processes surrounding domain expirations and renewals. For example, under some ccTLDs, domains always expire at the end of a month, rather than exactly a year after registration. Additionally, some ccTLDs restrict when domains can be renewed -- for example, .au domains can only be renewed within 90 days of their expiration, and .eu domains cannot be renewed within 5 days of expiration.

• Domain transfers can get weird as well. gTLDs have a standardized process for domain transfer authorization; ccTLDs often modify this system or replace it entirely.

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

#62

I manage a portfolio of 1800+ domains for my employer. When we migrated DNS to route53 in early 2019 we discussed moving registration as well. That conversation took about two minutes and ended in a hard no. Our registrar is MarkMonitor who specializes in large portfolios. I’ve got a dedicated account rep. We know each other well. We talk often, not just domains but college sports, etc. I need something I email my gu…

.es or .at, piece of cake. Try .ax! ;-)

Oh dammit, they opened it up for everyone. Nothing is holy these days.

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

#63

I manage a portfolio of 1800+ domains for my employer. When we migrated DNS to route53 in early 2019 we discussed moving registration as well. That conversation took about two minutes and ended in a hard no. Our registrar is MarkMonitor who specializes in large portfolios. I’ve got a dedicated account rep. We know each other well. We talk often, not just domains but college sports, etc. I need something I email my gu…

.es or .at, piece of cake. Try .ax! ;-)

No, try .aq!

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

#64
post #26

Earlier quoted context omitted.

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.

if your business involves registering a high volume of a specific domain then yes, help with managing those would be vital, but most people registering domain names are web developers registering on behalf of clients

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

#65
post #52

When AWS initially started offering domain registrations, I transferred a few domains (that I'd already been using Route 53 for) over to keep everything in one place. A few months later, I wanted to transfer them elsewhere, but quickly realized that the auth codes in the AWS interface had expired, with no way to renew them. I didn't have a support subscription since I only used the AWS account for these 4 domains + R…

That stinks. In the future you can post to r/aws. Lots of aws folks read that subreddit and they are responsive.

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

#66
post #52

When AWS initially started offering domain registrations, I transferred a few domains (that I'd already been using Route 53 for) over to keep everything in one place. A few months later, I wanted to transfer them elsewhere, but quickly realized that the auth codes in the AWS interface had expired, with no way to renew them. I didn't have a support subscription since I only used the AWS account for these 4 domains + R…

That stinks. In the future you can post to r/aws. Lots of aws folks read that subreddit and they are responsive.

That's really saying something about AWS, it's easier to get support and bugs fixed on reddit, than via direct contact.

Big red flag!

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

#67

The reason we're not using AWS is because we couldn't switch our entire network of a few thousand .at domains over here easily. It would have meant months of work. So we went with a competitor. @AWS my 5cents: adding many more TLDs is one of the highest ROI investments you can make.

So you don't use AWS simply because you can't host dns there? Oddly almost everyone I know using AWS refuses to use Route53.

You'd of been fine to use AWS without route53, it's basically the standard. As discussed in this thread, separation of concerns is wise.

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

#69

Earlier quoted context omitted.

The consequences are not quite so dramatically irrevocable. I’ve recently assisted a family member whose hosting provider was bought by a gang of unscrupulous clowns and their domains effectively held to ransom. It took only hours to recover them and switch registrars, during which time I’d used/activated only the same channels and processes available to any other registrant. And AWS are not a gang of pirates. Someon…

Can you share a resource to learn more about the recovery process?

Well there’s a lot to learn, but you can do worse than start with the ICANN dispute processes. And they are many: https://www.icann.org/resources/pages/help-2012-02-03-en

Country code registries have their own, and many apparent registrars are actually reselling Tucows or OpenSRS, both of whom have compliance teams that create significant leverage over resellers.

However, communicating them with them concisely and unambiguously requires care and understanding. Obtaining a result from the people who execute these processes means encoding requests in terms of their incentives rather than your own. Many people find that hard to do, especially people burdened by their own overwhelming sense of entitlement. This is of course advice for anyone engaging with an external bureaucracy, and the best way to internalise it, is to have run one.

Post reply on HN