Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
NGINX multiple non-ssl based domains redirecting to same domain. Question Question
400 Error, Bad Request when visiting domain name, IP address loads fine Question Question

Question

DNS Not Resolving to IP

Posted November 21, 2020 777 views
NginxDNS

Hello, I have a Docker droplet set up with a .NET Blazor app. I can access the app through the IP address no problem.

My domain is registered through Google Domains, and three days ago I changed the DNS servers to DigitalOcean. I turned off DNSSEC, waited two days, then entered the Digital Ocean name servers. Three days later and my domain is still not resolving.

On the Digital Ocean side, I have an A record at the root which directs to my droplet IP address. I have three NS entries at the root which direct to the three Digital Ocean name servers.

nslookup mysite.com returns the IP address of my droplet. I have tried clearing the local DNS cache on both my machines.

Is there something I could be missing?

Thanks!

Add a comment
TurboLaser
By:
TurboLaser

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
NGINX multiple non-ssl based domains redirecting to same domain. Question Question
400 Error, Bad Request when visiting domain name, IP address loads fine Question Question

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.

×
Submit an Answer
2 answers
bobbyiliev November 22, 2020

Hi there @jghtch,

It does not sound like an issue with the DNS, as when running nslookup you get your IP address back, which means that the DNS is configured correctly.

I could suggest trying out this tool to see if you also get back the correct IP address as your A record:

https://www.digitalocean.com/community/tools/dns

Lately, I’ve noticed that some browsers like Chrome redirect http:// to https:// by default, and if you don’t have SSL installed on your server, the connection will time out. You could try accessing your domain via http:// directly and see if it loads.

If this is the case, I could suggest installing an SSL certificate so that your domain could work with both http:// and https://. You can use Let’s Encrypt as a free SSL certificate provider.

I hope that this helps!
Regards,
Bobby

Reply Report
TurboLaser November 22, 2020

Hi @bobbyiliev thanks for the reply.

I do get my IP back using the Digital Ocean DNS tool you linked.

I don’t believe I have SSL installed on my server yet, so that could be part of the problem. The site doesn’t load over http however.

Reply Report

Related

Looking for something else?

Ask a new question Search for more help