Re: nslookup question

From: Jim Harrison [MSFT] (jmharr_at_online.microsoft.com)
Date: 07/12/04 

Date: Mon, 12 Jul 2004 16:01:11 -0700

There are two different questions here:
1 - nslookup "can't find name for server"; this is normally caused by missing reverse lookup zones on the DNS server. Windows help
has a pretty good discussion on basic DNS setup and configuration.
2 - "slow internet" is most often a factor of name resolution, especially for web proxy and firewall clients. If ISA has trouble
resolving names, then they will too.

Something you need to keep in mind; nslookup operates a bit differently for name resolution than do most other network apps.
Nslookup speaks directly to the DNS server, while other apps ask Windows to figure it out via Winsock calls.
What this means to you is that you can have completely different behavior from nslookup than you do from other apps under perfectly
functional circumstances, especially if the Firewall Client is installed on the test host. 

-- 
 Jim Harrison [ISASE]
 Read the help, books and articles!
 This posting is provided "AS IS" with no warranties, and confers no rights.
"Mike A" <Leorick_2000@Hotmail.Com> wrote in message news:uLeFmvfZEHA.3132@TK2MSFTNGP10.phx.gbl...
Dainel, this is a good question.  I have the same problem, hopefully someone
out there might be able to help or at least explain what the problem is.
"Daniel" <webmaster@nhscomputerclub.com> wrote in message
news:4cadd7d3.0406291905.d1d144f@posting.google.com...
> I installed ISA 2000 on a DC (Configured as intergrated mode) and when
> I run nslookup on any machine on the network I get an error can't find
> server name for 10.20.121.200 (The server).  I was just wondering if
> this is ok and I have one other question.  The internet is so much
> slower and im just wondering what is causing it.  (when I run nslookup
> sometimes it finds the dns name sometimes it times out.)  When they
> went on regularly they could get to any web page real fast.  Now it
> takes 5 sec instead of 1 sec to get to a webpage.  All the dns and
> gateways of the clients are set to the server and they can connect to
> the internet and the web proxy works.  It is just slower.
>
> I hope someone can help
>
> Thanks

Relevant Pages

  • Re: Cannot Resolve Names Outside Windows Domain
    ... What do you mean "nslookup does not work correctly when I leave the domain"? ... If you don't connect to the domain, which DNS you will use? ... nslookup works properly when I am logged into the windows domain: ... the domain server on the windows domain, the ip address, but the name is ...
    (microsoft.public.windowsxp.network_web)
  • Re: Registered domain name not translating internally
    ... Once you fix your DNS, clear your Event Viewer logs, then your dcdiag output ... When you do an nslookup, it should find your server if you have a reverse ... SBS Server is setup with one NIC. ...
    (microsoft.public.windows.server.sbs)
  • Re: Can NSLOOKUP do this......?
    ... > Firstly may I say I am still learning about DNS. ... ie I have used nslookup with the d2 switch ... > and it shows a query to my local DNS server, ... > The way I understand the resolution process in this scenario would be my ...
    (microsoft.public.windows.server.dns)
  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)