Question
Server IP address could not be found, after Droplet upgrade
- Posted on February 15, 2018
- DNSUbuntu
Asked by PhilDiscuss Team
Hello.
I upgraded my droplet (take snapshot, create droplet from snapshot, delete old droplet). All is success.
I notice that when I create new droplet from snapshot a New IP is served, so I manage my domain to point to the new IP of Droplet.
But now when I visit my site it says: This site can’t be reached www.domain.com’s server IP address could not be found.
ERR_NAME_NOT_RESOLVED
My DNS is ns1.digitalocean.com, ns2, ns3…
Can you please help?
Thank you.
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!
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.
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.
Hello. Thanks for the reply.
URL: https://www.phildiscuss.com
On my domain registrar the only record that I put there is the Nameservers(ns1.digitalocean.com, ns2… ns3…)
On my DO, DNS Record are: AAAA phildiscuss.com 2400:6180:0:d1::1ae:9001 A phildiscuss.com 159.65.132.141 NS ns1.digitalocean.com ns2.digitalocean.com ns3.digitalocean.com
It’s been 6 days, I hope 6 days is enough to propagate. LOL!
Thank you
Thank you for the reply.
Here is the link: https://www.phildiscuss.com
My domain will expired on Nov. 2018.
DO, domain config are: A-@-159.65.132.141 AAAA-@-2400:6180:0:d1::1ae:9001 ns1.digitalocean.com ns2.digitalocean.com ns3.digitalocean.com
And on my domain registrar, I only put the nameservers (ns1.digitalocean.com,ns2…,ns3…) as record there.
IDK
It’s been 6 days, I hope 6 days is enough to propagate.
Thank you.
Since DNS is not hosted on your droplet an upgrade or even downtime on your droplet would not cause the error you are seeing. Can you share the domain name you are encountering problems with? There are a few possible reasons you may see this error:
The second or last item here are the most likely based on your recent changes. To troubleshoot the second option, check your DNS record to ensure the IP is correct. For the last item, the best resolution is found by waiting for propogation but you can test this by changing your local DNS resolver to a publicly provided one like Google’s 8.8.8.8 and see if the domain then resolves. If it does, you will most likely just need to wait for your ISPs servers to pull the updated record.