BIND DNS with Windows DNS

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

Relevant Pages

  • Re: ad and dns setup
    ... MCSE, MVP Directory Services ... _msdcs, forward zone, reverse lookup zone. ... To fully rebuild DNS: ... changes immediately to all servers, this helps to speedup the process. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication issues
    ... I wanted to say Zone Transfers not Zone Forwarding. ... on 2 servers out of 4 DNS servers. ... DNS and 2003 DNS and how to set up Conditional Forwarding. ...
    (microsoft.public.windows.server.active_directory)
  • Re: ad and dns setup
    ... "Jorge Silva" wrote: ... domain It gave me 2 errors, no dns servers have dns records for this dc ... error no logon servers.. ... Make sure that the _msdcs zone exists and the scope is set ...
    (microsoft.public.windows.server.active_directory)
  • Re: Global catalog server died before completing replication to new GC server
    ... What about the DNS zones,are all machines listed there? ... Install DNS role and create a forward lookup zone for your complete ... Then make sure all servers are listed in the zones, ... cause Group Policy problems. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Very Critical issue
    ... the clients are configured to go to local Domain Controller for DNS query. ... created secondary zone for b.com in the root server of a.com and vise versa. ... As we are migrating all the users first, the file and other servers are ... "Jorge Silva" wrote: ...
    (microsoft.public.windows.server.active_directory)