Re: GUID DNS Name could not be resolved
From: Gary (anonymous_at_discussions.microsoft.com)
Date: 09/22/04
- Next message: wasonce: "Re: Script?"
- Previous message: Chad: "Re: MMC Help: Active Directory and multiple Domain Controllers"
- In reply to: Herb Martin: "Re: GUID DNS Name could not be resolved"
- Next in thread: Herb Martin: "Re: GUID DNS Name could not be resolved"
- Reply: Herb Martin: "Re: GUID DNS Name could not be resolved"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 21 Sep 2004 18:36:08 -0700
Herb,
Thanks for the response. I have checked all of the
client properties and they seem to be fine. I also have
checked the underscore sub-domains and they exist as
well. The wierd thing is that if I scroll down through
the options of the underscore entries, each reference to
the server is just the name and a dot (SERVER_NAME.) and
it has no namespace suffix (such as
SERVER_NAME.domain.com). Also, DNS keeps generating a
SERVER_NAME. entry as one of the name servers and it has
no IP associated with it. Meaning there is a SERVER_NAME
host entry (with no Dot), but there is no SERVER_NAME.
entry. IF I delete the Name Server entry, it gets
automatically added back in when I restart DNS services.
I think this is the root of the problem, but I can't
figure out where the SERVER_NAME. entry is being generated
from.
Any thoughts?
>-----Original Message-----
>DNS
> 1) Dynamic for the zone supporting AD
> 2) All internal DNS client NIC\IP properties must
specify SOLELY
> that internal, dynamic DNS server (set.)
> 3) DCs and even DNS servers are DNS clients too --
see #2
>
>Restart NetLogon on any DC if you change any of the above
that
>affects a DC.
>
>Also double check that you have the _Underscore sub-
domains
>in your DNS server(s) and that all DNS servers are
replicated
>fully.
>
>(e.g., _msdcs, _sites, etc.)
>
>--
>Herb Martin
>
>
>"Gary" <anonymous@discussions.microsoft.com> wrote in
message
>news:0ee001c4a013$e33a0630$a601280a@phx.gbl...
>> I have already posted this, but received no response,
so I
>> am trying to reword in hopes that someone may have an
>> answer.
>>
>> My Win2K Domain Controller is having DNS issues. I
>> believe the root of the problem is that its GUID DNS
name
>> could not be resolved. I have listed the error message
>> from DCDIAG below.
>>
>> Does anyone know have to rectify this?
>>
>> Testing server: Default-Site\SERVER_NAME
>> Starting test: Connectivity
>> SERVER_NAME's server GUID DNS name could not be
>> resolved to an IP address. Check the DNS server, DHCP,
>> server name, etc Although the Guid DNS name
>> (7942fd1f-bf54-4105-a1d5-45f6824bfbab._msdcs.domain.com)
>> couldn't be resolved, the server name (SERVER_NAME)
>> resolved to the IP address (xx.xx.xx.xx) and was
>> pingable. Check that the IP address
>> is registered correctly with the DNS server.
>> ......................... SERVER_NAME failed test
>>
>
>
>.
>
- Next message: wasonce: "Re: Script?"
- Previous message: Chad: "Re: MMC Help: Active Directory and multiple Domain Controllers"
- In reply to: Herb Martin: "Re: GUID DNS Name could not be resolved"
- Next in thread: Herb Martin: "Re: GUID DNS Name could not be resolved"
- Reply: Herb Martin: "Re: GUID DNS Name could not be resolved"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|