Re:Dns query fail

Question

Hi. I have set DNS record A record point to my elastic ip, but DNS query still fail. Use dns checker all no result waited more than 48 hours already.
I point www.mydomain.com to my elastic ip.set 300 ttl
NS record set to 4 records provided by aws.

Riku_Kobayashi · Accepted Answer

There may have been a problem when registering the domain.  
Just to be safe, I think it would be a good idea to open a case with AWS Support under "Account and billing" and inquire.  
Inquiries under "Account and billing" can be made free of charge.  
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-contact-support.html

If you share your actual domain, I can do a little more research.  
Is it possible to share the domain?

Riku_Kobayashi · Answer

Hello.

Is it possible to resolve the name of NS record with the following command?  
If the NS record cannot be resolved, the registered NS record may be incorrect.  
```
dig mydomain.com ns
```

I think that if the NS record was set correctly, you would be able to check the value of "Name servers" listed in the hosted zone details.  
![a](/media/postImages/original/IMdZstcJtWR4ObBeRA9n9IwQ)

Please check the following documents for other troubleshooting methods.  
https://repost.aws/knowledge-center/route-53-dns-website-unreachable

Frankfurt · Answer

They all not propagated.

Frankfurt · Answer

![Enter image description here](/media/postImages/original/IMNr_TBfH_QW6LhSXE5QZqSg)
Four records have been set same at the domain registrar ns records page.

Frankfurt · Answer

hi solved. 
the new ns record has to be the one assigned by aws, and not just edit it to use the previous one.
thanks a lot.

Frankfurt · Answer

Nameserver also changed and set correctly. But without a . at the back. Does it make sense? I can't change it even I set without a . at the back it will auto set to with a . at the back.

Frankfurt · Answer

;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 60483 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;twig.events. IN A ;; Query time: 9 msec ;; SERVER: x.x.x.x#53(x.x.x.x) ;; WHEN: Sun Aug 11 08:54:16 UTC 2024 ;; MSG SIZE rcvd: 40

Frankfurt · Answer

So should just leave it to propagate? I'm just afraid settings incorrect. But I confirm pointed a record to my domain.com and also ns set to the aws records.

Riku_Kobayashi · Answer

The domain I own also has a dot after the NS record, so there is no problem.  
Name resolution has failed because the status is "SERVFAIL".  
By the way, can you confirm that NS records are being propagated on the following websites?  
https://www.nslookuptool.com/

Riku_Kobayashi · Answer

By the way, is it possible for you to share your actual domain?  
It will be easier for users on AWS re:Post to troubleshoot if you also share an image of your hosted zone settings.

Also, please check if the results of searching your domain from the URL below and checking the NS records match the contents of Route53's NS records.  
https://lookup.icann.org/en

Re:Dns query fail

Relevant content