> Actually it doesn't. In the absence of /etc/resolv.conf the resolver simply defaults to
> the configuration equivalent to "nameserver 127.0.0.1".
Weirdly, I've multiple 14.04 machines (including freshly installed) here that lose name resolving abilities after removing /etc/resolv.conf. Only Firefox continues to work until restart, but eg. ping www.google.com immediately reports unknown host. If I move the symlink back, resolving works.
> Install 12.04
> Do `rm /etc/resolv.conf`
> Upgrade resolvconf to 1.63ubuntuNewWithYourChange
This wouldn't need any changes in 12.04, and the version would be 1.69NewWithMyChange in 14.04. So 12.04 users would continue to use as normal, but this fix would prevent network getting seemingly broken for no obvious reason upon upgrade to 14.04, as a one-time upgrade change of restoring the symlink that by default is there in both 12.04 and 14.04. But only 14.04 seems to rely on it existing, thus 12.04 users are unaware they'd hit this problem when upgrading.
> Actually it doesn't. In the absence of /etc/resolv.conf the resolver simply defaults to
> the configuration equivalent to "nameserver 127.0.0.1".
Weirdly, I've multiple 14.04 machines (including freshly installed) here that lose name resolving abilities after removing /etc/resolv.conf. Only Firefox continues to work until restart, but eg. ping www.google.com immediately reports unknown host. If I move the symlink back, resolving works.
> Install 12.04 thYourChange
> Do `rm /etc/resolv.conf`
> Upgrade resolvconf to 1.63ubuntuNewWi
This wouldn't need any changes in 12.04, and the version would be 1.69NewWithMyChange in 14.04. So 12.04 users would continue to use as normal, but this fix would prevent network getting seemingly broken for no obvious reason upon upgrade to 14.04, as a one-time upgrade change of restoring the symlink that by default is there in both 12.04 and 14.04. But only 14.04 seems to rely on it existing, thus 12.04 users are unaware they'd hit this problem when upgrading.