How to tell where issue is between nameserver and reverse proxy?

I can publicly access the page i’d like to serve through my droplet IP at port 5000, but can’t reach it with my domain?

A “dig +trace” command gets responses from the DigitalOcean nameservers but nothing past that.

I have 3 NS records directing from my domain (@) to,, I have 2 A records saying hostnames * and @ will direct to my droplet IP. I have 1 CNAME record saying ‘www’ hostname is an alias of ‘@’. These were created weeks ago, it seems like they would be propagated by now.

I’m wondering if there’s something missing in my nginx configuration.

If my nginx config block looks like:

server {
   listen 80;
   server name;
   location / {
       proxy_pass    ;
       proxy_set_header   Host $host;
       proxy_set_header   X-Real-IP $remote_addr;
       proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
       proxy_set_header   X-Forwarded-Host $server_name;

is there anything else that is necessary to serve the page at my domain?


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

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.


As long as you have both of your www and your non-www versions pointing to your Droplet’s IP address it should work as expected.

Your Nginx looks correct, there’s only one thing that I’ve noticed which might be causing the issue, you need to change:

   server name;



Note the missing underscore. Then run a config test with nginx -t and if you get Syntax OK message, restart Nginx.

Regards, Bobby