Re: netdiag dns test fails

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Thanks for the info. Your right I was way off on the GUID thing. Iwas
thinking of GUI I think.

( A theroy I am working on is the server was forcefully removed from the AD
before and now there is a old GUID number is AD (metadata). The reason I say
this is in the error below I see references to 2 GUIDs
0a3e1b3d-0e06-40c2-bd88-8df7f613d62a
9b5ec568-8b40-4758-84b3-a1ae5a91b99d

What do you think?)

Tried what you suggested it did recreate the files. Ran the /fix command and
revcieved this.

NS test . . . . . . . . . . . . . : Failed
[FATAL] Failed to fix: DC DNS entry
_ldap._tcp.0a3e1b3d-0e06-40c2-bd88-8df7f613d62a.domains._msdcs.CVGLAB.LOCAL.
re-registeration on DNS server '172.16.68.210' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
[FATAL] Failed to fix: DC DNS entry
9b5ec568-8b40-4758-84b3-a1ae5a91b99d._msdcs.CVGLAB.LOCAL. re-registeration
on DNS server '172.16.68.210' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
[FATAL] Failed to fix: DC DNS entry
_kerberos._tcp.dc._msdcs.CVGLAB.LOCAL. re-registeration on DNS server
'172.16.68.210' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
[FATAL] Failed to fix: DC DNS entry
_kerberos._tcp.USKAB._sites.dc._msdcs.CVGLAB.LOCAL. re-registeration on DNS
server '172.16.68.210' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
[FATAL] Failed to fix: DC DNS entry
_kerberos._tcp.USDUB._sites.dc._msdcs.CVGLAB.LOCAL. re-registeration on DNS
server '172.16.68.210' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.CVGLAB.LOCAL.
re-registeration on DNS server '172.16.68.210' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
[FATAL] Failed to fix: DC DNS entry
_ldap._tcp.USKAB._sites.dc._msdcs.CVGLAB.LOCAL. re-registeration on DNS
server '172.16.68.210' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
[FATAL] Failed to fix: DC DNS entry
_ldap._tcp.USDUB._sites.dc._msdcs.CVGLAB.LOCAL. re-registeration on DNS
server '172.16.68.210' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
[FATAL] Fix Failed: netdiag failed to re-register missing DNS entries
for this DC on DNS server '172.16.68.210'.
[FATAL] No DNS servers have the DNS records for this DC registered.

"Kevin D. Goodknecht Sr. [MVP]" <admin@xxxxxxxxxxxxxx> wrote in message
news:eS0DCEr0GHA.4264@xxxxxxxxxxxxxxxxxxxxxxx
Eric wrote:
Have you disabled the DHCP client service?
The DHCP client service is a required service and must running and
set to automatic startup on all DCs and clients that register in DNS.

No I have not disabled them

Make sure you set up all your subnets in AD Sites and Services.

Verified all are listed

You also need to find the source of the APIPA record, and disable the
interface. This addresses are not routable on your network, and will
cause connectivity issues.

i agree the record needds to be removed and find out why it is there

None of this unfortannly helps with this issue.
9b5ec568-8b40-4758-84b3-a1ae5a91b99d._msdcs.CVGLAB.LOCAL. on DNS
server 172.16.68.210 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on
DNS server)
Correct me if I'm wrong bu thte problem is I have a guid (graphical
user id) this is in DNS that does not have a server for. A abondand
record perhaps?

GUID is not graphical user id, it is Globally Unique Identifier, each DC
has
one and is how DCs identify themselves and other DCs, without it
replication
breaks. This record is registered by the netlogon service.

You might try moving the %systemroot%\system32\config\netlogon.dns and
netlogon.dnb to a different place for backup and restart the netlogon
service. Then try netdiag /fix.

If this files aren't recreated and registered in DNS it may take a closer
look at the registry to see if the netlogon registration keys and values
are
correct.



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================




.

Relevant Pages

  • Re: DNS, DCDiag and Netdiag errors in a Single-label domain
    ... there is any other fix unless someone else has an idea. ... This box is also the DNS server. ... re-registeration on DNS ...
    (microsoft.public.win2000.active_directory)
  • Re: Replication issues
    ... I wanted to say Zone Transfers not Zone Forwarding. ... AD-Integrated DNS does not do zone transfers between the ... your DNS server will bypass ...
    (microsoft.public.windows.server.active_directory)
  • Re: Servers hang on boot
    ... The last DC at that site (not a DNS server). ... EventID: 0x00000457 ... (Event String could not be retrieved) ...
    (microsoft.public.windows.server.networking)
  • Re: NTDS replication problems
    ... Changing it to "server2" caused DNS to stop complaining and so it started to resolve everything neccassery to get AD going again, and hence exchange can now be started. ... Unfortunately I have butchered the machine as a result of trying to fix it by trial and error, ... But just be be sure I have run the .js script supplied to> fix this problem, and it hasn't :-( > So, still everytime that I start the DNS server it logs in the event log:> ... Its DNS name is a> single label hostname with no domain (example: ...
    (microsoft.public.win2000.active_directory)
  • Re: Please help a DNS dummie!
    ... > other Windows nodes on my LAN also point to this DNS server. ... > Failed to fix: ... > re-registeration on DNS server '192.168.10.10' failed. ...
    (microsoft.public.windows.server.dns)