On Sun, Apr 17, 2005 at 08:50:58PM +0200, Thomas Hood wrote: > Please forgive me if this is a duplicate mail but I don't see my mail > turning up in the BTS.
This is the only copy I've received. However, I automatically filter duplicates out. > > Thanks for the bug report. I have confirmed that the bug is present and > afflicts resolvconf both in combination with bind and in combination > with bind9. The bug bites when there are non-lo resolvconf records that > contain no nameserver entries. > > I have prepared a new version of resolvconf that should fix the bug. It > would be a help to me if you would test this version before I release > it. Get the package at: > > http://www.aglu.demon.nl/resolvconf > > Please let me know whether or not the bug is fixed and whether or not > you have any other problems with the new package. It (resolvconf_1.28~beta1_all.deb) seems to fix the problem. After initial install things were still bad (maybe the script should run postinst?), but I dialed in and then out. Afterwards, the file looked like options { forwarders { }; Which I think it correct. I don't see any complaints in my logs. Thanks for the quick response. I have a bunch of other questions/problems, mostly about the documentation, but I'll file those separately when I think I understand what's going on! Also FYI there seems to be a missing fetchmail script for resolvconf, but it is owned by the fetchmail package. I filed a bug against fetchmail (#304586: fetchmail: resolvconf script is missing) about it, but there's an outside chance it might be a resolvconf issue. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]