Scenario: Main hub office with two dns servers (pre-Active Directory)
three other hub offices in geographically separate locations, each with two
dns servers setup as secondary DNS Servers.
Clients configured for their secondary (Secondary) DNS server as the primary
(preferred DNS Server) in their IP configuration. In this scenario will
dynamic updates work for client DNS? Or will they all need to be pointed to
the first dns server in the main hub office thats setup as the primary?
Also, can you have more than one primary DNS server in this scenario? We
are migrating to AD, but in stages, DNS first, then AD, then Exchange. So
whats the best way to setup internal DNS?
Thanks
Joe
Well, what happens is the client will ferret the MNAME record from the
secondary zone so it can send it to the server holding the writable zone.
Then zone transfer occurs and the secondary will be updated with the new
data.
>
> Scenario: Main hub office with two dns servers (pre-Active Directory)
> three other hub offices in geographically separate locations, each
> with two dns servers setup as secondary DNS Servers.
>
> Clients configured for their secondary (Secondary) DNS server as the
> primary (preferred DNS Server) in their IP configuration. In this
> scenario will dynamic updates work for client DNS? Or will they all
> need to be pointed to the first dns server in the main hub office
> thats setup as the primary?
No, the secondary is fine. But keep in mind, if the WAN link goes down,
nothing will get registered.
>
> Also, can you have more than one primary DNS server in this scenario?
NO. Following based on the RFCs. there can be only one (sounds like the
"Highlander" TV show).
> We are migrating to AD, but in stages, DNS first, then AD, then
> Exchange. So whats the best way to setup internal DNS?
Once you've gone to AD, and install DNS on the DCs, then you can use AD
Integrated zones and all DCs will automatcially have a copy. No need for
secondaries.
Deploying and Designing Active Directory [DNS Design, Migration, Cert Auth,
Branch Offices, Exchange, ADC, Import-Export, etc]:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/activedirectory/deploy/default.mspx
Active Directory Operations Guide:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/activedirectory/maintain/opsguide/part1/default.mspx
825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003 (including how-to configure a forwarder):
http://support.microsoft.com/default.aspx?scid=kb;en-us;825036
291382 - Frequently asked questions about Windows 2000 DNS and Windows
Server 2003 DNS
http://support.microsoft.com/default.aspx?scid=kb;en-us;291382
323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
(How to configure a forwarder):
Also: Recommendation - Point all machines only to the internal servers, and
configure a forwarder to your ISP's DNS. This way all machines query your
DNS and if it doesn;'t have the answer, it asks outside. If the forwarding
option is grayed out, delete the root zone, (it looks like a period),
refresh the console, and try again. If not sure how to configure this, this
article will guide you thru it:
http://support.microsoft.com/d/id?=323380
Common Mistakes When Upgrading a Windows 2000 Domain To a Windows 2003
Domain
http://support.microsoft.com/default.aspx?scid=kb;en-us;555040
>
> Thanks
> Joe
No prob!
--
Regards,
Ace
Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.
This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Infinite Diversities in Infinite Combinations.
=================================