On Wednesday 22 March 2006 11:16, Jesse Keating <jkeating@xxxxxxxxxx> wrote: > On Wednesday 22 March 2006 03:51, Tomasz Kłoczko wrote: > > Last change breaks bind. After upgrade to this named is started > > with /etc/named.caching-nameserver.conf as default config. > > Anyone performs some minimal testing after this kind changes ? > > Did you have a custom /etc/named.conf prior to the upgrade? Did the upgrade > remove this file? Do you still have /etc/named.conf on your system and bind > is refusing to use that and uses the /etc/named.caching-nameserver.conf ? > This is simply not possible. Any existing named.conf is preserved, and if any /etc/named.conf exists, /etc/named.caching-nameserver.conf is never used. I've tested and retested this. Unfortunately, even the default unmodified named.conf from the old caching-nameserver package would be preserved also, owing to recent changes to caching nameserver to mark named.conf as "%config(noreplace)". Anyone wanting only the caching-nameserver functionality, without a customized nameserver, should remove any existing /etc/named.conf left over after upgrade to bind-config. Regards, Jason. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
