On Wednesday 22 March 2006 09:34, Tomasz Kłoczko wrote: > > Did you have a custom /etc/named.conf prior to the upgrade? > > Yes. > > > Did the upgrade remove this file? > > No. It will be biggest bug than currently existing. > > > 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 ? > > > > > > # ls /var/named/chroot/etc/ -1; ps aux | grep named > > localtime > named.caching-nameserver.conf. > named.conf > named.conf~ > named.conf.old > named.conf~.org > named.conf.rpmnew > named.custom > named.rfc1912.zones > rndc.conf > rndc.key > rndc.key.rpmnew > named 1514 0.2 0.2 72464 12152 ? Ssl 12:11 > 0:56 /usr/sbin/named -u named -n 2 -t /var/named/chroot > kloczek 27335 0.0 0.0 58076 800 pts/13 S+ 18:28 0:00 less > named.init > > named.caching-nameserver.conf is not used only because now it dos not > exist (just renamed as you see). Wait, you're talking about the files in the chroot. Jason, did you test this? Tomasz, before (or if) you renamed the named.caching-nameserver.conf, did named prefer this file over your modified named.conf ? -- Jesse Keating RHCE (geek.j2solutions.net) Fedora Legacy Team (www.fedoralegacy.org) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub)
Attachment:
pgpZPBpqHAEvV.pgp
Description: PGP signature
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
