ERR_NAME_NOT_RESOLVED On NGINX

Question

Hi I’m trying to connect to my website and I got this following error in Chrome: ERR_NAME_NOT_RESOLVED

I have run nginx -t as well as tail /var/log/nginx/error.log with no luck.

DNS OUTPUT from https://network-tools.com/nslookup:

Name	TTL Until Refresh	Class	Type	Data
loveofportugal.com.	3492	IN	A	104.248.243.249
loveofportugal.com.	1691	IN	NS	ns1.digitalocean.com.
loveofportugal.com.	1691	IN	NS	ns2.digitalocean.com.
loveofportugal.com.	1691	IN	NS	ns3.digitalocean.com.
loveofportugal.com.	1692	IN	SOA	ns1.digitalocean.com. hostmaster.loveofportugal.com. 1574866016 10800 3600 604800 1800

NGINX Sites-enabled file:

server {
        listen 127.0.0.1;

        root /var/www/loveofportugal.com/public;

        # Add index.php to the list if you are using PHP
        index index.html index.htm index.nginx-debian.html index.php;

        server_name loveofportugal.com www.loveofportugal.com;

        location / {
                try_files $uri $uri/ /index.php?$query_string;
        }

        location ~ \.php$ {
                include snippets/fastcgi-php.conf;
                fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
                fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
                include fastcgi_params;
         }

        location ~ /\.ht {
                deny all;
        }
}

I use GoDaddy as Domain hoster. All of the nameservers are pointing to digitalocean.

leocbce408bd80d706e5c24b19 · Answer

@alexdo

I have the same Issue with exact respond for my domain busboy.app

DNS OUTPUT from https://network-tools.com/nslookup:
Name	TTL Until Refresh	Class	Type	Data
busboy.app.	3600	IN	A	192.241.153.48
busboy.app.	1800	IN	NS	ns1.digitalocean.com.
busboy.app.	1800	IN	NS	ns2.digitalocean.com.
busboy.app.	1800	IN	NS	ns3.digitalocean.com.
busboy.app.	1800	IN	SOA	ns1.digitalocean.com. hostmaster.busboy.app. 1575337665 10800 3600 604800 1800

$ ping busboy.app
PING busboy.app (192.241.153.48) 56(84) bytes of data.
64 bytes from 192.241.153.48 (192.241.153.48): icmp_seq=1 ttl=49 time=108 ms
64 bytes from 192.241.153.48 (192.241.153.48): icmp_seq=2 ttl=49 time=259 ms
64 bytes from 192.241.153.48 (192.241.153.48): icmp_seq=3 ttl=49 time=100 ms
64 bytes from 192.241.153.48 (192.241.153.48): icmp_seq=4 ttl=49 time=106 ms
^C
--- busboy.app ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 100.942/143.772/259.335/66.777 ms

https://www.whatsmydns.net/ propagarion data

Reston VA, United States
Sprint
192.241.153.48
Dallas TX, United States
Speakeasy
192.241.153.48
Ashburn VA, United States
Cloudflare
192.241.153.48
Boston MA, United States
Speakeasy
192.241.153.48
New York NY, United States
Speakeasy
192.241.153.48
London ON, Canada
Golden Triangle
192.241.153.48
Sao Paulo, Brazil
Universo Online
192.241.153.48
London, United Kingdom
Verizon
192.241.153.48
Paris, France
France Telecom
192.241.153.48
Berlin, Germany
Strato
192.241.153.48
Bologna, Italy
Fastweb
192.241.153.48
Yeditepe, Turkey
Yeditepe University
192.241.153.48
St. Petersburg, Russia
Uni of Tech & Design
192.241.153.48
Karachi, Pakistan
My Solutions
192.241.153.48
Bhubaneswar, India
Ortel Communications
192.241.153.48
Bangkok, Thailand
Loxley Wireless
192.241.153.48
Petaling Jaya, Malaysia
Clear-Comm
192.241.153.48
Beijing, China
CNNIC
Malvern VIC, Australia
TPG Internet
192.241.153.48
Coolum Beach QLD, Australia
Telstra
192.241.153.48
Rotorua, New Zealand
Global Gateway
192.241.153.48

alexdo · Answer

Hello, @brittwittrup

Can you please confirm if your domain name is resolving/pointing to your droplet/server? What happens when you ping the domain name? If you’ve made any recent DNS changes, keep in mind that DNS changes might take up to 48 hours due to DNS cache. You can check the DNS propagation using this site: https://www.whatsmydns.net/

Regards, Alex

Related

Question

ERR_NAME_NOT_RESOLVED On NGINX

Related

Try DigitalOcean for free