named-bootconf failure
Greetings,
named-bootconf is no longer working on one of my DNS systems. I have two
identical systems, both doing DNS with the same software loaded.
Last week, the named-bootconf stopped writing the named.conf file on the
primary server. The file is empty except for the header, "this file
generated by...." When run, I noticed that it was not reading the
boot.options and boot.zones files. I compared the two systems, and I
cannot see a difference between the primary and the secondary. Same perl,
same bash, same sh. I even exported the boot.options file to the secondary
system and ran named-bootconf and it created the named.conf file.
One thing I have noticed is two files have been altered. Both gzip and
gunzip were at 0 bytes. Not sure if this has anything to do with it. And
input on this matter would be appreciated.
Anthony Landreneau
Infinity Data Systems
Network Engineer
Reply to: