- Newest
- Most votes
- Most comments
Hi neteng!
I ran a dig command on your domain trontv.com at 8.8.8.8, 8.8.4.4, 9.9.9.9, and 1.1.1.1 and it had resolved successful. I also tried with my EC2 instance's internal DNS and was successful also.
It seems like I am reading your post about 24 hours after you posted it, so I think the DNS records may have propagated by now. Note that caching DNS resolvers are outside the control of the Amazon Route 53 service and will cache your resource record sets according to their time to live (TTL)
-Michael
Yep , It was actually DNSSEC issue.
issue has been resolved by removing DNSSEC on Godaddy side.
Thanks
Issue due to DNSSEC on Godaddy side.
and It just got resolved by removing it from Godaddy control panel.
Thanks
Hello neteng,
I would like to let you know that at this time, Amazon Route 53 supports DNSSEC only for domain registration but does not support DNSSEC for DNS service:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-configure-dnssec.html
Google Public DNS performs DNSSEC validation for all DNS queries by default. So, when a name server fails DNSSEC validation, it returns SERVFAIL/NXDOMAIN.
As you had DNSSEC enabled for your domain and since DNSSEC is disabled with the DNS service (Route 53), the Google Public DNS resolver was returning SERVFAIL error to clients.
Therefore, the issue got resolved when you disabled DNSSEC for your domain on your Registrar i.e. GoDaddy.
Edited by: Charu-aws on Jun 10, 2019 12:08 AM
Relevant content
- asked 9 months ago
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago