Hi Michael, quite simple: as the Cobalt-Tools don't work with our subnet-reverse-DNS i set up a little script that runs on our secondary DNS. It checks whether the correct settings for secondary DNS are in /etc/named.conf. If not it fixes this file and restarts the bind. This is necessary because everytime we do changes in the cobalt-surface the correct reverse-settings get smashed. So my little program does NOT touch the /etc/named/records-file which is the main DNS-Database of the RaQ. And in worst case condition the reverse lookup on our secondary will work correctly after 1 hour max.
So grep, awk or sed might be your friends on this topic, it's really simple. Just find out how your ISP wnats you to name up your reverse-zone. I think because of it's simplicity this solution is better better than modifying the Cobalt-Scripts. And those modifications may get lost after updating the UI. And if you don't need it anymore, just kill the cron-job. Yours Jan* Am Dienstag, 12. August 2003 21:13 schrieben Sie: > >Jan* wrote: i bulit a little hack that corrects the settings on our > > secondary which is > > >a RaQ4r. > > Sorry if I missed it somewhere but what is this "hack". I would like to > get this working as well. > > -------------------------------------------- > Michael Aronoff - CIIC, Inc. > > _______________________________________________ > cobalt-developers mailing list > [EMAIL PROTECTED] > http://list.cobalt.com/mailman/listinfo/cobalt-developers _______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
