Hi, I can confirm the original report, though I noticed it through a different vector... The dns-nameservers option in /etc/network/interfaces now seems to be a complete no-op, regardless of the order.
(and somehow in my fiddling to try and diagnose that, the dns-search option I had there appears to have become a permanent part of my resolv.conf and is no longer removed if I ifdown the (static) interface it is listed for) ... hmm, I see from the changelog that the 127.* thing is deliberate. I wonder if that is what we really want. In my case at least, I wanted the host to fall back to an alternate server if the local one was temporarily unavailable. That doesn't explain why dns-nameservers doesn't work any more though ... unless it is that bind on the same machine already adds the 127.* entry before it is run... The "law of least surprise" seems to be somewhat in tatters if this all really is a result of that change. But perhaps I'm missing part of the bigger picture. best, Ron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
