Home All Groups Group Topic Archive Search About

joining domain by short name...

Author
4 Mar 2006 11:29 PM
Aaron Anderson
joining domain by short name...


I'm working on migrating my domain controller to a 2003 box. (new hardware)
I have gotten everything to function properly except for a small quirk that
is DNS related when joining new clients to the domain.

My domain name is 'THERMEX'

When I enter 'thermex' for the domain to join, it retruns the following
error:


-----------------------------------------------------------
The following error occurred when DNS was queried for the service location
(SRV) resource record used to locate a domain controller for domain
thermex.thermex-thermatron.com:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for
_ldap._tcp.dc._msdcs.thermex.thermex-thermatron.com

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its child
zone:

thermex.thermex-thermatron.com
thermex-thermatron.com
com
.. (the root zone)

For information about correcting this problem, click Help.
-----------------------------------------------------------



When I enter 'thermex.thermex-thermatron.com' as the domain to join, the
credentials box pops right up and everything works fine.



Thoughts? Clues? Anything?

Author
5 Mar 2006 1:04 AM
Joe Richards [MVP]
You probably need to start with a network trace to verify what the DNS query is
that is being sent and the response to it.

--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

         http://www.joeware.net/win/ad3e.htm



Aaron Anderson wrote:
Show quoteHide quote
> joining domain by short name...
>
>
> I'm working on migrating my domain controller to a 2003 box. (new hardware)
> I have gotten everything to function properly except for a small quirk that
> is DNS related when joining new clients to the domain.
>
> My domain name is 'THERMEX'
>
> When I enter 'thermex' for the domain to join, it retruns the following
> error:
>
>
> -----------------------------------------------------------
> The following error occurred when DNS was queried for the service location
> (SRV) resource record used to locate a domain controller for domain
> thermex.thermex-thermatron.com:
>
> The error was: "DNS name does not exist."
> (error code 0x0000232B RCODE_NAME_ERROR)
>
> The query was for the SRV record for
> _ldap._tcp.dc._msdcs.thermex.thermex-thermatron.com
>
> Common causes of this error include the following:
>
> - The DNS SRV record is not registered in DNS.
>
> - One or more of the following zones do not include delegation to its child
> zone:
>
> thermex.thermex-thermatron.com
> thermex-thermatron.com
> com
> . (the root zone)
>
> For information about correcting this problem, click Help.
> -----------------------------------------------------------
>
>
>
> When I enter 'thermex.thermex-thermatron.com' as the domain to join, the
> credentials box pops right up and everything works fine.
>
>
>
> Thoughts? Clues? Anything?
>
>
Author
5 Mar 2006 2:03 AM
Aaron Anderson
What's your reccomendation for that sir? Something like Ethereal should do
the trick, no?


Show quoteHide quote
"Joe Richards [MVP]" <humorexpr***@hotmail.com> wrote in message
news:O7V8wC$PGHA.3872@TK2MSFTNGP15.phx.gbl...
> You probably need to start with a network trace to verify what the DNS
> query is that is being sent and the response to it.
>
> --
> Joe Richards Microsoft MVP Windows Server Directory Services
> Author of O'Reilly Active Directory Third Edition
> www.joeware.net
>
>
> ---O'Reilly Active Directory Third Edition now available---
>
>         http://www.joeware.net/win/ad3e.htm
>
>
>
> Aaron Anderson wrote:
>> joining domain by short name...
>>
>>
>> I'm working on migrating my domain controller to a 2003 box. (new
>> hardware) I have gotten everything to function properly except for a
>> small quirk that is DNS related when joining new clients to the domain.
>>
>> My domain name is 'THERMEX'
>>
>> When I enter 'thermex' for the domain to join, it retruns the following
>> error:
>>
>>
>> -----------------------------------------------------------
>> The following error occurred when DNS was queried for the service
>> location (SRV) resource record used to locate a domain controller for
>> domain thermex.thermex-thermatron.com:
>>
>> The error was: "DNS name does not exist."
>> (error code 0x0000232B RCODE_NAME_ERROR)
>>
>> The query was for the SRV record for
>> _ldap._tcp.dc._msdcs.thermex.thermex-thermatron.com
>>
>> Common causes of this error include the following:
>>
>> - The DNS SRV record is not registered in DNS.
>>
>> - One or more of the following zones do not include delegation to its
>> child zone:
>>
>> thermex.thermex-thermatron.com
>> thermex-thermatron.com
>> com
>> . (the root zone)
>>
>> For information about correcting this problem, click Help.
>> -----------------------------------------------------------
>>
>>
>>
>> When I enter 'thermex.thermex-thermatron.com' as the domain to join, the
>> credentials box pops right up and everything works fine.
>>
>>
>>
>> Thoughts? Clues? Anything?
Author
5 Mar 2006 11:05 AM
Paul Williams [MVP]
Yes, Ethereal or the version of NETMON that ships with SMS.

However, just before you do that, ensure that you are pointing to your DC
for DNS and that your DC is pointing to itself for DNS.  Then restart
NETLOGON on the DC and verify that DNS is OK with the following command:

nslookup -type=srv _ldap._tcp.dc._msdcs.thermex.thermex-thermatron.com


If that returns a positive result, ensure your clients are pointing to that
DC for DNS and try again.

You can also use the following command to test name-resolution:

nltest /dsgetdc:thermex.thermex-thermatron.com
nltest /dsgetdc:thermex
nltest /dsgetsite

Note.  NLTEST is a support tool:
http://www.msresource.net/content/view/53/46/

If that doesn't help, or there are problems, run the sniff like Joe said and
see what's going where.  You should also check the event logs.  If there are
relevant errors and/ or warnings, look them up at www.eventid.net

--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net