- Newest
- Most votes
- Most comments
Hello.
Is Route53 managing the domain you are accessing?
You can check the NS record for a domain by executing the following command.
Does this result match the Route53 NS record?
And while you're at it, check the A record.
dig Domain.com ns
dig Domain.com a
Incidentally, if you are managing outside of Route 53, you will need to register an alias with a CNAME record instead of an A record to register the DNS name of the ALB.
You cant have an A record pointing to the ALB DNS Name assuming your not using Route 53
You will need to create a CNAME to point to your ALB DNS record for resolution to work
Thank you for your response. In my case, I am indeed using Amazon Route 53 as my DNS service. When you are using Route 53 and want to associate a domain with an AWS resource like an Application Load Balancer (ALB), it's recommended to use an 'Alias' record, not a CNAME.
Alias records in Route 53 allow you to create a DNS alias to an AWS resource, including an ALB, and they automatically handle the resolution of the ALB's DNS name. This is important because ALBs do not have static IP addresses, and using an Alias record ensures that the DNS resolution is always up to date, even if the ALB's IP address changes.
So, to clarify, when using Amazon Route 53 with an ALB, it's best to create an Alias record pointing to the ALB DNS name for accurate and dynamic resolution
Ok yes that’s correct for route 53. Please confirm your NS records are correct on your domain. The domain is public and your alias record for the domain is blank for the record name but pointing to your alb. Screenshots would help here without giving too much into away
If briefly, NXDOMAIN means that the authoritative nameserver didn't have a record of the specified domain name. This troubleshooting guide covers the most common scenarios with NXDOMAIN. A complete dig +trace output (as described in the guide) can help pinpoint the problem if you need further assistance.
Relevant content
- Accepted Answerasked 2 years ago
- asked 3 years ago
- asked a year ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
; <<>> DiG 9.10.6 <<>> Domain.in ns ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 25736 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;Domain.in. IN NS
;; Query time: 6 msec ;; SERVER: fe80::b814:4dff:fe78782:ad64%11#53(fe80::b814:4dff:fe82:ad64%11) ;; WHEN: Fri Sep 22 19:33:34 IST 2023 ;; MSG SIZE rcvd: 41
I've created a hosted zone in Amazon Route 53 and copied the nameservers provided by Route 53. Then, I went to GoDaddy, where I originally purchased my domain, and replaced their default nameservers with the ones from my Route 53 hosted zone. This action delegates the DNS resolution for my domain to Route 53. Despite this configuration, I'm encountering a 'SERVFAIL' issue when trying to access my website through the domain name. Any guidance on resolving this issue would be greatly appreciated.
The following document provides general troubleshooting instructions when a DNS SERVFAIL occurs with Route53. https://repost.aws/knowledge-center/route53-dns-servfail-response
It may be related to the TTL of the NS record, etc. So it is conceivable that waiting a day or so may fix the problem.