Slave (secondary) nameserver files

[Gerald Waugh]

Ok, I know I have had my problems, using Cobalt server appliances, with reverse
look-up. I now will *always* remember that I have to edit named.conf every time
I use the GUI to modify DNS.(thank you Mathias) This anomaly messed up my
reverse a couple of times.
And, that the GUI does not put $TTL in the zone files. (thank you Mark) I am
looking for the script that does these dastardly deeds so I can fix it.

There are a couple of other issues that I question about the Cobalt DNS GUI,
particularly for the Slave Server.

(1) There is no "named.boot" on the Slave.
(2) There is no 28-32.178.175.216.in-addr.arpa file.
    I think there should be, am I correct?

Maybe the Slave "fsn2.frontstreetnetworks.com" should be a Master for it's own
domain (IP). I only have it serve as a secondary for all domains, which are
served by the Master "fsn1.frontstreetnetworks.net". fsn2 appears to be
operating OK, answers NOTIFY and keeps the sec. zone files updated. But I am
almost positive that it must have an 28-32.178.175.216.in-addr.arpa file, and a
named.boot file (to load the in-addr.arpa file), else how would it function if
the master were down.

I thought that maybe I should enter master records for
"fsn2.frontstreetnetworks.com", the main site, in the slave instead of having
these records in the master "fsn1.frontstreetnetworks.net" . Then setup the
master "fsn1.frontstreetnetworks.net" as a slave for
"fsn2.frontstreetnetworks.com".

Thank you for considering my questions.
Gerald Waugh