I'd create smaller subnet records in AD (probably matching
the /25 VLANs) and assign those to the sites which house the domain controller
which you want them to use. You can keep the /21 subnet entry as a catch all as
well, just in case.
--------
Roger Seielstad
E-mail Geek
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kamlesh Parmar
Sent: Monday, September 05, 2005 3:30 AM
To: [email protected]
Subject: [ActiveDir] DNS resolution - prioritization
Dear All,
We have around 50 sites with 80 DCs, all in single domain.
Now issue is three sites, have very restrictive network configuration for
subnets. (all having 500+ machines)
i.e. their subnet specification in AD is 10.*/21
but at the network level they have divided this subnet into VLANs with mask
of /25, all inclusive in mask /21 defined for subnet at AD level.
Problem: when machine tries to find the nearest DC using domain DNS
name, DNS server doesn't give IP of nearest DC first.
as server falls into only into one of the /25 subnets. ( "subnet mask
request" in DNS server is enabled)
And as a result, machines go to other DCs for netlogon related
activities/scripts. (generating unnecessary WAN traffic, slow login)
I am working with Network team to initiate the feasibility of so many
VLANs, (long process)
and if its possible to merge some VLAN, then I will move the DC in that
subnet.
Any solution other than hard coding nearest DC in host file of all these
machines.
Regards,
Kamlesh
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Fortune and Love befriend the bold"
~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Fortune and Love befriend the bold"
~~~~~~~~~~~~~~~~~~~~~~~~~~~
