Live data from Hacker News

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

forums.aws.amazon.com

41–50 of 69 posts

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

#41
post #38

Earlier quoted context omitted.

The "corporate" answers in the support thread don't give any information, and the barrage of links to unhelpful and unrelated information make it seem like they're scripted and not really interested in their customers specific problem at all. If AWS were to say what the problem was then people might be a bit happier to wait?

There must be some marketing handbook somewhere that says "When the customer asks if you have this model in blue, you must never say 'No.' Instead, always say 'We have it in red, green, orange, and seafoam violet.'" Drives me nuts, but all companies do this rather than giving a direct answer.

It's not limited to marketing. Try asking a question along the lines of, "why does x do this?" The answer is frequently, "you shouldn't do x, you should do y." Clearly the question is asking for an explanation, but people will double down on how wrong the questioner is for even asking.

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

#42
post #10
post #5

Route53 seem to have some weird gaps. For instance .nz (New Zealand) originally only allowed people to register 3rd level domains ( like company.co.nz or network.net.nz ). This changed in 2015 and you can now register 2lds like company.nz or network.nz but AWS still hasn't updated their system. It means my employer has to have a 2nd registrar just for those domains. Nagging our TAM and asking other companies to do th…

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

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.

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

#43

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.

This doesn’t make sense. Domain registration is different than DNS. Many would argue keeping your domain registration separate is probably a good thing. Sounds like your problem was with the registrar (making it hard to update NS records to Route53 or anyone else) not AWS.

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

#44

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…

Quatloos... I got that reference! ;) Just watched that ST TOS episode some nights ago (for the first time).

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

#45
post #41

Earlier quoted context omitted.

There must be some marketing handbook somewhere that says "When the customer asks if you have this model in blue, you must never say 'No.' Instead, always say 'We have it in red, green, orange, and seafoam violet.'" Drives me nuts, but all companies do this rather than giving a direct answer.

It's not limited to marketing. Try asking a question along the lines of, "why does x do this?" The answer is frequently, "you shouldn't do x, you should do y." Clearly the question is asking for an explanation, but people will double down on how wrong the questioner is for even asking.

Golang in one comment.

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

#47
post #41

Earlier quoted context omitted.

There must be some marketing handbook somewhere that says "When the customer asks if you have this model in blue, you must never say 'No.' Instead, always say 'We have it in red, green, orange, and seafoam violet.'" Drives me nuts, but all companies do this rather than giving a direct answer.

It's not limited to marketing. Try asking a question along the lines of, "why does x do this?" The answer is frequently, "you shouldn't do x, you should do y." Clearly the question is asking for an explanation, but people will double down on how wrong the questioner is for even asking.

Sometimes people are asking for what they think they want because they don't know that theres a better way to solve their problem. http://xyproblem.info/

Also https://xkcd.com/1172/

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

#48
post #41

Earlier quoted context omitted.

It's not limited to marketing. Try asking a question along the lines of, "why does x do this?" The answer is frequently, "you shouldn't do x, you should do y." Clearly the question is asking for an explanation, but people will double down on how wrong the questioner is for even asking.

Golang in one comment.

Hah, definitely. It's like everyone working on that tag is trying to read the question in a way to not answer anything.

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

#49
post #47
post #41

Earlier quoted context omitted.

It's not limited to marketing. Try asking a question along the lines of, "why does x do this?" The answer is frequently, "you shouldn't do x, you should do y." Clearly the question is asking for an explanation, but people will double down on how wrong the questioner is for even asking.

Sometimes people are asking for what they think they want because they don't know that theres a better way to solve their problem. http://xyproblem.info/ Also https://xkcd.com/1172/

> Sometimes people are asking for what they think they want

Except when they aren't, which is what I'm talking about. And you could say the same thing about the marketing speak.

If you ask a question on Stackoverflow, a lot of people will give you the answer they know, regardless of the question you asked.

If I ask "how do I do this with x?" The answer "Generally in this language we do it with y. Will that work?" is a proper answer

If I ask "why does x panic?" The answer isn't, "do y." The answer is an insight to the programming language/operating system in question, but people just can't resist, and it is exactly like the marketing speak mentioned here.

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

#50
post #47
post #41

Earlier quoted context omitted.

It's not limited to marketing. Try asking a question along the lines of, "why does x do this?" The answer is frequently, "you shouldn't do x, you should do y." Clearly the question is asking for an explanation, but people will double down on how wrong the questioner is for even asking.

Sometimes people are asking for what they think they want because they don't know that theres a better way to solve their problem. http://xyproblem.info/ Also https://xkcd.com/1172/

Assuming the person asking doesn't know what they're doing is not the best approach if you actually want to solve problems.
Post reply on HN