| Author |
Message |
Tom
Guest
|
 Posted:
Tue Nov 08, 2005 5:50 pm Post subject:
DNS Zones - Multiple zones or one? |
|
|
Hello. We're planning AD rollout next week and are having a tough time
deciding how to design DNS. We have three sites, each with their own
subnet. Our Nashville site has about 900 PCs, Omaha has 13 PCs and Philly
has about 25. In testing, we tried setting up multiple zones, one for each
site (nash.xyz.com, omaha.xyz.com, etc) but we were then unable to resolve
from a PC in one zone to one in another zone. How do we resolve across
zones? With only 13 and 25 in the other sites, is there even a need to
create separate zones for them? If having 938 PCs in one zone is okay, it
would be prefeable to have them all in one zone.
Thanks,
Tom |
|
| Back to top |
|
 |
Phil
Guest
|
| Posted:
Thu Nov 10, 2005 9:45 am Post subject:
RE: DNS Zones - Multiple zones or one? |
|
|
Try setting up a zone for each location and make sure that they are Active
Directory Integrated zones. Have the zone replicate to all of your DC's at
all of your sites. This way each DC at each site is holding a master record
for each of your zones.
We have over 10K dns records in one zone.
P
"Tom" wrote:
| Quote: | Hello. We're planning AD rollout next week and are having a tough time
deciding how to design DNS. We have three sites, each with their own
subnet. Our Nashville site has about 900 PCs, Omaha has 13 PCs and Philly
has about 25. In testing, we tried setting up multiple zones, one for each
site (nash.xyz.com, omaha.xyz.com, etc) but we were then unable to resolve
from a PC in one zone to one in another zone. How do we resolve across
zones? With only 13 and 25 in the other sites, is there even a need to
create separate zones for them? If having 938 PCs in one zone is okay, it
would be prefeable to have them all in one zone.
Thanks,
Tom
|
|
|
| Back to top |
|
|
Tom
Guest
|
| Posted:
Thu Nov 10, 2005 5:50 pm Post subject:
Re: DNS Zones - Multiple zones or one? |
|
|
Thanks P. I've decided to keep the network as one zone, AD integrated.
This is less complex, and there doesn't seem to be a need to set up a zone
for 25 PC and another for 13 PCs. The zone will have those PCs plus 800 in
the main office. Do you see this causing any issues or do you think
multiple zones would be better?
Thanks again,
tom
"Phil" <Phil@discussions.microsoft.com> wrote in message
news:2AF4F75B-CA65-45B5-AD46-FB35421D0DF5@microsoft.com...
| Quote: | Try setting up a zone for each location and make sure that they are Active
Directory Integrated zones. Have the zone replicate to all of your DC's at
all of your sites. This way each DC at each site is holding a master
record
for each of your zones.
We have over 10K dns records in one zone.
P
"Tom" wrote:
Hello. We're planning AD rollout next week and are having a tough time
deciding how to design DNS. We have three sites, each with their own
subnet. Our Nashville site has about 900 PCs, Omaha has 13 PCs and
Philly
has about 25. In testing, we tried setting up multiple zones, one for
each
site (nash.xyz.com, omaha.xyz.com, etc) but we were then unable to
resolve
from a PC in one zone to one in another zone. How do we resolve across
zones? With only 13 and 25 in the other sites, is there even a need to
create separate zones for them? If having 938 PCs in one zone is okay,
it
would be prefeable to have them all in one zone.
Thanks,
Tom
|
|
|
| Back to top |
|
|
Phil
Guest
|
| Posted:
Thu Nov 10, 2005 5:50 pm Post subject:
Re: DNS Zones - Multiple zones or one? |
|
|
I think you'll be fine either way, understand though that if you have all
clients in one zone they will all have a FQDN of "clientname".nash.xyz.com
even if they are located in Omaha. I might create seperate zones for
orginzation as well as allowing future expansion to be built-in. For
instance, if you decide your other sites grow as large as your nashville
sites you may want to create sperate Active Directory domains for them, with
these zones already inplace you will find migrating to that structure easier.
Hope that helps.
"Tom" wrote:
| Quote: | Thanks P. I've decided to keep the network as one zone, AD integrated.
This is less complex, and there doesn't seem to be a need to set up a zone
for 25 PC and another for 13 PCs. The zone will have those PCs plus 800 in
the main office. Do you see this causing any issues or do you think
multiple zones would be better?
Thanks again,
tom
"Phil" <Phil@discussions.microsoft.com> wrote in message
news:2AF4F75B-CA65-45B5-AD46-FB35421D0DF5@microsoft.com...
Try setting up a zone for each location and make sure that they are Active
Directory Integrated zones. Have the zone replicate to all of your DC's at
all of your sites. This way each DC at each site is holding a master
record
for each of your zones.
We have over 10K dns records in one zone.
P
"Tom" wrote:
Hello. We're planning AD rollout next week and are having a tough time
deciding how to design DNS. We have three sites, each with their own
subnet. Our Nashville site has about 900 PCs, Omaha has 13 PCs and
Philly
has about 25. In testing, we tried setting up multiple zones, one for
each
site (nash.xyz.com, omaha.xyz.com, etc) but we were then unable to
resolve
from a PC in one zone to one in another zone. How do we resolve across
zones? With only 13 and 25 in the other sites, is there even a need to
create separate zones for them? If having 938 PCs in one zone is okay,
it
would be prefeable to have them all in one zone.
Thanks,
Tom
|
|
|
| Back to top |
|
|
Tom
Guest
|
| Posted:
Thu Nov 10, 2005 9:50 pm Post subject:
Re: DNS Zones - Multiple zones or one? |
|
|
Thanks Phil. With the smaller sites, there are no plans for expansion. If
we do need to expand in 4 or 5 years, hopefully creating new zones then
won't be too difficult.
Thanks,
Tom
"Phil" <Phil@discussions.microsoft.com> wrote in message
news:6254C408-81F0-4D55-8CB9-CA79B7F2F195@microsoft.com...
| Quote: | I think you'll be fine either way, understand though that if you have all
clients in one zone they will all have a FQDN of "clientname".nash.xyz.com
even if they are located in Omaha. I might create seperate zones for
orginzation as well as allowing future expansion to be built-in. For
instance, if you decide your other sites grow as large as your nashville
sites you may want to create sperate Active Directory domains for them,
with
these zones already inplace you will find migrating to that structure
easier.
Hope that helps.
"Tom" wrote:
Thanks P. I've decided to keep the network as one zone, AD integrated.
This is less complex, and there doesn't seem to be a need to set up a
zone
for 25 PC and another for 13 PCs. The zone will have those PCs plus 800
in
the main office. Do you see this causing any issues or do you think
multiple zones would be better?
Thanks again,
tom
"Phil" <Phil@discussions.microsoft.com> wrote in message
news:2AF4F75B-CA65-45B5-AD46-FB35421D0DF5@microsoft.com...
Try setting up a zone for each location and make sure that they are
Active
Directory Integrated zones. Have the zone replicate to all of your DC's
at
all of your sites. This way each DC at each site is holding a master
record
for each of your zones.
We have over 10K dns records in one zone.
P
"Tom" wrote:
Hello. We're planning AD rollout next week and are having a tough
time
deciding how to design DNS. We have three sites, each with their own
subnet. Our Nashville site has about 900 PCs, Omaha has 13 PCs and
Philly
has about 25. In testing, we tried setting up multiple zones, one for
each
site (nash.xyz.com, omaha.xyz.com, etc) but we were then unable to
resolve
from a PC in one zone to one in another zone. How do we resolve
across
zones? With only 13 and 25 in the other sites, is there even a need
to
create separate zones for them? If having 938 PCs in one zone is
okay,
it
would be prefeable to have them all in one zone.
Thanks,
Tom
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in