Christoph Anton Mitterer put forth on 1/11/2010 5:31 PM:
> Using the "resolvconf" package, should solve your problems, the Debian
> postfix package ships rules for resolvconf in order to automatically
> update the chroot resolv.conf.
resolvconf has a long list of conflicts including ifupdown and bind8/9. I've
heard of some folks running bind locally on their (large) mail servers for dnsbl
lookups (yes, instead of rbldnsd) and other purposes. Would using resolvconf
break bind? Aptitude seems to suggest this. Does one need to be extra careful
if/when installing this package? What kind of collateral damage does this
pagkage cause, if any?
Conflicts: bind (< 1:8.3.4-1), bind9 (< 1:9.2.1-7), dhcp-client (=
3.0.1betaRC4-1), dhcp-client (< 2.0pl5-18), dhcp3-client (<
3.0+3.0.1rc11-5), dhcpcd (< 1:1.3.22pl4-7), divine, dnsmasq (<
1.13-2), ifupdown (< 0.6.4-4.1), laptop-net (< 2.21-1),
pcmcia-cs (< 3.2.5-1), pdnsd (< 1.1.10par-4), pppconfig (< 2.3.1),
pppoeconf (< 1.0), pump (< 0.8.15-1), runit (<
1.8.0-3), totd (< 1.4-4), udhcpc (< 0.9.8cvs20050124-3), webmin (<
1.150-2), webmin-wvdial (< 1.160-3), whereami (<
0.3.3), xisp
--
Stan
