Question

Droplets showing DNS name resolution issues?

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.

Example:

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/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://mirror.linux.duke.edu/pub/centos/7.3.1611/extras/x86_64/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?


Submit an answer


This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

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.

Accepted Answer

I’m also having problems with my servers in SFO1, I would change to the openDNS servers 208.67.220.220 and 208.67.222.222.

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.

This comment has been deleted

    Try DigitalOcean for free

    Click below to sign up and get $200 of credit to try our products over 60 days!

    Sign up

    Get our biweekly newsletter

    Sign up for Infrastructure as a Newsletter.

    Hollie's Hub for Good

    Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

    Become a contributor

    Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

    Welcome to the developer cloud

    DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

    Learn more
    DigitalOcean Cloud Control Panel