Re: GUID DNS Name could not be resolved
From: Gary (anonymous_at_discussions.microsoft.com)
Date: 09/22/04
- Next message: Gary: "No Host Name listed in Netdiag"
- Previous message: Richard G. Harper: "Re: Windows cannot obtain the domain controller name for your computer network. Return value (59)."
- 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: Wed, 22 Sep 2004 04:02:33 -0700
1) I am not familiar with the term two-tag, but I am
assuming you mean something like "mycompany.com", if so
the answer is yes. It was all functioning prior to me
adding a second card to the server. I was trying to add a
private network for administrative purposes. The Domain
Name is properly registered and functioning in DNS, except
for that server. entry. I have since taken the extra card
out and I am just trying to get things stabalized and back
to normal.
2)Yes, the server name and domain name are all correctly
listed in the System's Control Panel. On DC you don't
even get the option to modify those. They are
automatically generated there with the domain name when
you promote it to a DC.
That is the thing, I can't figure out where it is getting
the server. entry from? Of all the utilities that I have
run, nothing really states any problem except the GUID
error below from the DCDIAG utility. The other stange
thing is that when I run NETDIAG it doesn't list anything
for the DC Host name? All of the tests pass, but I have
to think no Host name is a problem.
I have been wrestling with this for a few days. Do you
know of any utility that will reset the GUID settings in
the error below. Or any other brute force method that will
get me up and runnig?
>-----Original Message-----
>Do you have:
>
> 1) At least a TWO-TAG domain name?
>
> 2) Each server, especially DC & DNS server, completely
> named (with domain name) in each's System Control
Panel
>
>[If not, fix #2 and ask here or search Google for the fix
>to #1 -- both are very bad.]
>
>Server_name by itself would be fine since that would
>append the full name on there, but the "." (dot)
terminates
>the name.
>
>The normal case is that the full name is actually written
out
>in there with the terminating dot, e.g.,
server.domain.com.
>
>
>
>--
>Herb Martin
>
>
>"Gary" <anonymous@discussions.microsoft.com> wrote in
message
>news:362201c4a044$886d9600$a501280a@phx.gbl...
>> 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: Gary: "No Host Name listed in Netdiag"
- Previous message: Richard G. Harper: "Re: Windows cannot obtain the domain controller name for your computer network. Return value (59)."
- 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
|
