I’ve bought a domain since it’s a .dk the DNS records must be changed at which I have done, this is the current config.

Current nameservers

No other configurations can be done at dk-hostmaster.

I configured my DNS records like this:

A	directs to		3600
NS	directs to	1800
NS	directs to	1800
NS	directs to	1800

I then followed this tutorial on how to setup Nginx

However when I reached the point where I should be able to go to I get the error

This site can’t be reached’s server IP address could not be found.

When I try to connect to the IP directly it works eg shows test

After looking at multiple previous answers on similar questions, I changed my DNS records to this:

CNAME	*		is an alias of			43200
CNAME	is an alias of			43200
A		directs to		3600
NS		directs to	1800
NS		directs to	1800
NS		directs to	1800

But still it doesn’t work.

I have an index.html located in /var/www/ this file should output something like works! and I have an index.html located in /var/www/html/index.html this file outputs test It’s this file you see when you connect to the ip directly.

I have a file located in /etc/nginx/sites-available/ which contains the following:

server {
        listen 80;
        listen [::]:80;

        root /var/www/;
        index index.html index.htm index.nginx-debian.html;


        location / {
                try_files $uri $uri/ =404;

This file is linked with sudo ln -s /etc/nginx/sites-available/ /etc/nginx/sites-enabled/

My Nginx Config file looks like this

user www-data;
worker_processes auto;
pid /run/;
include /etc/nginx/modules-enabled/*.conf;

events {
	worker_connections 768;
	# multi_accept on;

http {

	# Basic Settings

	sendfile on;
	tcp_nopush on;
	tcp_nodelay on;
	keepalive_timeout 65;
	types_hash_max_size 2048;
	# server_tokens off;

	server_names_hash_bucket_size 64;
	# server_name_in_redirect off;

	include /etc/nginx/mime.types;
	default_type application/octet-stream;

	# SSL Settings

	ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
	ssl_prefer_server_ciphers on;

	# Logging Settings

	access_log /var/log/nginx/access.log;
	error_log /var/log/nginx/error.log;

	# Gzip Settings

	gzip on;

	# gzip_vary on;
	# gzip_proxied any;
	# gzip_comp_level 6;
	# gzip_buffers 16 8k;
	# gzip_http_version 1.1;
	# gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;

	# Virtual Host Configs

	include /etc/nginx/conf.d/*.conf;
	include /etc/nginx/sites-enabled/*;

#mail {
#	# See sample authentication script at:
#	#
#	# auth_http localhost/auth.php;
#	# pop3_capabilities "TOP" "USER";
#	# imap_capabilities "IMAP4rev1" "UIDPLUS";
#	server {
#		listen     localhost:110;
#		protocol   pop3;
#		proxy      on;
#	}
#	server {
#		listen     localhost:143;
#		protocol   imap;
#		proxy      on;
#	}

In the Nginx error log this is everything 2019/01/03 14:16:33 [notice] 13789#13789: signal process started

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.

Andy Hattemer
DigitalOcean Employee
DigitalOcean Employee badge
January 4, 2019
Accepted Answer

Looks like it’s working now, right?

ERR_NAME_NOT_RESOLVED usually indicates a DNS caching issue, I bet it was either a slow update on’s side, or cached DNS lookup info on your local network.

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel