americanintel
08-19-2006, 12:19 PM
I don't use dns on the server and guess I could just kill it all together but when I was logged into DA the other day I noticed a large amount of warning messages stating that named has not been running.
I gave it a 'service named start' and get a list of problems with certain zone files. One partial example being (domain.com is my use):
zone domain.com/IN: loading master file /var/named/domain.com.db: file not found
_default/domain.com/IN: file not found
Now.. you have symlinks to /var/named/chroot/var/named and most of the domains have the files in the chroot directory but several of my newest domains are not getting these files created in the chrooted dir so you will see the db file in /var/named but not in /var/named/chroot/var/named. My older domains have the files in the correct chrooted /var/named dir but named chokes when looking for the new files.
Seems DA isn't creating the files in the chrooted dir.
domain.com.db -> /var/named/chroot/var/named/domain.com.db
I searched but didn't see any reference to this. Anyone have any insight?
I gave it a 'service named start' and get a list of problems with certain zone files. One partial example being (domain.com is my use):
zone domain.com/IN: loading master file /var/named/domain.com.db: file not found
_default/domain.com/IN: file not found
Now.. you have symlinks to /var/named/chroot/var/named and most of the domains have the files in the chroot directory but several of my newest domains are not getting these files created in the chrooted dir so you will see the db file in /var/named but not in /var/named/chroot/var/named. My older domains have the files in the correct chrooted /var/named dir but named chokes when looking for the new files.
Seems DA isn't creating the files in the chrooted dir.
domain.com.db -> /var/named/chroot/var/named/domain.com.db
I searched but didn't see any reference to this. Anyone have any insight?