In news:%23tO%(E-Mail Removed),
Blake <(E-Mail Removed)> typed:
> I have a machine, bobo.
>
> 1) it is a member server of xyz.org (Active Directory Domain) - so
> there is a computer account BOBO in the xyz domain
> 2) it's primary DNS suffix is set to abc.def.org (for reasons that are
> beyond my control)
> 3) I can log onto the xyz.org domain via this box, but I am getting
> Kerberos errors (I think it is failing over to NTLM)
>
> I have found some articles about this type of problem, but no real
> solutions. I need AD Kerberos to recogize that bobo.abc.def.org is
> the same machine as bobo.xyz.org. Can't I configure more than one
> 'Kerberos name'?
> Thoughts?
>
> Blake
The Primary DNS Suffix is used by the DNS registration process, as well as
to identify itself, esecially if is a domain controller. Since this is a
member server, this specific type of suffix is used to register it's
information into DNS. It will look for a zone name identical to the Primary
DNS Suffix. If it doesn't exist, it doesn't register. Now the Search Suffix
is used for the DNS resolver devolution process. Kerberos uses the SPN
(Service Principal Name) to ID the machine. The SPN is the FQDN of the
machine as identified in it's properties and DNS. If the registration is not
in DNS or the machine's Primary DNS Suffix is incorrect, we've got a
problem, and no, it's not that easy, or at least I don't even believe it is
even possible to alter the SPN of a machine. It's part of security.
In short, for a machine to be part of an AD domain called xyz.org, the
Primary DNS Suffix MUST match the domain name it's a member of.
--
Regards,
Ace
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 MVP - Directory Services
Microsoft Certified Trainer
For urgent issues, you may want to contact Microsoft PSS directly. Please
check
http://support.microsoft.com for regional support phone numbers.
Infinite Diversities in Infinite Combinations