Bug#318464: [Resolvconf-devel] Bug#318464: resolvconf: Cascaded dnscache incompatibility

2007-02-06 Thread Tobias Reckhard
Hi Daniel First of all, thanks a lot for the quick response. Daniel Kahn Gillmor wrote the following on 05.02.2007 20:32: > At 2007-02-05 09:12, [EMAIL PROTECTED] said: > >>> The advantage of this setup over one with only one dnscache is that >>> you can make changes to the dnscache redirection

Bug#318464: [Resolvconf-devel] Bug#318464: resolvconf: Cascaded dnscache incompatibility

2007-02-05 Thread Daniel Kahn Gillmor
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 2007-02-05 09:12, [EMAIL PROTECTED] said: > The advantage of this setup over one with only one dnscache is that > you can make changes to the dnscache redirection configuration, > which requires a restart of dnscache to take effect, without losing

Bug#318464: [Resolvconf-devel] Bug#318464: resolvconf: Cascaded dnscache incompatibility

2007-02-05 Thread Thomas Hood
Tobias Reckhard wrote: > The dnscache script in the resolvconf package breaks this setup by > overwriting the root/servers/@ file of the forward-only-dnscache with > its own address, leading to a forwarding loop. This effectively breaks > all DNS reolution on the system. > > If resolvconf is to co