ping: Temporary failure in name resolution


I have a problem with my Droplet, which I believe I caused myself and can’t get out of it. Basically I’m unable to ssh into the droplet (18.04, failed upgrade to 20.04), and can’t access outside internet from it. Below are the things I tried so far (apart from fully turning off and rebooting the droplet numerous times):

ssh into the server results in: ssh: connect to host port 22: Connection timed out

From the droplet:

$ ping
ping: Temporary failure in name resolution

Contents of /etc/systemd/resolved.conf:

$ ufw status
ERROR: Couldn't determine iptables version
$ ifconfig -a
lists eth0 and lo, both running
$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

source /etc/network/interfaces.d/*

auth eth0
iface eth0 inet static

… and probably bunch of other things which I will mention when I recall all of them… Also I don’t care about fully resurrecting the droplet, I need to make some data backup and destroy it. For that though I need outside access, besides the “Access console”.

What am I missing?

Thanks, Lukasz

Show comments

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hi @LukaszFormela,

First try making your resolv.conf be the following:

options edns0

If this doesn’t work, I’ll suggest contacting DigitalOcean’s support. I was going to ask you to check the contents of your /etc/netplan/50-cloud-init.yaml file and see if everything there looks properly configured however there might be some misconfiguration which you won’t be able to see so better to contact support.

You can reach them here:

Please do keep me in the loop though! I’m interested to see how this would be resolved.