Droplets showing DNS name resolution issues?

March 27, 2017 3.8k views

Anyone noticed issues with DNS resolution issues with various linux applications on their droplets?

While I can get IPs from nslookup, apps like yum seem to be having resolution errors.


Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64 error was
12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64: (28, 'Resolving timed out after 30545 milliseconds')
http://centos.firehosted.com/7.3.1611/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://centos.firehosted.com/7.3.1611/extras/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 30545 milliseconds')
Trying other mirror.
^Chttp://mirror.linux.duke.edu/pub/centos/7.3.1611/extras/x8664/repodata/repomd.xml: [Errno 12] Timeout on http://mirror.linux.duke.edu/pub/centos/7.3.1611/extras/x8664/repodata/repomd.xml: (28, 'Resolving timed out after 30878 milliseconds')
Trying other mirror.
http://ftpmirror.your.org/pub/centos/7.3.1611/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://ftpmirror.your.org/pub/centos/7.3.1611/extras/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 30545 milliseconds')
Trying other mirror.
http://mirror.cs.vt.edu/pub/CentOS/7.3.1611/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://mirror.cs.vt.edu/pub/CentOS/7.3.1611/extras/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 30546 milliseconds')
Trying other mirror.

ping resolves, but seems rather slow in pulling up the ip or doing pings.

Looking at the droplet's load time, I am not seeing hardly any load and I rebooted the droplet recently as well.

Anyone else having similar issues?

5 Answers
reednj March 27, 2017
Accepted Answer

I'm also having problems with my servers in SFO1, I would change to the openDNS servers and

SFO1, I believe.

It looks like Google DNS is hammered or something. I pointed my droplet to Level 3's DNS. I would list the link I got it from, but the community forum flagged it as spam.

  • I am on SFO1 and using Google DNS servers as well. I have been experiencing DNS resolution issues for the past 12 hours.

What servers are you using for resolving on the server?

sudo cat /etc/resolv.conf

At the moment, nameservers are and

Can't find any information for setting a closer DNS at the moment. But seeing that in nslookup now, it seems to be having issues with one of them, but refers to pulling non-authoritive answer from

  • @keiichi25
    Where's your droplet located - in which data center? Maybe there's issues with Google DNS in that region (sadly, that's not the first time this has happened)

Have another answer? Share your knowledge.