Scenario

• co-locate bosh-dns release on a VM; this creates an entry in /etc/resolv.conf using the file /etc/resolvconf/resolv.conf.d/head
• remove bosh-dns release from the VM

Expected

• There is no entry in /etc/resolv.conf or /etc/resolvconf/resolv.conf.d/head pointing to bosh-dns anymore

Actual

• The file /etc/resolvconf/resolv.conf.d/head is still there, therefore bosh-dns is still in /etc/resolv.conf

Proposed Solution

• drain should delete the file /etc/resolvconf/resolv.conf.d/head, just in case the release gets removed

Current Workaround

• recreate the VM
• should we have used https://github.com/cloudfoundry/bosh-dns-release/blob/master/jobs/bosh-dns/spec#L68 and deploy first with it switched to off, then a second time to remove bosh-dns entirely?