On Wed, Jul 09, 2008 at 08:42:12AM -0700, Chris Miller wrote:
I just had a customer's bind server lose all of it's local DNS records. Yum updated the bind packages this morning at ~6am, and replaced the original /etc/named.conf file, saving the old as named.conf.rpmsave. This seems like the opposite of what it should have done (i.e. save the new file as named.conf.rpmnew).
If you have the caching-nameserver package, it's the expected behaviour:
/etc/named.conf is "owned" and labelled as "config file" for caching-nameserver.
The regular bind/bind-chroot don't provide named.conf. You should not install the caching-nameserver package if you are indeed providing DNS services with bind...
Tru