cant resolve GUID DNS name

[Azz]

Can a guru tell me what this means, and what do i do to get this corrected?
Thanx
Aze
below is the DCDIAG:

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\BDC
Starting test: Connectivity
BDC'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

(b2b1a235-a813-4691-b5b1-12d99cd079de._msdcs.CONSARCDG) couldn't be

resolved, the server name (bdc.CONSARCDG) resolved to the IP
address

(192.0.0.6) and was pingable. Check that the IP address is
registered

correctly with the DNS server.
......................... BDC failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\BDC
Skipping all tests, because server BDC is
not responding to directory service requests

Running enterprise tests on : CONSARCDG
Starting test: Intersite
......................... CONSARCDG passed test Intersite
Starting test: FsmoCheck
......................... CONSARCDG passed test FsmoCheck

--

 

[Herb Martin]

Your DCs will attempt to register various records automatically
in DNS -- including some records based on their "GUID" or
Globably Unique Identifier -- it's a big long number that uniquely
identifies each DC (in this context but GUIDs are used in many
other places too, like COM+)

This may fail if they cannot reach the right DNS server which
is also able to accept DYNAMIC registrations.

Check to make sure the DC is a CLIENT of the correct DNS
(set) and that these DNS servers support and enable dynamic
updates.

If you must change either setting, stop and start the NetLogon
Service:

Net Stop NetLogon
Net Start NetLogon

(Starting the NetLogon server re-registers these records.)

 

[Azz]

Herb,
Hi I'm afraid this is over my head.

The BDC have this GUID problem, whilst the Server-2 doesn't. The main DNS is
on Server-2 (DC). All other clients points to this server. Both BDC and
server-2 are set to receive dynamic updates.

When you say check the DC is a client, how do you mean ? The DNS is also
running on BDC and has been ever and replicating fine until service pack 4
was installed.

As I said previously Herb, this is going to be panic time, as the main
server is not looking that good, and if there is no replication, ......
should I be worried here ?

 

[Herb Martin]

Herb,
Hi I'm afraid this is over my head.

The BDC have this GUID problem, whilst the Server-2 doesn't. The main DNS is
on Server-2 (DC). All other clients points to this server. Both BDC and
server-2 are set to receive dynamic updates.

There are no Win2000+ BDCs -- only DCs. If you have true BDCs
then they are running NT and don't use the GUIDs in DNS but since
you also say, "set to receive Dynamic updates" this strongly suggests
that they are Win2000 as NT DNS doesn't support dynamic updates.

When you say check the DC is a client, how do you mean ? The DNS is also
running on BDC and has been ever and replicating fine until service pack 4
was installed.

Check the DC's own CLIENT NIC/IP properties to make sure it points
at (one of) those DYNAMIC DNS servers -- if it doesn't register OR they
are not accepting dynamic registrations you will not get these records
automatically. (Also make sure your DHCP client is running -- some people
turn that off on the theory that they aren't using DHCP but this client is
the
one that DOES the client's dynamic registration and you need it even for
static IP address machines IF they need to be registered automatically.)

As I said previously Herb, this is going to be panic time, as the main
server is not looking that good, and if there is no replication, ......
should I be worried here ?

Sure -- if you don't have replication then your AD isn't going to work
the way you hope.

The DCs need those records to find and replicate with each other.

ALL DCs must be DNS clients of your dynamic zone (NIC/IP
property setting.)

 

[Azz]

Hi, thanx,

The BDC is only a name allocated to the second DC. It could have been called
DC2 or anything. So they are not NT machines upgraded.
They were all windows 2000. The BDC (a DC) is SP4, and server-2 is on SP3.

The server-2 has DNS installed and pointing to itself.
The BDC (DC) has DNS installed and pointing to DNS on server-2.
BDC and server-2 have DHCP on them and running. All other clients are
pointing to DNS on server-2 as well.
All addresses are static.

So what's there I have overlooked ?

 

[Herb Martin]

The BDC is only a name allocated to the second DC. It could have been
called

DC2 or anything. So they are not NT machines upgraded.
They were all windows 2000. The BDC (a DC) is SP4, and server-2 is on SP3.

To avoid confusion, don't call it "THE BDC" (a title) but
rather identify it or call it, the DC "BDC", or just "BDC"
to avoid confusion as much as practical.

The server-2 has DNS installed and pointing to itself.
The BDC (DC) has DNS installed and pointing to DNS on server-2.
BDC and server-2 have DHCP on them and running. All other clients are
pointing to DNS on server-2 as well.
All addresses are static.

