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

  • 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.

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

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.

21 answers

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

I has the same problem, please can you help me?

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

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

Our nameservers are set up with a very low TTL so DNS changes should be nearly instant. If you can share the domain name you’re having trouble with I’d be happy to take a closer look.

same with me hifebriansyah.com i changed from to, but some how it still stuck at until this time..

Same problem, I even delete the Networking and it is still redirecting to a shared server I register at A record

I’m having some issues myself, still showing the godaddy parking page

How much down time did you experience?

Same problem here. It’s 4 days already

Having the same issue every time I set up a new record. Always think it’s broken, change it multiple times (with large gaps between) until I give up. Wait a few days and it works.

I have the same problem… any solution? i have to wait?

2019 and the same problem. The case occur when change IP with the API. In the panel show correct IP changed, but not propagating. Waiting for two days

I have the same issue. How much time I have to wait until the new IP Address takes effects?

Waiting 4 days it is too much. Is there any problem with Digital Ocean?.

DO guys… your DNS is broken. I have updated 1 A record and added a new A record 30 minutes ago and it still hasn’t propagated funny thing is, it is not even “caught” by the DO droplet.

Please fix this!!

Same problem!!! Please answer digitalocean

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.

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

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

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

Submit an Answer