My reverse zones are setup as Conditional Forwarder so that requests can be forwarded to my router's DNS service to resolve DHCP clients (as DHCP is handled by my router). I also intend to add records into the reverse zones directly for static hosts.
Thus, it is my expectation that queries to these reverse zones will first be handled locally if a record exists, or forwarded to the router otherwise. This seems to work just fine.
However, the Auto PTR feature throws "Error! Reverse zone '2.16.172.in-addr.arpa' is not a primary zone." when I have the Add reverse (PTR) record option checked. But I can add the PTR record in the zone manually.
So it seems that this check isn't actually necessary, and Auto PTR should automatically create records in non-primary zones.
My reverse zones are setup as Conditional Forwarder so that requests can be forwarded to my router's DNS service to resolve DHCP clients (as DHCP is handled by my router). I also intend to add records into the reverse zones directly for static hosts.
Thus, it is my expectation that queries to these reverse zones will first be handled locally if a record exists, or forwarded to the router otherwise. This seems to work just fine.
However, the Auto PTR feature throws "Error! Reverse zone '2.16.172.in-addr.arpa' is not a primary zone." when I have the Add reverse (PTR) record option checked. But I can add the PTR record in the zone manually.
So it seems that this check isn't actually necessary, and Auto PTR should automatically create records in non-primary zones.