Ubuntu
network-manager package

  1. Bug #1051348
  2. Comment #6

Comment 6 for bug 1051348

Revision history for this message
Thomas Hood (jdthood) wrote : Re: No resolving after upgrade from 12.04 to 12.10 beta

@Jason: From the log you posted it appears that resolvconf is now configured correctly.

Was /etc/resolv.conf simply non-existent on your system before your created the symlink?

Do you have any idea *why* /etc/resolv.conf was not there, or not a symlink to ../run/resolvconf/resolv.conf? Normally the resolvconf package postinst script creates this symlink.

When /etc/resolv.conf is not present, glibc falls back to the default of "nameserver 127.0.0.1". In Precise the NetworkManager-controlled dnsmasq process listens at 127.0.0.1, so if the resolv.conf file is absent and NM-dnsmasq is running then you still have name service. In Quantal the NetworkManager-controlled dnsmasq process listens at 127.0.1.1, so if the resolv.conf file is absent then you end up with no name service. As a result of this change we can expect a number of bug reports to be filed by people who had no /etc/resolv.conf on their system, still had name service under Precise, and no longer have name service after upgrade to Quantal. Get ready for this, especially in light of bug report #1000244.