Question

There is something wrong with my DSN domain configuration that I can't understand

Hello everybody,

I have a problem with my droplet DSN configuration. Five days ago I bought a new domain on Godaddy and I set it up in order to point the droplet ip out by configurating the nameservers:

my domain: www.marcolorenzetti.dev droplet ip: 161.35.227.204

ns1.digitalocean.com ns2.digitalocean.com ns3.digitalocean.com

The propagation has gone well as I received an email by GoDaddy saying so, but as you can see, the requests to the domain above retrive a error (sometimes showing a 404 bad request).

What is weird is that I can reach out my website only by Tor browser (not always actually) and this is uncomprensible for me. Nevertheless, this suggest me that the problem is in my network configuration on Digital Ocean but I can’t figure out waht is it.

I belive I created a proper record on it, this is my download zone:

$ORIGIN marcolorenzetti.dev. $TTL 1800 marcolorenzetti.dev. IN SOA ns1.digitalocean.com. hostmaster.marcolorenzetti.dev. 1602252637 10800 3600 604800 1800 marcolorenzetti.dev. 1800 IN NS ns1.digitalocean.com. marcolorenzetti.dev. 1800 IN NS ns2.digitalocean.com. marcolorenzetti.dev. 1800 IN NS ns3.digitalocean.com. www.marcolorenzetti.dev. 3600 IN A 161.35.227.204 marcolorenzetti.dev. 3600 IN A 161.35.227.204

I also check out the server configuration, I added my new domain to the ip address already listed in my Nginx config file and in my settings.py file (it’s a django project).

Last but not least, I didn’t configurate the SSL standard certificate that was included in the package. Could it be the problem? I don’t think so.

Please someone help me.


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.

Accepted Answer

Hi there @marklore,

Yes, your DNS configuration looks absolutely correct.

The problem is due to the redirect from HTTP to HTTPS, but you don’t seem to have an SSL certificate installed.

What you could do is follow the steps here on how to install Let’s Encrypt certificate for Nginx:

https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-18-04

Hope that this helps! Regards, Bobby

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.