| 2017-10-10 21:44:06 |
Scott Moser |
description |
$ ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Oct 6 12:00 /etc/resolv.conf -> ../run/resolvconf/resolv.conf
$ cat /etc/cloud/build.info
build_name: server
serial: 20171005.1
$ lsb_release -sc
artful
$ for p in resolvconf nplan; do dpkg-query --show $p; done
resolvconf
nplan 0.29
So what we see is the symlink points as if resolvconf was installed
and managing /etc/resolv.conf, but it is not and should not be. |
$ ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Oct 6 12:00 /etc/resolv.conf -> ../run/resolvconf/resolv.conf
$ cat /etc/cloud/build.info
build_name: server
serial: 20171005.1
$ lsb_release -sc
artful
$ for p in resolvconf nplan; do dpkg-query --show $p; done
resolvconf
nplan 0.29
So what we see is the symlink points as if resolvconf was installed
and managing /etc/resolv.conf, but it is not and should not be.
Note, that /run/systemd/resolve/resolv.conf is correct, just not used.
$ grep '^[^#]' /run/systemd/resolve/resolv.conf
nameserver 168.63.129.16
search ng102m4hnhaedfnxz3boonlkbb.xx.internal.cloudapp.net |
|
