Once upon a time, MJang <[EMAIL PROTECTED]> said: > Hmm, just saw this in the Slashdot RSS feed - suggesting that the latest > Red Hat bind update overrides current named.conf files with the default > associated with caching nameservers > http://it.slashdot.org/article.pl?sid=08/07/18/1210257&from=rss
That's a typical /. story. The real problem is apparently that the guy installed the RHEL 4 caching-nameserver package, added zones to the RPM-installed named.conf, and then was suprised when updating the caching-nameserver package renamed his modified named.conf to named.conf.rpmsave. Now, the named.conf from caching-nameserver doesn't clearly identify that it should not be edited (RHEL 5 handles this much better by not using named.conf for the caching-nameserver), but since part of the update needed to remove any references to query-source setting a port (to fix the BIND security issue), the only way to do that is to replace named.conf. -- Chris Adams <[EMAIL PROTECTED]> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
