DNS in Two Locations

  • Thread starter Thread starter scott
  • Start date Start date
S

scott

I have my primary DNS in new york. I need to put a DNS
server in my denver location. Should I make the denver
DNS a secondary zone or create a new primary zone?

Thanks!
 
In
scott said:
I have my primary DNS in new york. I need to put a DNS
server in my denver location. Should I make the denver
DNS a secondary zone or create a new primary zone?

Thanks!
Click to expand...

Assuming you want a copy of the same zone at Denver...

If you install DNS on a DC in Denver, and it's in the same domain as the
server in NY, (on W2k), then you can make both zones AD Integrated. No need
for zone transfers, since the zone is stored in AD and gets replicated with
AD's replication schedule.

If you install DNS on a non-DC or on a DC that is in a different domain (on
W2k), then yes, make a secondary zone.

If using W2k3, and DNS will be on a DC in Denver (no matter what domain),
then you can make it AD Integrated as well, but make sure you opt to
replicate the zone to the other domain.

Make sense?
:-)

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
scott said:
I have my primary DNS in new york. I need to put a DNS
server in my denver location. Should I make the denver
DNS a secondary zone or create a new primary zone?
Click to expand...


You must NOT make a new primary for the same zone
unless you want DNS replication to fail.

Either make the new one a "secondary" or if it's a DC,
you can use AD Integrated on both.

AD Integrated DNS allows a "set of DCs" to act like
a single Primary but if AD replication works you can
make changes at any of the servers/locations.
 
Ok those posts were helpful - a couple things I see need
to reply to:

1) The denver server is W2K3.
2) The domain is denver.xxxx.com, the domain in New York
is xxxx.com. - so, if I create a secondary zone, Denver
computers will use the local DNS server for requests,
correct? (which is what I want)


Thanks again!
 
Ok those posts were helpful - a couple things I see need
to reply to:

1) The denver server is W2K3.
2) The domain is denver.xxxx.com, the domain in New York
is xxxx.com. - so, if I create a secondary zone, Denver
computers will use the local DNS server for requests,
correct? (which is what I want)
Click to expand...

Separate the CONCEPTS of "clients resolving" addresses from
"servers holding zones".

There is NO necessary relationship between the two.

We must be careful how we say this since my standard advice
is to insist that "Internal machines must be configured to use the
internal DNS servers." This advice needs no amplification if the
company only has one zone, but must be tempered a bit if the
company has a tree:

"Internal clients must be configured to use DNS server(s) that
resolve ALL of the internal zones and NOT configured to use
any external DNS servers (ISP etc.) that cannot do this."
 
In
Ok those posts were helpful - a couple things I see need
to reply to:

1) The denver server is W2K3.
2) The domain is denver.xxxx.com, the domain in New York
is xxxx.com. - so, if I create a secondary zone, Denver
computers will use the local DNS server for requests,
correct? (which is what I want)


Thanks again!
Click to expand...

If you create the secondary zone on the DNS server in Denver, yes, your
clients will use it provided that is the ONLY DNS server you specify for
their IP properties, whether thru static configuration or thru DHCP Option
006.

As Herb implied, make sure you DO NOT use any other DNS addresses for your
clients or DCs other than the Denver server as the 1st entry, and the NY
server as the second entry.

Configure a forwarder for efficient Internet resolution. If not sure how,
see this article:
http://support.microsoft.com/?id=300202

I hope that was easy enough!


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Back
Top