Domain not working after pointing it: DNS_PROBE_FINISHED_NXDOMAIN and DNS propagation
After a DNS change the update usually appears within hours and can take up to 48. If it takes longer, the cause is usually a wrong record, unchanged nameservers or an expired domain, and waiting will not fix that.
Last updated:
How to point a domain at a server correctly
At your domain registrar, add an A record for the domain pointing to the server's IP, and a CNAME for www pointing to the domain. Or change the nameservers to the ones your host gave you, but not both.
See what the internet sees now
These commands show the current address and nameservers. 1.1.1.1 is a public DNS server, so if it gives the right answer and your computer does not, the problem is your computer's cache.
$ nslookup example.com 1.1.1.1 $ nslookup -type=ns example.com 1.1.1.1
Clear the DNS cache on your computer
Your computer and browser can keep the old address even after the change is complete. Clear it and reopen the browser. In Chrome you can also visit chrome://net-internals/#dns.
$ ipconfig /flushdns$ sudo dscacheutil -flushcache $ sudo killall -HUP mDNSResponder
Why it still does not work after 48 hours
The nameservers still point to the old provider, so nobody reads your new records. Or the record was made for the wrong name, the www record is missing, or the domain has expired or is not active at the registrar. Check the expiry date there.
The domain resolves but the site does not open
If the address is right, the problem is no longer DNS. The server must be set up to answer for this domain, so add it in your hosting panel or in Nginx or Apache, then see the guide on sites that do not open.