none
how to fix DNS error?

    Question

  • Problem:

    >netdiag.exe /test:DNS


    DNS test . . . . . . . . . . . . . : Failed
        [WARNING] The DNS entries for this DC are not registered correctly on DNS se
    rver '192.168.3.202'. Please wait for 30 minutes for DNS server replication.
        [FATAL] No DNS servers have the DNS records for this DC registered.

    -----------------------------------------------------------------------------------------
    how to fix?



    My Testing Result:


    TCP/IP setting:
    "Register this connection's addresses in DNS" is checked

    nslookup:
    Default Server:  dc1.abc.com
    Address:  192.168.3.202


    netdiag.exe /fix:


    DNS test . . . . . . . . . . . . . : Failed
        [FIX] re-register DC DNS entry 'wahyan.edu.hk.' on DNS server '192.168.3.202
    ' succeed.
        FIX PASS - netdiag re-registered missing DNS entries for this DC successfull
    y on DNS server '192.168.3.202'.
        [FATAL] No DNS servers have the DNS records for this DC registered.


    netdiag.exe /test:DNS /v:

    DNS test . . . . . . . . . . . . . : Failed
    Interface {CBBEF828-C8C9-4972-8426-375843E03DC4}
    DNS Domain:
    DNS Servers: 192.168.3.202
    IP Address: Expected registration with PDN (primary DNS domain n
    ame):
    Hostname: dc1.abc.com.
    Authoritative zone: abc.com.
    Primary DNS server: dc1.abc.com 192.168.3.202
    Authoritative NS:192.168.3.202
    Check the DNS registration for DCs entries on DNS server '192.168.3.202'
    The Record is different on DNS server '192.168.3.202'.
    +------------------------------------------------------+
    The record on your DC is:
    DNS NAME = abc.com.
    DNS DATA =
    A 192.168.3.202
    The record on DNS server 192.168.3.202 is:
    DNS NAME = abc.com.
    DNS DATA =
    CNAME dc1
    +------------------------------------------------------+
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    The Record is correct on DNS server '192.168.3.202'.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS se
    rver '192.168.3.202'. Please wait for 30 minutes for DNS server replication.
    [FATAL] No DNS servers have the DNS records for this DC registered.
    Friday, December 05, 2008 12:26 AM

Answers

  •  

    Hi,

     

    How many DCs are there in the environment?

     

    Please open the DNS management console and check if the A record for the domain abc.com exists. If the record does not exist, restart the Net Logon service and type the command ipconfig /registerdns on the DC, and then perform the test again to see if the issue is solved.

     

    If the issue persists, please check if there is any warning or error logged in the DNS event log.

    Monday, December 08, 2008 7:55 AM