my domain stuck to an old IP address associated to a droplet i destroyed and now cant get it to connect to my new ip

My domain name is stuck to a droplet Ip I destroyed… I created a new droplet and added the same domain but it does not connect to my new ip because is still connected to the old droplet I destroyed… I don’t know what to do please help…I don’t know if its associated with the digital ocean nameservers


Submit an 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.

Hi @CuteAquamarineSnorkler,

You’ll need to change the DNS of your Domain to point to your new Droplet.

Basically, at the moment the DNS of your Domain is still pointing to your previous Droplet. What you’ll need to do is first check where your NameServers are.

NameServers tell the whole world where the should look for your DNS. Basically, when I try to load your website, my computer sends a request and sees where your NameServers are pointing at and that’s where it’s searching for the proper DNS records. So, what you can do is use the website:

In there put your domain and from the DropDown menu next to the domain box select the NS line and click Search. This will show where your DNS is being managed.

If it’s DigitalOcean, you can change the DNS record from your Control Panel, if it’s somewhere else, you’ll need to contact the support there to help you sort it out.

Once you know where your DNS is being controlled and you can change the DNS. You’ll need to change two records your main/root A record and your www A record. Both there records will show your old droplet’s IP address. Change it to the new IP.

If your DNS is being managed by DigitalOcean, check the following documentation. It can show you how to manage it properly:


I will be happy to provide assistance with your query here.

You need to check the delegation of the domain in this scenario because the queries will get answered from the DNS zone to which your domain is delegated to. For example: If your domain is delegated to DigitalOcean, then making changes to the DNS zone on the cloud panel will be effective.

If your domain is using the registrar nameservers then you need to make changes to the A record on the registrar panel for changes to take the effect.

You can check the domain delegation through its NS records. This online tool will be helpful:

After you have identified the NS records are of DigitalOcean or your registrar then making the changes to A record on the relevant platform will resolve the issue.