However, while my Reverse zone transfers fine, my Forward zones do not transfer at all.
I am unable to add records to the secondary and I cannot get the host records from my primary to transfer.
I've stumbled upon a strange behaviour with Windows machines, which seems to be fairly consistent between all Windows versions from Vista/2008 to 8.1/2012 R2; it doesn't happen instead when using Windows XP or Windows Server 2003.
The problem is this: when the network adapter is configured for DHCP and the DHCP server doesn't register DNS records on behalf of its clients (because it can't, or because it's not configured to do so), then A friend not on SF said: "That's normal, PTR is only updated by DHCP in Win2K ".
Both are set to allow zone transfers between the two.
in the TCP/IP settings of the network interface: As much as it may appear strange, this is the only solution to ensure Windows will register both the A and the PTR records for a DHCP network connection; otherwise, it will only register the A record. sends option 81 and its fully qualified domain name to the DHCP server and requests the DHCP server to register a pointer resource record (PTR RR) on its behalf.
The dynamic update client registers an address resource record (A RR). the DHCP server can be configured to instruct the client to allow the server to register both records with the DNS.
This feature alone can save an administrator a lot of valuable time.
As you can see by the Properties sheet shown in Figure A, you have a number of options to consider when configuring DHCP for dynamic updates.