Net Diag shows references to a non existent server


G

Guest

When I run the netdiag /v /l /test:dns command on my Dc which has Active
Directory Integrated DNS Installed the command passes successfully but I
also have a concern that it lists a server which is non existant on my
network. This is a part of the output.

The record on your DC is:
DNS NAME = _kpasswd._udp.xxx-xxx-xxx.com.
DNS DATA =
SRV 0 100 464 cat.xxx-xxx-xxx.com.

The record on DNS server 192.168.177.80 is:
DNS NAME = _kpasswd._udp.xxx-xxx-xxx.com
DNS DATA =
SRV 0 100 464 horse.xxx-xxx-xxx.com
SRV 0 100 464 cat.xxx-xxx-xxx.com
SRV 0 100 464 eagle2.xxx-xxx-xxx.com
SRV 0 100 464 dog.xxx-xxx-xxx.com
SRV 0 100 464 eagle.xxx-xxx-xxx.com
+------------------------------------------------------+

PASS - All the DNS entries for DC are registered on DNS server '192.168.177.
80' and other DCs also have some of the names registered.

The command completed successfully

I am not too sure from where it is listing eagle2.xxx-xxx-xxx.com(Maybe the
previous admin must have installed a machine with this name) , But currently
I have no such server.
What can I do to remove this server refrence. Pardon me for using these
server names as an example.

Thank You
JC
 
Ad

Advertisements

H

Herb Martin

jc said:
When I run the netdiag /v /l /test:dns command on my Dc which has Active
Directory Integrated DNS Installed the command passes successfully but I
also have a concern that it lists a server which is non existant on my
network. This is a part of the output.
[snip]

I am not too sure from where it is listing eagle2.xxx-xxx-xxx.com(Maybe the
previous admin must have installed a machine with this name) , But currently
I have no such server.

Probably it existed previously and was improperly
removed (e.g., by not running DCPromo.)
What can I do to remove this server refrence. Pardon me for using these
server names as an example.

NTDSUtil "metadata cleanup" is the way to cleanup this stuff.


NTDS metadata cleanup

Search Google for:

[ NTDS "metadata cleanup" remove DC Domain ]

No need to add either site:microsoft.com OR microsoft:
since the NTDS and other terms make it Microsoft specific
by itself.

Unless you WISH to restrict answers to the site:microsoft.com
for some reason.

[ NTDS "metadata cleanup" remove DC Domain site:microsoft.com ]

Key points to NOTE when doing the metadata cleanup:

You CONNECT to a WORKING DC.
You SELECT the missing/dead DC or DOMAIN

'Connect' and 'Select' are technical terms in this context.
 
K

Kevin D. Goodknecht Sr. [MVP]

In
jc said:
When I run the netdiag /v /l /test:dns command on my Dc
which has Active Directory Integrated DNS Installed the
command passes successfully but I also have a concern
that it lists a server which is non existant on my
network. This is a part of the output.

The record on your DC is:
DNS NAME = _kpasswd._udp.xxx-xxx-xxx.com.
DNS DATA =
SRV 0 100 464 cat.xxx-xxx-xxx.com.

The record on DNS server 192.168.177.80 is:
DNS NAME = _kpasswd._udp.xxx-xxx-xxx.com
DNS DATA =
SRV 0 100 464 horse.xxx-xxx-xxx.com
SRV 0 100 464 cat.xxx-xxx-xxx.com
SRV 0 100 464 eagle2.xxx-xxx-xxx.com
SRV 0 100 464 dog.xxx-xxx-xxx.com
SRV 0 100 464 eagle.xxx-xxx-xxx.com
+------------------------------------------------------+

PASS - All the DNS entries for DC are registered on DNS
server '192.168.177. 80' and other DCs also have some of
the names registered.

The command completed successfully

I am not too sure from where it is listing
eagle2.xxx-xxx-xxx.com(Maybe the previous admin must have
installed a machine with this name) , But currently I
have no such server.
What can I do to remove this server refrence. Pardon me
for using these server names as an example.

