Report this

What is the reason for this report?

Apt error: Temporary failure resolving 'deb.debian.org'

Posted on July 24, 2017
J K

By J K

Apt is throwing a dns error. :(

This is digitalocean’s image, and I haven’t done anything on it yet. (Other than changing the dns servers from google to opendns, didn’t work with google’s dns servers either).

“”" Err:1 http://deb.debian.org/debian stretch InRelease Temporary failure resolving ‘deb.debian.org’ Err:2 http://security.debian.org stretch/updates InRelease Temporary failure resolving ‘security.debian.org’ Err:3 http://deb.debian.org/debian stretch-updates InRelease Temporary failure resolving ‘deb.debian.org’ Reading package lists… Done W: Failed to fetch http://deb.debian.org/debian/dists/stretch/InRelease Temporary failure resolving ‘deb.debian.org’ W: Failed to fetch http://security.debian.org/dists/stretch/updates/InRelease Temporary failure resolving ‘security.debian.org’ W: Failed to fetch http://deb.debian.org/debian/dists/stretch-updates/InRelease Temporary failure resolving ‘deb.debian.org’ W: Some index files failed to download. They have been ignored, or old ones used instead. “”"

“”" root@leobuilt:~# ping deb.debian.org PING static.debian.org (5.153.231.4) 56(84) bytes of data. 64 bytes from senfter.debian.org (5.153.231.4): icmp_seq=1 ttl=49 time=154 ms 64 bytes from senfter.debian.org (5.153.231.4): icmp_seq=2 ttl=49 time=153 ms “”"

“”" root@leobuilt:~# cat /etc/resolv.conf nameserver 208.67.222.222 nameserver 208.67.220.220 “”"



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!

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.

We had the same problems today with droplets on which we used the rebuild feature to upgrade the base image. Newly created droplets were not affected but all Droplets which we upgraded from an older Debian version to Debian 9 were affected. The only workaround we found so far is to rebuild the machine with the Debian 8.9 base image and then upgrade the OS manually:

https://linuxconfig.org/how-to-upgrade-debian-8-jessie-to-debian-9-stretch

Good question! I sorta solved it by just installing Arch Linux.

I have exactly same problem here. The droplet I have build before (debian 9.0) is working nicely (FRA1 data center), but the droplet I rebuilded today (debian 9.1, FRA1) can’t ‘resolve anything’ using apt-get or aptitude. It’s amazing becouse ping and wget are still working fine to the same addressess. I’m also able to use ssh. So I think it isn’t a network problem, but an issue of apt.

I can work now with the other droplet for couple of days, but I would appreciate any workaround there…

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.