debathena-dns-config breaks networking when registration required

[geofft]

As far as I can tell, debathena-dns-config sets up bind to start resolving from the global root servers, not whatever DNS servers are provided via DHCP. This makes you sad when you're on a network that depends on redirecting web requests via DNS to a registration page. (For instance, the Middle East's network, although free, requires you to click okay on a web page on every session.)

I haven't tested this with a MITnet-unregistered machine, but it seems like it would be a problem there, too, e.g., if you just installed debathena-workstation on a new machine from PXE.

There appears to be code in /etc/resolvconf/update.d/bind to configure bind's forwarders to be what the other resolvconf sources say your DNS servers should be, which would be a perfect fix. Is that not getting triggered for some reason?

[jdreed]

#1131 makes this irrelevant, as dnsmasq does in fact go check what resolvconf thinks your upstream servers should be.

Also, don't do this.