On my domain i've got a w2k8 standard domain controller and a w2k8R2 domain controller.
I recently added dns to the w2k8R2 server in an attempt to set up a failover/secondary dns but it is not working when the primary dns goes down. It's somewhat difficult to schedule shutting down the primary machine to test the failover so I post this question today hoping to form the best plan of attack using some answers provided.
I've configured and checked quite a few things. I'll list what I think is important to hopefully cross off a few of the possibilities.
The w2k8 standard server holds all the FSMO roles and was the only dns until recently. Replication between domain controllers is working fine. Zone Aging/Scavenging has been set to 3 days on both dns servers. Only had to delete 3 or 4 very old entries that would not scavenge. Zone Transfers are allowed to other nameservers on this domain. Forward/Reverse zones on both dns servers have same records. Replication working between zones because the "old entries" I removed from the secondary dns replicated back to the primary dns.
I've tested with NSLookup and I get mixed results. I have a few random outputs of "Can't find x.x.x.xxx - non existent domain" when the given ip is definitely in the fwd/reverse zones of both dns servers. NSlookup out to the web works fine it seems. Tracert seems to be able to resolve happily along its hops.
One thing that worries me is that when I run ipconfig /all I only get the ipaddress of my primary dns server assigned to me. But, I can use nslookup interactive mode and use the "server x.x.x.x" command and switch dns server contexts. So nslookup seems to be aware of the fact that I have multiple dns's out there but i'm not handing out the ip as a secondary dns.
Can anyone suggest other things for me to check?