Martin wrote: > So NM needs to be taught where to write DNS servers > for static configurations when resolvconf is installed/enabled.
When resolvconf is installed, as indicated by the presence of /sbin/resolvconf, NM doesn't write out a file but pipes the content to the /sbin/resolvconf script which does the right thing with it. At least, that is what is supposed to happen. My guess is that the following happens in your case. * NM has already written /etc/resolv.conf * Resolvconf is installed; the postinst copies the content of that file to /etc/resolvconf/resolv.conf.d/original and to /run/resolvconf/resolv.conf * Something causes resolvconf to do an update; resolvconf writes out an empty /run/resolvconf/resolv.conf because it has no nameserver information in its database yet If this is what is happening then it should suffice to disable and enable networking via the indicator. When NM reconnects it will send nameserver information to resolvconf which will put that info in /run/resolvconf/resolv.conf. If that does not suffice, does rebooting suffice? What versions of network-manager and resolvconf are you using? Assuming that it does suffice to disable and re-enable networking, or to reboot, I would remark that the user shouldn't have to do that. NM and other interface configurers should notice the installation of resolvconf and should send resolvconf their info. There is a mechanism for this. I notice that someone has already requested that this functionality be added to n-m: bugs.debian.org/639803. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1053236 Title: does not write static nameservers into resolvconf config Status in “network-manager” package in Ubuntu: New Bug description: I just helped a friend upgrade to 12.04, he lost DNS after the upgrade. /run/resolvconf/resolv.conf only had the comment, but no actual contents. He has a static IP/DNS etc. configured in NetworkManager (no DHCP at all). Before resolvconf, NM wrote a correct /etc/resolv.conf with the configured DNS server. After the upgrade, /var/lib/dpkg/info/resolvconf.config decided that /etc/resolv.conf was generated by NM and decided to not set resolvconf /link-tail-to-original, so that it was only moved to /etc/resolvconf/resolv.conf.d/original, but not linked to "tail" (where it would get active). This is a correct behaviour from resolvconf's point of view, I think. So NM needs to be taught where to write DNS servers for static configurations when resolvconf is installed/enabled. NM should not constantly touch files in /etc/ at all then (i. e. please don't just write it into /etc/resolvconf/resolv.conf.d/tail), instead it should either be written directly to /run, or resolvconf should get a script which queries the current DNS and puts it into the generated script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1053236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
