none
[WARNING] Cannot find a primary authoritative DNS server for the name

    Question

  • hey guys i have a funny question it might be the wrong place to post it,

    but everybody who installed exchange had to pass through this.....

    im setting new exchange 2003 server
    on 2003 r2 server

    when i do pre check of netdiag i get this error :
    ===================================================

    [WARNING] Cannot find a primary authoritative DNS server for the name
      'xxx.xxxxx.xxx.xx.'. [ERROR_TIMEOUT]

    ===================================================

     

    complete log of the netdiag :
    -----------------------------
        Computer Name: xxx
        DNS Host Name: xxx.xxxxx.xxx.xx
        System info : Microsoft Windows Server 2003 (Build 3790)
        Processor : x86 Family 15 Model 4 Stepping 8, GenuineIntel
        List of installed hotfixes :
            KB921503
            KB924667-v2
            KB925398_WMP64
            KB925876
            KB925902
            KB926122
            KB927891
            KB929123
            KB930178
            KB931784
            KB932168
            KB933360
            KB933854
            KB935839
            KB935840
            KB936021
            KB936357
            KB936782
            KB937143
            KB938127
            Q147222


    Netcard queries test . . . . . . . : Passed
        [WARNING] The net card 'Microsoft Tun Miniport Adapter' may not be working.

     

    Per interface results:

        Adapter : RTL 7128G 54M

            Netcard queries test . . . : Passed

            Host Name. . . . . . . . . : srv
            IP Address . . . . . . . . : 192.168.1.100
            Subnet Mask. . . . . . . . : 255.255.255.0
            Default Gateway. . . . . . : 192.168.1.1
            Primary WINS Server. . . . : 192.168.1.100
            Dns Servers. . . . . . . . : 192.168.1.100
                                         192.168.1.1
                                         192.115.106.35
                                         194.90.1.5


            AutoConfiguration results. . . . . . : Passed

            Default gateway test . . . : Passed

            NetBT name test. . . . . . : Passed
            [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
    r Service', <20> 'WINS' names is missing.

            WINS service test. . . . . : Passed


    Global results:


    Domain membership test . . . . . . : Passed


    NetBT transports test. . . . . . . : Passed
        List of NetBt transports currently configured:
            NetBT_Tcpip_{E62E8B96-715C-45EC-89CD-67F25501D197}
        1 NetBt transport currently configured.


    Autonet address test . . . . . . . : Passed


    IP loopback ping test. . . . . . . : Passed


    Default gateway test . . . . . . . : Passed


    NetBT name test. . . . . . . . . . : Passed
        [WARNING] You don't have a single interface with the <00> 'WorkStation Servi
    ce', <03> 'Messenger Service', <20> 'WINS' names defined.


    Winsock test . . . . . . . . . . . : Passed


    DNS test . . . . . . . . . . . . . : Passed


              [WARNING] Cannot find a primary authoritative DNS server for the name
                'xxx.xxxxx.xxx.xx.'. [ERROR_TIMEOUT]
                The name 'xxx.xxxxx.xxx.xx.' may not be registered in DNS.


              [WARNING] Cannot find a primary authoritative DNS server for the name
                'xxx.xxxxx.xxx.xx.'. [ERROR_TIMEOUT]
                The name 'xxx.xxxxx.xxx.xx.' may not be registered in DNS.


          
        [WARNING] The DNS entries for this DC are not registered correctly on DNS

                server '0.0.0.0'. Please wait for 30 minutes for DNS server replication.


        PASS - All the DNS entries for DC are registered on DNS server '192.168.1.100'.


    Redir and Browser test . . . . . . : Passed
        List of NetBt transports currently bound to the Redir
            NetBT_Tcpip_{E62E8B96-715C-45EC-89CD-67F25501D197}
        The redir is bound to 1 NetBt transport.

        List of NetBt transports currently bound to the browser
            NetBT_Tcpip_{E62E8B96-715C-45EC-89CD-67F25501D197}
        The browser is bound to 1 NetBt transport.


    DC discovery test. . . . . . . . . : Passed


    DC list test . . . . . . . . . . . : Passed


    Trust relationship test. . . . . . : Skipped


    Kerberos test. . . . . . . . . . . : Passed


    LDAP test. . . . . . . . . . . . . : Passed


    Bindings test. . . . . . . . . . . : Passed


    WAN configuration test . . . . . . : Skipped
        No active remote access connections.


    Modem diagnostics test . . . . . . : Passed

    IP Security test . . . . . . . . . : Skipped

        Note: run "netsh ipsec dynamic show /?" for more detailed information


    The command completed successfully
    ---------------------------------------------------------

    to add on the pre info - i setup the dns with its own ip at first. everything seems to be working

    good internal resolutios and external resolutions, i have in the dns the _msdcs.sitename container
    the dns passes its own test. i have setup a reverse lookup zone which do works.

    the funny thing is i still get this error. what went wrong and how do i fix this error msg...???

    Thanks for all responders !

    Friday, October 05, 2007 8:53 AM

All replies

  • I have the same problem. Can any one please help
    Thursday, July 16, 2009 10:45 AM
  • Coud you please run netdiag /fix and see what happens? see for description


    http://support.microsoft.com/default.aspx/kb/219289
    Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|
    Thursday, July 16, 2009 11:18 AM
  • Follow what Vinod suggested, try running the netdiag /fix. If the problem persists, please check if your server have 2 LAN ports, if so  and you use only one of them, try disable the unused one and try netdiag again.
    Wednesday, September 09, 2009 10:15 AM
  • This is very general error occurs when we have two NICs configured in server. But I am sure only one NIC needs to be registered with DNS and another may not require as we configure them for legacy application in most of the cases...
    So solution for this is
    On secondary NIC card, Go to TCP/IP properties -> Advanced -> DNS, here Uncheck "Register this connections addresses in DNS"
    and make sure check mark is the for the same in Primary NIC.

    Cheers

    PITCHUKA
    • Proposed as answer by shadwick Sunday, July 08, 2012 3:21 PM
    Tuesday, October 20, 2009 7:52 AM
  • Thank you TopMasterchief & Pitchuka!  Your solution fixed it for me on a 2003 Standard DC
    Thursday, October 13, 2011 4:28 PM