Yes !
Not only for remote site DCs but also for regional hub DCs too...
--
Kamlesh
On 12/31/05, Al Mulnick [EMAIL PROTECTED] wrote:
If I understand you correctly, you can already control between local site and regional/central site authentication hierarchy through publication of records (as
Thanks Jorge for so nicely putting it all together...
This is what I was thinking as the simplest possible optimized configuration.
So, thought lets put it across masters to knowall possibilities...
--
Kamlesh
On 1/1/06, Almeida Pinto, Jorge de [EMAIL PROTECTED] wrote:
what you could do is:*
: Sat 2005-12-31 13:57
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] DNS SRV records
1)
AFAIK, Site is a active directory specific concept, and AD is Directory (LDAP),
Authentication server (Kerberos) etc. These services are published by AD in DNS
thru SRV records in _sites._msdcs
1)
AFAIK, Site is a active directory specific concept, and AD is Directory (LDAP), Authentication server (Kerberos) etc. Theseservices are published by AD in DNS thru SRV records in _sites._msdcs for each site and it covers them all... (LDAP,DC,GC,Kerberos,Kpassword)
so I was curious what
If I understand you correctly, you can already control between local site and regional/central site authentication hierarchy through publication of records (as inbranch office scenario)but you want to further control which DC does authentication by controlling, in the event of failure in the
you generate or some logic that perl can follow.
You could set up just about anything you would like to set
up.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kamlesh
ParmarSent: Saturday, December 31, 2005 7:57 AMTo:
ActiveDir@mail.activedir.orgSubject: Re: [ActiveDir] DNS
_sites.dc._msdcs.DNSDomainName is for locating a DC (hence the _msdcs) that
hosts a certain service in a certain site
_sites.DnsDomainName is for locating a SERVER (does not need to be a DC) that
hosts a certain service in a certain site
for more info on service resource records see:
