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 buster InRelease
  Temporary failure resolving ''
Err:2 buster/updates InRelease
  Temporary failure resolving ''
Err:3 buster-updates InRelease
  Temporary failure resolving ''
Err:4 buster-backports InRelease
  Temporary failure resolving ''

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?

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

Hi there @nwesdnetops,

Thanks for reporting this!

It seems that this an issue that occurs when a Droplet is rebuilt with a base image that’s from a different OS family than the Droplet was originally created with.

Our team is looking into this and how to best fix it, but for now, if you need to fix this for your Droplets, manually fixing the file permission as you did should work fine.

Creating a fresh Droplet from the base image will also result in the correct file permissions, so that would also be an alternative solution for now :)

You can find out more about rebuilding Droplets in our documentation: (We’ll be updating this to be more clear about the potential issues of rebuilding to a different OS family base image).

Hope that helps! - Matt.