[ClassicMac]

I decided to look in to this a little more today. I figured that maybe if I created a new zone it would fix everything and my other zones would show up. Bad idea… It did fix my problem and the new zone showed up but not only did it remove all of my zones from named.conf but it also deleted the files for the zones. Luckily I had a backup of them and restored them.

After shuffling things around a bit I fould that it was my reverse lookup zone that was causing the problem. I had just copied it over from another BIND installation and things were working fine before I updated to 10.4+ (I forget exactly which version broke it). After moving the reverse zone in to another folder everything looked fine in server admin. I then began comparing the problem file with the good file that Server Admin created when I created the test zone. I noticed the entries differed a bit.

*** non working ***
1 IN PTR router.company.com.

*** working ***
1.1.168.192.in-addr.arpa. IN PRT router.company.com.

It looked like Server Admin needed to see the full domain name ending in in-addr.arpa. for it to interpret the zone properly. If anyone else is experiencing the same problem check your zone file in a text editor and see if this fix will work for you too. It should be located in /var/named.

Another side effect is that I had the zone named 1.168.192.in-addr.arpa.zone. After Server Admin recognized the file (after editing the entries) it renamed the file and edited my named.conf file to db.192.168.1. I doubt that will really affect anyone besides needing to be aware of the new filename but I thought I would mention it.

Good luck to anyone having the same problem as me.

[ClassicMac]

I am having the same problem. It may be a problem with the newer versions of Server Admin. When using version 10.4v156 the zones show up fine. I am interesting in getting zones to show up in the latest version though. If anyone has any ideas i’m all ears.

[Author]

Posts