Rodc dns not updating
My best practice used to be just to use Open DNS and perhaps Google DNS but after checking out the DNS Benchmark tool, I found that a previously unknown provider called Ultra DNS actually had faster results for their nameservers and they provide similar security to Open DNS. My internal DNS server (as configured above) will try to resolve the name first through Ultra DNS; if that service is down, the second attempt will be through Open DNS; and my third attempt will be through a secondary Open DNS address.
The likelihood of one being down happens from time to time, but two being down is a rarity.
This tip applies to regular computers in your domain that are getting their DNS settings manually or more realistically, from a DHCP server like Windows Server or a small business router.
Most of the time, my company likes to offload DHCP to the router in offices so that if a Windows Server has to be taken offline for a short period of time, we are not affecting address handout.
For these common situations, we look to using Forwarders in the DNS configuration area to point our requests externally.
Public DNS like Google DNS or Open DNS have NO IDEA about your internal network and will not be able to route login requests, file share connections, etc.
The bigger issues we ran into was on the DNS front.
Due to some mismanagement of DNS in the past, and not following best practices, we had to clean up a few snags that were left behind by the old IT company.
We happen to use NIC teaming on Server 2012 at some customer sites, but it works well because we configured it properly so that the network only sees dual or quad connections as a single logical connection and address.
You can read up on Server 2012 NIC teaming from resources like this great Tech Net post.