So what's there I have overlooked ?

You NEED Dynamic updates on the Primary DNS server,
and you need to make sure the DCs can easily reach that
DNS server (probably best to point their client properties
to the DYNAMIC Primary.)

It is not pratical to have DNS which supports a Win2000
Domain use "All static addresses".

Those GUID records are a prime examples of dynamic
records that WILL be registered if you set your DNS
to allow dynamic updates and RESTART the NetLogon
service.

 

[Ace Fekay [MVP]]

In

To avoid confusion, don't call it "THE BDC" (a title) but
rather identify it or call it, the DC "BDC", or just "BDC"
to avoid confusion as much as practical.


You NEED Dynamic updates on the Primary DNS server,
and you need to make sure the DCs can easily reach that
DNS server (probably best to point their client properties
to the DYNAMIC Primary.)

It is not pratical to have DNS which supports a Win2000
Domain use "All static addresses".

Those GUID records are a prime examples of dynamic
records that WILL be registered if you set your DNS
to allow dynamic updates and RESTART the NetLogon
service.

Herb, don;t know if you saw Azz's earlier post, but this stems back to a
single label name domain and is what's causing the problems. Now after
reading this thread, I see he doesn't have an NT4 BDC, but just in "name",
which confused me in the earlier post because I suggested to dump the W2k
box, and go back, promote the NT4 BDC to PDC, and reinstall it as an NT4
BDC, etc. But now I see that this won't work because of his two W2k DCs.

I agree the use of names such as BDC can be confusing since that is a legacy
term from NT4.

If he could export his users with CSVDE, make some modifications for the
domain name and get rid of some of the unnecessary speicif attributes, then
reinstall the W2k box, and re-import the users, Ass will be better off,
otherwise he can bandaid it with that reg entry to force DNS to allow single
label names and possibly keep getting these errors for time to come.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Ace Fekay [MVP]]

In

I agree --what's in a name? A rose by any other name....

Er, he might object to you renaming HIM as "Ass" though. <grin>

NO rename intended there! BIG Typo. I apologize for that!

[Before anyone takes this serious, I am SURE it was a TYPO -- I
make those all the time too.]

Yes, I dearly apologize, it was a typo. S and Z are right near each other
and I must have fat fingered the keys or something. But that's no excuse.

Azz, once again, I dearly apologize!

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Herb Martin]

I know you well enough to know it was a mistake--
he probably does too.

But I couldn't resist pointing it out -- since it was a
"rename" issue.

 

[Ace Fekay [MVP]]

In

I know you well enough to know it was a mistake--
he probably does too.

But I couldn't resist pointing it out -- since it was a
"rename" issue.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Ace Fekay [MVP]]

In

Guys, no harm done as I do it all the time, especially when the name
is Aze (pronounced as Asa, sometimes people called me Ace as well).
Ace, you might want to chuckle over this.
Unfortunately, though, I had gone back to Sp3 and those errors
disappeared (seemed like) and the DCDIAG is ok. Although there is no
replication whatsoever. I will post you the DCDIAG from BDC and
Server-2.

Azz

Interesting, I get the same from my Irish friends, the way they pronounce
"Ace".

SP3? Strange going backwards fixed this. Were you getting 5781 errors as
well (Event viewer)?


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Azz]

There were 5781 errors after SP4 was installed, but can't see any now.

But now it's the NTFRS errors cropping up, and where in the newsgroups are
these located?
Does anybody know about fixing the 13505, 13555 , 13506, 13568 errors ? Why
these errors ?
Please help..
Azz

 

[Ace Fekay [MVP]]

In

There were 5781 errors after SP4 was installed, but can't see any now.

But now it's the NTFRS errors cropping up, and where in the
newsgroups are these located?
Does anybody know about fixing the 13505, 13555 , 13506, 13568 errors
? Why these errors ?
Please help..
Azz

Hmm, did you ever post an ipconfig /all of this server? I looked back, but
didn't see one, unless I missed it. I know we got off topic a bit, so asking
for a memory refresh. I would like to see it. Can you also refresh my memory
as to what your ADUC reports to be the domain name too?

Here's some links to that. But these can all be DNS based.

13555
http://www.eventid.net/display.asp?eventid=13555&source=

13506
http://www.eventid.net/display.asp?eventid=13506&source=
http://support.microsoft.com/default.aspx?scid=KB;en-us;296776

