Custom Query (1145 matches)


Show under each result:

Results (307 - 309 of 1145)

Ticket Resolution Summary Owner Reporter
#1535 fixed debathena-dns-config breaks dnsmasq with DHCP jdreed

Reported by jdreed, 10 years ago.


Not that this was ever supposed to work, but apparently using "lo.*" resolvconf profiles without a nameserver line is Bad(tm). Also, this is dumb, because a cluster machine without in the search domain is defined to be broken in the modern install environemnt. We should kill the initscript.

#358 wontfix debathena-dns-config breaks networking when registration required geofft

Reported by geofft, 15 years ago.


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?

#1166 wontfix debathena-dns-config doesn't configure resolv.conf to use jdreed jdreed

Reported by jdreed, 12 years ago.


Installed cluster machines end up with one of the "real" DNS servers in resolv.conf. And now that resolvconf actually works, it probably should.

Note: See TracQuery for help on using queries.