Question

my domain Is stuck to an old IP address of my old droplet instead of new droplet

I Moved my domain (aivocalremover.com) to another droplet. (from droplet-161.35.71.36 to droplet-167.99.132.209). I also setup the A records appropriately as shown in the attached image. But the domain still continues to be connected to the old droplet. If i turn off the old droplet, the domain name starts returning error 503 till i turn it back on. Please help me look into this. Thanks


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.

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.

For others having same issue. Here is what happened.

I forgot to replace the update the ip address in virtualhost file -

sudo nano /etc/apache2/sites-available/000-default.conf

Hi @alexdo.

Its been 72 hours and the domain name is still pointing to my old droplet.

Hello @ismailosunlana

The DNS might take up to 24 hours in order to fully update due to DNS cache.

However, since you’ve conducted tests with the old droplet being powered off and this leading to a 503 error, there’s clearly a misconfiguration on the new droplet.

Have you examined the server logs to gather more information about the error itself? Would you mind sharing more details on the setup itself?

503 Service Unavailable server error response code indicates that the server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded.

You can check if the web server (Apache/Nginx/Node) is running as well as other services that are related to your site/application.

Regards