Why is the DNS in the Debian 10 image broken after a brand new rebuild?
Who should I be nagging to get this fixed?
I rebuilt my droplet with the ‘Debian 10.0 x64 Base Image’.
I logged in, and ran 'apt-get update’.
root@droplet:~# apt-get update Err:1 http://mirrors.digitalocean.com/debian buster InRelease Temporary failure resolving 'mirrors.digitalocean.com' Err:2 http://mirrors.digitalocean.com/debian buster/updates InRelease Temporary failure resolving 'mirrors.digitalocean.com' Err:3 http://mirrors.digitalocean.com/debian buster-updates InRelease Temporary failure resolving 'mirrors.digitalocean.com' Err:4 http://mirrors.digitalocean.com/debian buster-backports InRelease Temporary failure resolving 'mirrors.digitalocean.com'
After searching around I found a few dozen hits about the DNS on the Debian image being broken out of the box on digitalocean because the 'resolv.conf’ has screwed up permissions A completely new rebuild based on the provided based image has 0660 instead of the correct '0644’
# stat /etc/resolv.conf File: /etc/resolv.conf Size: 83 Blocks: 8 IO Block: 4096 regular file Device: fe01h/65025d Inode: 6753 Links: 1 Access: (0660/-rw-rw----) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2019-11-21 18:35:12.569400331 +0000 Modify: 2019-11-21 18:24:19.182513860 +0000 Change: 2019-11-21 18:50:37.687215552 +0000
Who do we get to actually fix this, so people using Debian don’t have a broken system out of the box?
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.×