Problems with Digital Ocean DNS lookups


(Jay Pfaffman) #1

This is the first time I remember seeing any problems with Digital Ocean in the couple years I’ve been dealing with them. They use Google’s DNS servers by default, and Google is rate-limiting them. I don’t know whether this is in all data centers, but I know it’s in NYC2 (where I typically install for my clients). digitaloceanstatus.com has some info at the top of the page.

If you’re having strange problems and/or rebuilds are failing, this is likely why.

A fix (recommended by Digital Ocean) is to edit /etc/resolv.conf (e.g., nano /etc/resolv.conf) and replace the name server lines that are there with OpenDNS’s servers.

nameserver 208.67.222.222
nameserver 208.67.220.220

On the next reboot (which for my install customers will be soon after the next security update that requires a reboot), /etc/resolv.conf will be re-written with Google’s name servers.


(Jeff Atwood) #2

Not a new issue, though:

https://news.ycombinator.com/item?id=11353617


(Michael - DiscourseHosting.com) #3

What / where is your source? Can’t find that bit of info anywhere…


(Jay Pfaffman) #4

A response to the trouble ticket that I filed.

and http://digitaloceanstatus.com/ says:


(Matt Palmer) #5

apt-get install unbound ftw.


(Jay Pfaffman) #6

I just heard back on my ticket: