- Newest
- Most votes
- Most comments
I understand your frustration with the domain registration process for .click domains on Route 53. There are a few potential reasons for the discrepancy you're experiencing:
-
Availability caching: Route 53 may cache domain availability information for a period of time, which can lead to inconsistencies between what you see in the search results and what happens when you try to register the domain.
-
Real-time availability changes: Domain availability can change rapidly, especially for popular TLDs like .click. The domain might be available when you search, but become unavailable by the time you complete the registration process.
-
Registry synchronization: There might be a delay in synchronization between the Tucows registry and Route 53's systems, leading to conflicting availability information.
-
TLD-specific issues: While .click domains are supported by Route 53, there could be temporary issues specific to this TLD that are causing registration problems.
To address this issue, you can try the following:
-
Wait a short period (e.g., a few hours) and attempt the registration again. This may allow time for any caching or synchronization issues to resolve.
-
Use the AWS CLI to check domain availability in real-time. The
check-domain-availabilitycommand can provide up-to-date information about domain availability. -
If the problem persists, it's advisable to contact AWS Support. They can investigate the specific issues you're encountering with .click domain registrations and provide more detailed assistance.
Remember that domain registration can be complex, and discrepancies between different systems can occur. If you continue to experience issues, AWS Support will be best equipped to help resolve the problem.
Sources
Registering a new domain - Amazon Route 53
Use CheckDomainAvailability with an AWS SDK or CLI - Amazon Route 53
.click - Amazon Route 53
Contacting AWS Support about domain registration issues - Amazon Route 53
AWS provides its own method for checking domain availability. Have you tried verifying the domain's availability using the CLI command:
aws route53domains check-domain-availability --domain-name <your-domain> [1]?
What is the output of the command? Does it indicate that the domain is available or unavailable? If the command says its unavailable it is possible that tucows registry is not up to date. In that case, I also recommend checking: https://www.whois.com/.
[1] https://docs.aws.amazon.com/cli/latest/reference/route53domains/check-domain-availability.html
Best,
Relevant content
- asked a year ago
- asked a year ago
- asked 3 years ago
- AWS OFFICIALUpdated 3 years ago
