We currently have with BIND DNS servers that are the authorative for our main\nzone tom.com. The bind servers hand off the AD zones _msdcs.tom.com\n_tcp.tom.com etc. Everything functions fine, our upgrade went without\ntrouble.\nThis setup is fine for our corporate users since the BIND servers are\nlocated in house. However we have about 30 branches that have clients who use\nthe main DNS servers for resolution. That works just fine if the WAN links\nstay up. They are pretty stable, but there is always that chance. This came\nup during planning, but was nixed because the reliability was good.\nI know that if for some resaon these links do fail clients will not be able\nto logon...especially if when we go native. A thought I had was to setup DNS\non each branch server.....create a secondary zone called tom.com, pull all of\nthe info to windows from BIND and point users to their local server for DNS\nresolution.\nIf we decided to go full Windows DNS we could then change the zone\nproperties to Primary AD integrated.\nAny thoughts?