Announcement

Collapse
No announcement yet.

nslookup fails on my dns server, windows server 2003.

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • nslookup fails on my dns server, windows server 2003.

    hi all, i would be grateful for any assistance with my problem outlined below.

    this is happening within a native windows server 2003 R2 domain. i set this domain up a couple of years ago. unfortunately not from scratch, but as a migration from a poorly setup 2003SBS environment, i believe the issue i am having is as a legacy from this, and me not setting up the DNS correctly. as far as i can tell active directory is functioning ok, group policy is working, and i haven't had any problems over the years until i was investigating an internet connectivity issue during which i found this problem.

    when i am logged onto the global catalogue/dns server called hawk with ip 192.168.0.31 and run "nslookup" from the command prompt i get the following error:

    C:\Documents and Settings\Administrator>nslookup
    *** Can't find server name for address 192.168.0.31: Non-existent domain
    Default Server: UnKnown
    Address: 192.168.0.31

    if i perform an nslookup for an internet address i get the following result:

    C:\Documents and Settings\Administrator>nslookup petri.co.il
    *** Can't find server name for address 192.168.0.31: Non-existent domain
    Server: UnKnown
    Address: 192.168.0.31
    Non-authoritative answer:
    Name: petri.co.il
    Address: 204.236.131.24

    various guides have instructed me to create an [A] host within the forward lookup with the update associated pointer record (PTR) ticked. when i navigate to DNS -> Forward Lookup Zones -> star-emea.local (the name of my domain) there is an [A] host for hawk present. If i delete the host reference and recreate it i get the error:

    "Warning: the associated pointer (PTR) record cannot be created, probably because the referenced reverse lookup zone cannot be found."

    the host does get generated and the PTR box is ticked, but i still get the same nslookup error. i do have a reverse lookup zone, whether or not it is functioning correctly is another matter.

    Please advise me what logs or further information you require. here is a copy of my netdiag report.


    Microsoft Windows [Version 5.2.3790]
    (C) Copyright 1985-2003 Microsoft Corp.
    C:\Documents and Settings\Administrator>nslookup
    *** Can't find server name for address 192.168.0.31: Non-existent domain
    Default Server: UnKnown
    Address: 192.168.0.31
    >
    C:\Documents and Settings\Administrator>netdiag
    ......................................
    Computer Name: HAWK
    DNS Host Name: hawk.star-emea.local
    System info : Microsoft Windows Server 2003 R2 (Build 3790)
    Processor : x86 Family 6 Model 15 Stepping 11, GenuineIntel
    List of installed hotfixes :
    KB921503
    KB924667-v2
    KB925336
    KB925398_WMP64
    KB925876
    KB925902
    KB926122
    KB927891
    KB929123
    KB930178
    KB931784
    KB932168
    KB933360
    KB933729
    KB933854
    KB935839
    KB935840
    KB935966
    KB936021
    KB936357
    KB936782
    KB937143
    KB938127
    KB939653
    KB941202
    KB941568
    KB941569
    KB941644
    KB941672
    KB941693
    KB942763
    KB942830
    KB942831
    KB943055
    KB943460
    KB943484
    KB943485
    KB944338
    KB944653
    KB945553
    KB946026
    KB947864
    KB948496
    KB948590
    KB948881
    KB949014
    KB950762
    KB950974
    KB951066
    KB951698
    KB951748
    KB952954
    KB954550-v5
    KB955069
    KB956841
    KB957097
    KB958644
    Q147222

    Netcard queries test . . . . . . . : Passed
    [WARNING] The net card 'Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client
    ) #2' may not be working.

    Per interface results:
    Adapter : 192.168.0.31 1GB
    Netcard queries test . . . : Passed
    Host Name. . . . . . . . . : hawk.star-emea.local
    IP Address . . . . . . . . : 192.168.0.31
    Subnet Mask. . . . . . . . : 255.255.255.0
    Default Gateway. . . . . . : 192.168.0.201
    Dns Servers. . . . . . . . : 192.168.0.31
    195.74.128.6

    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. . . . . : Skipped
    There are no WINS servers configured for this interface.
    Adapter : Local Area Connection 2
    Netcard queries test . . . : Failed
    NetCard Status: DISCONNECTED
    Some tests will be skipped on this interface.
    Host Name. . . . . . . . . : hawk
    Autoconfiguration IP Address : 169.254.1.198
    Subnet Mask. . . . . . . . : 255.255.0.0
    Default Gateway. . . . . . :
    Dns Servers. . . . . . . . : 127.0.0.1


    Global results:

    Domain membership test . . . . . . : Passed

    NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
    NetBT_Tcpip_{5ACBC07B-215F-4CDA-94B7-390BED4258B2}
    NetBT_Tcpip_{D6A36EB8-5453-4641-97E9-B4A28BF27B0B}
    2 NetBt transports 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
    PASS - All the DNS entries for DC are registered on DNS server '192.168.0.31
    ' and other DCs also have some of the names registered.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS se
    rver '195.74.128.6'. Please wait for 30 minutes for DNS server replication.
    PASS - All the DNS entries for DC are registered on DNS server '127.0.0.1' a
    nd other DCs also have some of the names registered.

    Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
    NetBT_Tcpip_{5ACBC07B-215F-4CDA-94B7-390BED4258B2}
    NetBT_Tcpip_{D6A36EB8-5453-4641-97E9-B4A28BF27B0B}
    The redir is bound to 2 NetBt transports.
    List of NetBt transports currently bound to the browser
    NetBT_Tcpip_{5ACBC07B-215F-4CDA-94B7-390BED4258B2}
    NetBT_Tcpip_{D6A36EB8-5453-4641-97E9-B4A28BF27B0B}
    The browser is bound to 2 NetBt transports.

    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
    C:\Documents and Settings\Administrator>

  • #2
    Re: nslookup fails on my dns server, windows server 2003.

    This is not really a problem. The nslookup messages you're getting about

    "*** Can't find server name for address 192.168.0.31: Non-existent domain
    Default Server: UnKnown"

    mean that there is no reverse lookup zone for your subnet, that there's no PTR record for the AD\DNS server with ip address 192.168.0.31, or that the reverse lookup zone is not behaving properly (all as you've stated) but it has no bearing on the operation of your DNS server. Reverse lookup zones are not required and the lack of one will not hamper the operation of AD or DNS.

    My suggestion would be to delete the current reverse lookup zone and recreate it from scratch.

    Comment


    • #3
      Re: nslookup fails on my dns server, windows server 2003.

      joeqwerty, thank you for taking the time to reply.

      so from your post it would seem that this proble isn't really a problem for me in my ad/dns environment. i am not very familiar with DNS and the network is working fine at the moment so i don't like to fiddle with things that i am not sure of.

      i posted the question incase my nslookup failing might be causing potential errors or time outs for various services that i wasn't aware of. i will leave it untouched.

      thanks again.

      Comment


      • #4
        Re: nslookup fails on my dns server, windows server 2003.

        It threw me off too when I was just getting started with Windows DNS. This is what is happening:

        Your computer (or server) is configured with the ip addresses of the servers it should use for DNS. When you launch nslookup it will try to resolve the ip address for the server listed as the primary DNS server in the DNS settings of the network card. It does this by forming a PTR lookup for the ip address and sending it to the server listed as the primary DNS in the DNS settings of the network card. Basically it's trying to find the name of the server listed as it's primary DNS server (I don't know why nslookup was designed to do this as it doesn't help anything). If it can't resolve the name it gives you the messages you were seeing.

        At the end of the day, a PTR zone isn't required or needed so there's no harm in not having one.

        Also, when you're dealing with your DNS server remember that the DNS server component and the DNS client component on the server are two separate and unrelated components that don't interact with each other except in the same way that any other DNS client interacts with a DNS server. This can throw you off when you're dealing with DNS problems on the DNS server itself. For instance, clearing the DNS client cache and clearing the DNS server cache on the DNS server are two unrelated operations. I often hear people say "My DNS server isn't working right even though I cleared the cache using ipconfig/flushdns". I then remind them that they haven't cleared the DNS server cache they've cleared the DNS client cache.

        OK, enough of my long-windedness...

        Comment

        Working...
        X