Domain unresolved - dig SERVFAIL message

Question

I created a AWS Linux 2 instance and associated an Elastic IP address with it. I registered my domain within Route 53, created a public Hosted zone, and created the appropriate A record.

pubarts.agency A 3.20.149.98 - - 300

But the domain does not resolve (after several hours). I can hit the server using the IP address, but all attempts to resolve by domain name fails.

Dig gives the following results, which I see is a failure, but I don't know how to resolve.

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-9.P2.amzn2.0.2 <<>> pubarts.agency
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 28820
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;pubarts.agency. IN A

;; Query time: 770 msec
;; SERVER: 172.31.0.2#53(172.31.0.2)
;; WHEN: Sat Feb 08 01:27:15 UTC 2020
;; MSG SIZE rcvd: 43

Accepted Answer

Hi,  
  
Name servers appear in three places, and typically they should all be in synch:  
~ The name servers that Route 53 assigns to a hosted zone when you create it. These are the "master" name servers and can't be changed. Name servers in the other locations usually match these.  
~ The name servers in the NS record in the hosted zone.  
~ The name servers that are associated with the domain registration. These are the name servers that control which DNS configuration is in use.  
  
In your case, the first two sets of name servers match. However, the name servers for the domain registration are different. I'd guess that you had another hosted zone named  	pubarts.agency, you deleted it, and then created another pubarts.agency hosted zone. Route 53 assigned four new name servers to the new hosted zone. You now need to update the domain registration to use the new name servers.  
  
Here's how to fix that:  
1. Get the name servers that Route 53 assigned to the hosted zone when you created it. See "Getting the Name Servers for a Public Hosted Zone" in the _Route 53 Developer Guide_:  
  
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/GetInfoAboutHostedZone.html  
  
2. Update the domain registration to use the name servers that you got in step 1. See "Adding or Changing Name Servers and Glue Records for a Domain":  
  
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html  
  
Scott

Answer

That did the trick.  You are absolutely correct, I flushed the original hosted zone and created a new one - but I did not check the name servers.  
  
Thank you very much, Scott!

Domain unresolved - dig SERVFAIL message

相關內容