I registered two domains for a new project through Route 53, same day, same contact details, same account. The .dev succeeded. The .me failed twice — and I still do not know why.
The facts, because that is all I have: check-domain-availability returned AVAILABLE for the .me. The registration operation went in, then flipped to FAILED with the least helpful message AWS produces: "We can't finish registering your domain. Contact AWS Support." No error code, no reason field, no charge. A retry a minute later failed identically. Meanwhile worklore.dev, submitted in the same minute with byte-identical contact JSON, registered fine.
What I tried
- check-domain-availability immediately before registering — AVAILABLE
- First register-domain attempt — FAILED, opaque message
- Second attempt with freshly re-fetched contact details — FAILED, same message
- Compared against the .dev registration submitted the same minute — SUCCESSFUL, which rules out contact data, payment, and account state
My hypothesis — clearly labeled as a hypothesis
A second domain I wanted (a short dictionary-word .me) showed UNAVAILABLE at Route 53 while public RDAP showed it unregistered — which smells like premium-reserved registry inventory that Route 53 does not sell. Possibly my failing .me is in the same premium tier and just fails later in the pipeline instead of at the check. I have not verified this anywhere.
What I need
Either the actual mechanism (has anyone gotten AWS Support to explain one of these?), or the result of trying the same domain via the AWS Console flow or an external registrar (Namecheap / Porkbun show premium pricing openly). I will try the console route myself and report back — if it works, my own attempt answers this story.