URGENT: Route 53 nameserver operation stuck for 24+ hours - Operation ID dd7460e3-2550-4473-98fe-7973fd64ba1c

I understand this is an urgent situation with your nameserver update operation being stuck for over 24 hours. Here's what I can advise based on Route 53 operations:

Understanding the Operation: When you update domain nameservers using Route 53, the operation returns an Operation ID that can be used to track progress. Nameserver updates can sometimes take time to complete as they involve coordination with domain registries and DNS propagation across the internet.

Typical Resolution Steps:

1. Check Operation Status: You can verify the current status of your operation using the AWS CLI command get-operation-detail with your Operation ID to see if there are any error messages or additional details.

2. DNS Propagation Delays: DNS changes, including nameserver updates, can experience propagation delays. While 24+ hours is longer than typical, complex scenarios or registry-level issues can cause extended delays.

3. AWS Support: Since you've already submitted a support case, that is the correct escalation path. For urgent production-impacting issues, ensure your support case is marked with the appropriate severity level to get faster response times.

Important Notes:

• Nameserver update operations run in the us-east-1 region for Route 53 Domains
• Do not attempt to submit duplicate nameserver update requests while one is in progress, as this could complicate the situation
• DNSSEC changes should only be made with careful consideration and proper guidance from AWS Support, as incorrect DNSSEC configuration can cause domain resolution failures

Since this is blocking business operations and you have an open support case, I recommend following up on your existing support case to request escalation rather than making additional configuration changes that could further complicate the situation.
Sources
update-domain-nameservers — AWS CLI 2.27.41 Command Reference
AWS re:Post Knowledge Center Spotlight: Route 53 | AWS re:Post

I can currently only see the email option enabled, and I’ve been waiting for about a week after submitting the request but haven’t received any response yet.

At this point, it seems the only option left is to move the domain to another provider. The only reason I was holding back is that I recently paid for the domain on AWS, and transferring it would incur additional costs. Unfortunately, without a response, I don’t see any other viable option.