Re: Netdiag errors, again, [FATAL] Invalid DNS entries

From: Kevin D. Goodknecht Sr. [MVP] (admin_at_nospam.WFTX.US)
Date: 08/12/04


Date: Thu, 12 Aug 2004 05:26:26 -0500

In news:04c401c47f93$4e80a3f0$3501280a@phx.gbl,
jellis <anonymous@discussions.microsoft.com> wrote their comments
Then Kevin replied below:
> Below is a repost. If you read the contents you'll see
> that I posted a question. Got a reply. Performed the
> steps recommended. Didn't work. Replyed to the reply
> requesting additional assistance. Got no answer. Below
> is the thread in its entirety.
>
> This problem is getting old and the client is getting
> pissed. Help is needed.
>
> Thanks
>
> -------------------------------------------------------
> Thanks for your advice. Unfortunately it didn't resolve
> the problem.
>
> I reviewed the articles recommended. Made a few
> adjustments (Enabled Append primary and connection
> specific DNS suffixes, Append parent suffixes of the
> primary DNS suffix) restarted DNS server, ran Netdiag,
> same result.
>
> Below is the output from Netdiag:
> DNS test . . . . . . . . . . . . . : Failed
> [WARNING] The DNS host name 'zack_dc1.Zack.Loc' valid
> only on Windows 2000 DNS Servers. [DNS_ERROR_NON_RFC_NAME]
> [FATAL] File \config\netlogon.dns contains invalid
> DNS entries. [FATAL] No DNS servers have the DNS
> records for this DC registered.
>
> The messages are confusing in that the DNS server running
> on the domain controller "zack_dc1" clearly has records
> for "zack_dc1".

It is just as the message says, it is a non RFC name that is only valid only
on Windows 2000 servers.

 Go to the system32\config\ directory and delete the Netlogon.dns and
netlogon.dnb files. Then run ipconfig /flushdns, ipconfig /registerdns and
restart the netlogon service. Run netdiag /fix and netdiag /test:dns /v

-- 
Best regards,
Kevin D4 Dad 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/
================================================
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: Netdiag kerberos failure
    ... important for kerberos. ... keep in time synch with the domain controller that is the pdc fsmo which is the time ... Check the Event Viewer on the domain controller and run first netdiag on it and then ... assigned IP address as it's preferred dns server in tcp/ip properties and W2K/Xp Pro ...
    (microsoft.public.win2000.networking)
  • Re: Assign Domain Security Policy/Manage remote computer
    ... > I've run netdiag and dcdiag on the domain controller (Active Directory ... > The dc does refer to itself as it's DNS server. ... > Not done anything more with the IPSec config yet, ...
    (microsoft.public.win2000.security)
  • Re: GP cannont find Domain Controller
    ... so netdiag run on the DC see no problem. ... > DNS server is running and at least apparently working ok ... >> If it come out clean on the DCs, ... >> Microsoft MVP (Windows Security) ...
    (microsoft.public.windows.group_policy)
  • Re: Netdiag DNS error
    ... > was why this error keeps popping up in netdiag: ... Interfaces tab of the DNS server properties. ... 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. ...
    (microsoft.public.win2000.dns)
  • Re: EventID 3034 Error
    ... What type of errors did netdiag show? ... important to know to help determine whether the problem is with network ... > currently the DNS resolution is set to Append DNS suffixes and the correct ... > However I have been advised that I need to change the DNS search order to ...
    (microsoft.public.windows.server.networking)