13568
http://www.eventid.net/display.asp?eventid=13568&source=
http://support.microsoft.com/?id=307319





--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Azz]

Ace Hi,
previousl;y the problem was BDC. Now going back to SP3 there is no problem
with BDC but there's no replication at all except in the MMC. So any changes
made to say the users/groups will be reflected across to both DCs.
But the sysvol won't replicate.
The idea of replacing the 0 with the one (below) have been thought of, but
it sound like trouble going to brew up. So I gatherI won't do unless
verified safe. If I have the time, I'll put down later why I think it will
be trouble. But I won't drop the idea altogether.
..
Here is the IPCONFIG,:
Windows 2000 IP Configuration Host Name . . . . . . . . . . . . : SERVER-2
Primary DNS Suffix . . . . . . . : CONSARCDG
Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . .
.. : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . .
.. . : CONSARCDG

Ethernet adapter Intel Fast Ethernet LAN Controller - onboard:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 Network Connection
Physical Address. . . . . . . . . : this is taken out
DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . :
192.0.0.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.0.0.9 DNS Servers . . . . . . . . .
.. . : 192.0.0.2
192.0.0.6


The server-2 (192.0.0.2) is first DC in the forest. CONSARDG is the only
domain. BDC is also a DC (192.0.0.6)
DNS are on both dcs.

I would have posted the DCDIAG and NETDIAG as well but they are too long,
they looked fine though except this:

Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... SERVER-2 passed test frssysvol

and

Starting test: systemlog
An Error Event occured. EventID: 0xC0001B77
Time Generated: 07/30/2003 16:26:45
Event String: The File Replication Service service terminated
.......................... SERVER-2 failed test systemlog

On the DNS :It's not an error though,

DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server
'192.0.0.2' and other DCs also have some of the names registered.
PASS - All the DNS entries for DC are registered on DNS server
'192.0.0.6' and other DCs also have some of the names registered.

Appreciate feedback on what this is all about (my thought were staging file,
FRS stopped too long though I didn't do it). To complete re-install (which
have to be done in the longer run) is a laborious job. So HELP!!
Thanx Azé

 

[Ace Fekay [MVP]]

In

Ace Hi,
previousl;y the problem was BDC. Now going back to SP3 there is no
problem with BDC but there's no replication at all except in the MMC.
So any changes made to say the users/groups will be reflected across
to both DCs.
But the sysvol won't replicate.
The idea of replacing the 0 with the one (below) have been thought
of, but it sound like trouble going to brew up. So I gatherI won't do
unless verified safe. If I have the time, I'll put down later why I
think it will be trouble. But I won't drop the idea altogether.
.
Here is the IPCONFIG,:
Windows 2000 IP Configuration Host Name . . . . . . . . . . . . :
SERVER-2 Primary DNS Suffix . . . . . . . : CONSARCDG
Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . .
. . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search
List. . . . . . : CONSARCDG

Ethernet adapter Intel Fast Ethernet LAN Controller - onboard:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 Network
Connection Physical Address. . . . . . . . . : this is taken out
DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . .
. . : 192.0.0.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.0.0.9 DNS Servers . . . . . .
. . . . . : 192.0.0.2
192.0.0.6


The server-2 (192.0.0.2) is first DC in the forest. CONSARDG is the
only domain. BDC is also a DC (192.0.0.6)
DNS are on both dcs.

I would have posted the DCDIAG and NETDIAG as well but they are too
long, they looked fine though except this:

Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... SERVER-2 passed test frssysvol

and

Starting test: systemlog
An Error Event occured. EventID: 0xC0001B77
Time Generated: 07/30/2003 16:26:45
Event String: The File Replication Service service
terminated ......................... SERVER-2 failed test systemlog

On the DNS :It's not an error though,

DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server
'192.0.0.2' and other DCs also have some of the names registered.
PASS - All the DNS entries for DC are registered on DNS server
'192.0.0.6' and other DCs also have some of the names registered.

Appreciate feedback on what this is all about (my thought were
staging file, FRS stopped too long though I didn't do it). To
complete re-install (which have to be done in the longer run) is a
laborious job. So HELP!!
Thanx Azé

Yes, those errors are based on the single label name and possible not
registering. You can bandaid it with this link:

Information About Configuring Windows 2000 for Domains with Single-Label DNS
Names
http://support.microsoft.com/?id=300684

If you want, here's a way to rename it, if you choose to do so:
How to Rename the DNS Name of a Windows 2000 Domain
http://support.microsoft.com/?id=292541

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory