unable to get a nslookup on windows client

[Kevin Darcy]

Short version (not that I'm famous for being terse): nslookup sucks.

                                                                         
                           - Kevin

Barry Finkel wrote:
> "Agnello George" <agnello.dsouza at gmail.com> wrote, in part:
>
>   
>> but wheni try to do a nslookup for 192.168.0.244 on my windows client i get
>> the following i can how ever ping to 192.168.0.244
>>
>> C:\Documents and Settings\Admin>nslookup ns1.testserver.com
>> *** Can't find server name for address 192.168.0.244: No response from
>> server
>> *** Default servers are not available
>> Server:  UnKnown
>> Address:  192.168.0.244
>>
>> *** UnKnown can't find ns1.testserver.com: No response from server
>>     
>
> As has been mentioned many times before, do not use nslookup as a
> DNS debugging tool.  Many versions of nslookup require that the
> DNS server being queried be registered, both forward and reverse.
> If this is not the case, then nslookup quits.  Also, nslookup will
> display some output, and that output may not be the response to your
> query.  If you use nslookup in debug mode, then you will see the
> DNS response packet formatted, and you can determine the response to
> your query.
> ----------------------------------------------------------------------
> Barry S. Finkel
> Computing and Information Systems Division
> Argonne National Laboratory          Phone:    +1 (630) 252-7277
> 9700 South Cass Avenue               Facsimile:+1 (630) 252-4601
> Building 222, Room D209              Internet: BSFinkel at anl.gov
> Argonne, IL   60439-4828             IBMMAIL:  I1004994
>
>
>
>
>