DNS Record not updated or changing ? How long it will take to effect

I have a website running on one droplet and my domain settings was on Digital Ocean DNS and its all working fine. I made a new website on different droplet machine. I have changed A record of my website to this new IP of droplet machine but it takes more than 48 hours, but still it points out to my old droplet machine IP…

I don’t understand what was an issue ? Usually DNS update records at 12 hrs maximum as its already have name servers of digital ocean just change the droplet machine IP but it didn’t happen


having this issue as well, this ticket is 2 years old. Any update?

I am having the same issue. After updating an ‘A’ record which now points to my new LoadBalancer for kubernetes cluster, it has not taken effect for 3 days. Even a simple ping request is still taking me to prior IP address of an LB which no more exists.

Appreciate any help.

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.

Also observed as of October 6, 2020. Created droplet few days ago. Yesterday with TTL 3600 for the new domain, created new A record with correct IP address for the new droplet … and nothing …

It seemed like I was just encountering the same problem. But I’m thinking that a potential cause for the problem could be that the computer you are using has its own DNS cache which isn’t necessarily being updated, so that would need to be flushed so that the computer is forced to check the DNS records for your server. It’s a bit hard to confirm this as being a solution for everyone else but it is something that has just worked for me so I hope that it helps someone who is stuck with this problem!

Commands to flush your computer’s DNS cache

Mac (Note that this doesn’t work on all OSX versions):

sudo killall -HUP mDNSResponder


ipconfig /flushdns

Linux (Ubuntu):

sudo systemd-resolve --flush-caches

So I guess this is just part of DO then, I updated my pod versions and all my lbs went down. I switched the records to a healthy cluster and its all dead. Seems like DO is just plain shit. Theres also no way to contact support about it either.

First step is to check the dns TTL against digitalocean name server, and the dns server you are using.


dig @ is google dns server if you are using that.

The Time to Live (TTL) is under Answer Section e.g. my 3699 IN A <IP address> where 3699 is the number of seconds before the cache expires.

You will have to wait till that time is over.

Alternatively if you are using google dns server for lookups, try to flush it at Google’s DNS Cache, though to my experience, it’s not guarantee the dns get refresh at the edge.

Did any of you try clearing your local DNS cache as “demaine” suggested on October 24, 2019 ? Did it help?

I found if I modify the DNS entry it doesn’t update. I had to delete it and recreate it and it immediately worked.

Updated on a Thursday and it is Saturday and still not routing to new IP. Seriously disappointed.

This comment has been deleted

Same issue here as well, waiting for 48hours now but no change in DNS records, DO guys are you listening ??? this is raising big question on DO services.

Dear Support. We pay money for your services and I see that you don’t answer to your customers. Is there any issue with your support department?

I experience the same issue, making me waiting for more than 2 days for changes to take effect.

Is someone going to solve this or at least answer once?

Regards, Dmitri