Secondary Reverse Transfer

[joelande]

I notice that the reverse records for a zone do not transfer automatically, and attempting to add the “0.201.10.in-addr.arpa” zone to the secondary server’s “secondary zones” tab will not save the zone.

Things I have tried:
Looking at /var/named on the primary server I noticed that the reverse records that the GUI automatically creates are saved in files named “db.0.201.10”, so I tried adding the “db.0.201.10” zone to the secondary server’s secondary zones tab. That zone the GUI saved correctly, so maybe I am on the correct track here, but it did not transfer any of the zone files.
The log says non-authoritive answer from master.

I wonder if I have to create the reverse zones on the primary server manually using the GUI so that they are listed on the primary server’s zones tab?

Anyone have any luck transferring reverse DNS records to a secondary server on Tiger?

Notes:
both primary and secondary DNS servers are Tiger
both names and addresses are resolving correctly using the primary DNS server
names are resolving correctly using the secondary DNS server
addresses are not resolving using the secondary DNS server

[joelande]

Can I copy over the reverse zones from my primary server?

They titles like: db.10.201.1.0

[Author]

Posts