resolvconf definitely doesn't work under natty and oneiric

[jdreed]

I can't remember if this is relevant or not given that we still do caching nameservers, but resolvconf does not reliably work under Natty (that is, it does not pick up dns-* lines from /etc/network/interfaces.

[jdreed]

This is maybe not an issue? My -workstation machine did pick up 127.0.0.1. I think this is going to be an issue for private workstations not using dns-config, and they should be encouraged to use NM instead, maybe?

[jdreed]

OK, I think we'll see where things go. I don't have a good idea of how many private workstations use /etc/network/interfaces _and_ resolvconf and are NOT using debathena-dns-config.  LP:448095 hasn't moved in a while, so I'm not optimistic this will get fixed in Oneiric, and I don't have the cycles now to pretend to understand Upstart and how this all fits in.

[jdreed]

Actually, this is an issue in that cluster machines no longer have "search mit.edu" in resolv.conf. Do we care?

[kaduk]

Replying to jdreed:

Actually, this is an issue in that cluster machines no longer have "search mit.edu" in resolv.conf. Do we care?

I think we have a bunch of users that have been conditioned to expect it (or rather, to expect the functionality it gives). So we should care.

[jdreed]

Still broken in Oneiric. "Yay".  LP:366967 suggests that all the pieces are there for a fix, but the package may be lacking a maintainer in Ubuntu. We may want to punt resolvconf and just manage the file ourselves.

[amu]

If you're cool with packages from universe, you can see if openresolv works any better.

[andersk]

resolvconf is becoming part of the default installation in precise, and this should all be fixed in resolvconf 1.63ubuntu8.

[jdreed]

Indeed, this works in precise. I'm tempted to WONTFIX this, since the natty cluster machines are going away in 2 months.