Nameserver change in Route53 over 36 hours ago, but still marked PENDING / IN_PROGRESS

While the AI agent is correct regarding general DNS propagation timelines (the 48-hour rule), the "IN_PROGRESS" status for an UPDATE_NAMESERVER operation usually points to a backend issue between the Route 53 Registrar and the TLD Registry, rather than just cached records. If you are still seeing this status after 36 hours, you should check the following:

• Email Verification: Check the administrative email address associated with the domain. Sometimes, nameserver updates (especially during or after a transfer) are paused if there is a pending WHOIS/ICANN verification email that hasn't been confirmed.

• Support Ticket (Free Tier): You do not need a paid Support Plan for this. Go to the AWS Support Center and open a ticket under "Account and Billing" > "Domain Registration Issue". Since this is an administrative/registrar task that appears stuck in the backend, AWS Support can manually trigger a retry or investigate the specific API failure with the registry.

• Check "Pending Operations": In the Route 53 console, look specifically under the "Registered Domains" section -> "Pending Operations" to see if there are more details or specific error messages listed there.

Waiting the full 48 hours is standard advice for DNS resolution, but an "IN_PROGRESS" API status for over a day typically requires manual intervention by the AWS Registrar team.

I understand your frustration with the nameserver change taking longer than expected. However, it's important to clarify that DNS changes in Route 53 can legitimately take up to 48 hours to fully propagate, even though many changes complete much faster.

When you change nameservers for a domain to use Route 53's name servers, it can take up to two days for the change to take effect and for Route 53 to become your DNS service. This delay occurs because DNS resolvers across the internet typically cache nameserver information and only request updates once every 24-48 hours. This is normal behavior based on the Time to Live (TTL) settings used by DNS resolvers for nameserver records.

Regarding the status you're seeing, when making changes to Route 53 records, a "PENDING" status indicates that the request has not yet been applied to all Amazon Route 53 DNS servers. Under normal conditions, changes typically reach a synchronized status within 60 seconds for record changes, but nameserver changes specifically follow different propagation timelines due to how DNS works globally.

Unfortunately, there isn't a built-in mechanism to cancel or restart nameserver change requests in Route 53. The system is designed to process these changes through to completion. Since you're at 36 hours and the typical window is up to 48 hours, I'd recommend waiting a bit longer to see if the change completes within the expected timeframe.

If the issue persists beyond 48 hours, you would need to contact AWS Support directly for assistance with your specific case, as this would indicate an unusual situation requiring investigation.
Sources
I changed DNS settings, but they haven't taken effect - Amazon Route 53
ChangeInfo - Amazon Route 53