You can delete the record to see if it comes back, if it does, there is an
issue with Windows XP sometimes registering these Netlogon registrations,
you need to track down the offending client.
If you find that it is an XP client registering these records you should
install SP2 or contact MS for the hotfix.
Netlogon incorrectly registers SRV records in DNS for Windows XP-based
clients:
http://support.microsoft.com/default.aspx?scid=kb;en-us;825675
 
G

Guest

Thanks for your reply .
But I have used metadata cleanup and this server is not listed.
I can however see this server refrence at one more place.
If I open the DNS Console on the DC I see

DC1
.......Cached Lookups
.......Forward Lookup Zones
............xxx-xxx-xxx.com
............_msdcs ( I see the refrence to this server under sites here too)
............sites ( Expand sites ) [ It is also listed under _tcp and _udp)
.............Site1 (Expand Site1)
............_tcp ( The eagle2 server name is seen here)

it appears to be like this
_gc srv [0][100][368] eagle.xxx-xxx-xxx.com
_kerberos srv [0][100][88] eagle.xxx-xxx-xxx.com
_kerberos srv [0][100][88] horse.xxx-xxx-xxx.com
_ldap srv [0][100][389] eagle.xxx-xxx-xxx.com
_ldap srv [0][100][389] eagle2.xxx-xxx-xxx.com
_kerberos srv [0][100][88] dog.xxx-xxx-xxx.com


Can I just go ahead and delete refrence to eagle2 here ( nslookup and ping
does not return any results for eagle2). What services do I need to restart
after this.

Thank You for your help.
JC

Herb Martin said:
jc said:
When I run the netdiag /v /l /test:dns command on my Dc which has Active
Directory Integrated DNS Installed the command passes successfully but I
also have a concern that it lists a server which is non existant on my
network. This is a part of the output.
[snip]

I am not too sure from where it is listing eagle2.xxx-xxx-xxx.com(Maybe the
previous admin must have installed a machine with this name) , But currently
I have no such server.

Probably it existed previously and was improperly
removed (e.g., by not running DCPromo.)
What can I do to remove this server refrence. Pardon me for using these
server names as an example.

NTDSUtil "metadata cleanup" is the way to cleanup this stuff.


NTDS metadata cleanup

Search Google for:

[ NTDS "metadata cleanup" remove DC Domain ]

No need to add either site:microsoft.com OR microsoft:
since the NTDS and other terms make it Microsoft specific
by itself.

Unless you WISH to restrict answers to the site:microsoft.com
for some reason.

[ NTDS "metadata cleanup" remove DC Domain site:microsoft.com ]

Key points to NOTE when doing the metadata cleanup:

You CONNECT to a WORKING DC.
You SELECT the missing/dead DC or DOMAIN

'Connect' and 'Select' are technical terms in this context.
 
H

Herb Martin

jc said:
Thanks for your reply .
But I have used metadata cleanup and this server is not listed.
I can however see this server refrence at one more place.
If I open the DNS Console on the DC I see

Ok, well if it only appears in DNS you can just delete it.

If the server no longer exists it will not return (and is
not only unneeded but also counterproductive.)

Remove it from DNS.
DC1
......Cached Lookups
......Forward Lookup Zones
...........xxx-xxx-xxx.com
..........._msdcs ( I see the refrence to this server under sites here too)
...........sites ( Expand sites ) [ It is also listed under _tcp and _udp)
............Site1 (Expand Site1)
..........._tcp ( The eagle2 server name is seen here)

it appears to be like this
_gc srv [0][100][368] eagle.xxx-xxx-xxx.com
_kerberos srv [0][100][88] eagle.xxx-xxx-xxx.com
_kerberos srv [0][100][88] horse.xxx-xxx-xxx.com
_ldap srv [0][100][389] eagle.xxx-xxx-xxx.com
_ldap srv [0][100][389] eagle2.xxx-xxx-xxx.com
_kerberos srv [0][100][88] dog.xxx-xxx-xxx.com


