- Newest
- Most votes
- Most comments
It’s most likely your Glue records are incorrect.
When you transferred your domain, you may or may not have updated your Glue Name server records.
Look in your route53 zone file for your NS records. There will be 4 name servers.
Then head over to this link and update your name servers on your domain https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html
Hi,
You should go through this guidance: https://repost.aws/knowledge-center/route53-dns-servfail-response to validate that your problem doesn't come from one of the listed causes for DNS SERVFAIL errors
Stating that you're pretty sure of the Route53 settings and that it is a transfer from OVH, you may want to start with the first possible cause in the list "A third-party name server (NS) is blocking the AWS public resolver's IP address"
In particular, you should check via nslookup directly (nslookup [domain-name] [name-server]
) on OVH servers if they still directly publish infos about your domain
Best,
Didier
You mean I need to go back to OVH to update the DNS names to Route 53's ? But why would I need to do that? The domain is transferred, right? Why would OVH still publish infos about my domain? I'll try of course but I'm a bit confused here.
Relevant content
- Accepted Answerasked a month ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
You mean these? I didn't touch them. https://i.imgur.com/48wRbLx.png
What are your name servers set too in your domain? Not the zone but the name servers for your domain?
Use my link above to make sure the name servers set match your screen shot.
You update name server records in route53 per link not at ovh as you transferred the domain.
Oh ok I found it. Because the NS records were set automatically to AWS DNS I thought you would also make the change to the domain's DNS as well. But no. Plus I didn't know where to find the DNS names for my domain so I had to look around a bit, and then when I found them I realized they were still set to OVH's. It's fixed now. Thank you