How to fix DNS resolution?

Hi Everyone, newbie here. I have set up and redirected my domian with (AWS Route53) to Digital Ocean nameserver but I am still have problem with DNS resolution. I ran a demo app in Python (using Django) virtual environment but the page was unable to load with error message,’ Connection Timed Out’. Please see what I have setup on AWS and DO control panel. I will greatly appreciate your help. Thank you very much. AWS route 53:

Digital Ocean: A record >>>>>> droplet ip_address NS >>>> NS >>>> NS >>>>

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

@unixynet After following the information you provided, I was able to resolve my DNS. I greatly appreciate your input and thank you very much.

You don’t need to setup DNS at both Digitalocean and Route 53. One should do. But at either one of these there needs to be an A record defined to point at your droplet’s IP. Right now your domain’s whois info still shows AWS 53 as your name servers:

 $ whois -f|grep Server
   Registrar WHOIS Server:
   Name Server: NS-1438.AWSDNS-51.ORG
   Name Server: NS-1969.AWSDNS-54.CO.UK
   Name Server: NS-464.AWSDNS-58.COM
   Name Server: NS-652.AWSDNS-17.NET

But the above name servers refuse to answer basic DNS queries against

$ dig +norec

; <<>> DiG 9.10.3-P4-Ubuntu <<>> +norec
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, **status: REFUSED**, id: 57295
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;		IN	A

;; Query time: 37 msec
;; WHEN: Tue Oct 02 18:28:57 CDT 2018
;; MSG SIZE  rcvd: 33

This means there’s a misconfiguration at Route 53’s end. That’s where I’d check things.