DNS Resolution issues (SERVFAIL) after internal transfer of domain in Route 53

Question

We transferred our domain successfully from one AWS account to another one. Route53 automatically created a hosted zone with 4 nameservers. But the new domain is inaccessible. NS lookup returns SERVFAIL. Mailflows are disrupted. 
It has been more than 48 hours - so not sure about the DNS caching wait time. 
The domain was working nicely under the old AWS account. 
Any suggestions? Thanks much.

Answer

When you **dig** your domainname what does it tell you that the NS records are set to, and does this align with what's in the new hosted zone in the target account?

Also look at the TTL (time-to-live) for the NS records. For this either use the command line `dig @8.8.8.8 mydomain.com ns` (second column in the *ANSWER SECTION*) or Google Toolbox Dig https://toolbox.googleapps.com/apps/dig/

Even if you're on a Basic Support plan (which would preclude you from raising a support call most of the time) you can still raise a support call with AWS to get support for this, under Account and Billing -> Service: Billing -> Category: Domain Registration Issue

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-contact-support.html

DNS Resolution issues (SERVFAIL) after internal transfer of domain in Route 53

Contenus pertinents