Can I just go ahead and delete refrence to eagle2 here ( nslookup and ping
does not return any results for eagle2). What services do I need to restart
after this.

Thank You for your help.
JC

Herb Martin said:
jc said:
When I run the netdiag /v /l /test:dns command on my Dc which has Active
Directory Integrated DNS Installed the command passes successfully but I
also have a concern that it lists a server which is non existant on my
network. This is a part of the output.
[snip]

I am not too sure from where it is listing
eagle2.xxx-xxx-xxx.com(Maybe
the
previous admin must have installed a machine with this name) , But currently
I have no such server.

Probably it existed previously and was improperly
removed (e.g., by not running DCPromo.)
What can I do to remove this server refrence. Pardon me for using these
server names as an example.

NTDSUtil "metadata cleanup" is the way to cleanup this stuff.


NTDS metadata cleanup

Search Google for:

[ NTDS "metadata cleanup" remove DC Domain ]

No need to add either site:microsoft.com OR microsoft:
since the NTDS and other terms make it Microsoft specific
by itself.

Unless you WISH to restrict answers to the site:microsoft.com
for some reason.

[ NTDS "metadata cleanup" remove DC Domain site:microsoft.com ]

Key points to NOTE when doing the metadata cleanup:

You CONNECT to a WORKING DC.
You SELECT the missing/dead DC or DOMAIN

'Connect' and 'Select' are technical terms in this context.
 
G

Guest

Thank You , thank You, Thank you .
Netdiag runs just fine now. Thank You.


Herb Martin said:
jc said:
Thanks for your reply .
But I have used metadata cleanup and this server is not listed.
I can however see this server refrence at one more place.
If I open the DNS Console on the DC I see

Ok, well if it only appears in DNS you can just delete it.

If the server no longer exists it will not return (and is
not only unneeded but also counterproductive.)

Remove it from DNS.
DC1
......Cached Lookups
......Forward Lookup Zones
...........xxx-xxx-xxx.com
..........._msdcs ( I see the refrence to this server under sites here too)
...........sites ( Expand sites ) [ It is also listed under _tcp and _udp)
............Site1 (Expand Site1)
..........._tcp ( The eagle2 server name is seen here)

it appears to be like this
_gc srv [0][100][368] eagle.xxx-xxx-xxx.com
_kerberos srv [0][100][88] eagle.xxx-xxx-xxx.com
_kerberos srv [0][100][88] horse.xxx-xxx-xxx.com
_ldap srv [0][100][389] eagle.xxx-xxx-xxx.com
_ldap srv [0][100][389] eagle2.xxx-xxx-xxx.com
_kerberos srv [0][100][88] dog.xxx-xxx-xxx.com


Can I just go ahead and delete refrence to eagle2 here ( nslookup and ping
does not return any results for eagle2). What services do I need to restart
after this.

Thank You for your help.
JC

Herb Martin said:
When I run the netdiag /v /l /test:dns command on my Dc which has Active
Directory Integrated DNS Installed the command passes successfully but I
also have a concern that it lists a server which is non existant on my
network. This is a part of the output.

[snip]

I am not too sure from where it is listing eagle2.xxx-xxx-xxx.com(Maybe
the
previous admin must have installed a machine with this name) , But
currently
I have no such server.

Probably it existed previously and was improperly
removed (e.g., by not running DCPromo.)

What can I do to remove this server refrence. Pardon me for using these
server names as an example.

NTDSUtil "metadata cleanup" is the way to cleanup this stuff.


NTDS metadata cleanup

Search Google for:

[ NTDS "metadata cleanup" remove DC Domain ]

No need to add either site:microsoft.com OR microsoft:
since the NTDS and other terms make it Microsoft specific
by itself.

Unless you WISH to restrict answers to the site:microsoft.com
for some reason.

[ NTDS "metadata cleanup" remove DC Domain site:microsoft.com ]

Key points to NOTE when doing the metadata cleanup:

You CONNECT to a WORKING DC.
You SELECT the missing/dead DC or DOMAIN

'Connect' and 'Select' are technical terms in this context.
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top