Re: DNS and NSLOOKUP ISSUES

Maybe I'm not understanding what exactly you mean from the command. I launch CMD from the run menu and type NSLOOKUP. Can you enlighten me on the way that you're requesting this?

Thanks.


"Herb Martin" <news@xxxxxxxxxxxxxx> wrote in message news:eCs0%233ftIHA.4848@xxxxxxxxxxxxxxxxxxxxxxx

"Elrey" <fairbanksf@xxxxxxxxxxx> wrote in message news:74ACAE96-8AF0-4BDB-B55E-2C3EB4FCDB0A@xxxxxxxxxxxxxxxx
Here you go. I'm trying to figure out why I cannot see a website "acespower.com" and yet it resolves fine. Figured I'd try some NSLOOKUP queries to troubleshoot the matter. It seems to have opened a can of worms.

Thanks!

www.acespower.com
Server: h-dns.deseretgt.com
Address: 10.1.1.231

Well it resolves to a PRIVATELY administered address, so unless
that site in on YOUR Network (i.e., is internal routable then of course
you cannot get there.

Non-authoritative answer:
DNS request timed out.
timeout was 2 seconds.
Name: acespower.com
Address: 216.37.33.2
Aliases: www.acespower.com

I really wish you would do these from the COMMAND prompt
and include BOTH the "command" AND the (unedited) results.

Here you get an external address.

Are you getting different addresses when you query different
DNS Servers? (I would be able to tell that if you gave me the
INPUT COMMANDS.)

If so, there is your (likely) problem -- different answers from
different servers. DNS clients presume that ALL DNS clients
they CAN query will give both the CORRECT and the SAME
answers.

server 216.136.76.95
Default Server: ip95.bitwisesolutions.com
Address: 216.136.76.95

www.acespower.com
Server: ip95.bitwisesolutions.com
Address: 216.136.76.95

Name: www.acespower.com.deseretgt.com
Address: 216.190.14.35

Without you commands I can't tell you much more.
(There is a reason we ask for this stuff.)



"Herb Martin" <news@xxxxxxxxxxxxxx> wrote in message news:ek0$aVetIHA.1328@xxxxxxxxxxxxxxxxxxxxxxx

"Elrey" <fairbanksf@xxxxxxxxxxx> wrote in message news:A8F73CA0-BE58-4285-99B8-F41CDB0EB180@xxxxxxxxxxxxxxxx
Windows 2003 DNS

I'm trying to do some NSLOOKUP queries and I keep running into an odd problem on my workstations as well as the server. This only happens when I point to an external DNS server for verification purposes. If I use my DNS server for an NSLOOKUP query I get a proper response. However, like I said, if I use an external DNS for a query, for instance yahoo.com, I get a return of -

Name: www.yahoo.com.mydomain.com
Address : mydns.server.ip 192.168.1.1

Any ideas why this is happening?

Copy the exact commands you are using from the command prompt
with the responses -- don't edit anything just give us what you do and
receive.

(Also easiest is usually just do this from the command prompt and
without entering the NSLookup shell.)






.

Relevant Pages

  • Re: Some DNS server names will not resolve using internal servers
    ... I have done all the nslookup commands. ... All of our external ISP DNS ... Is there a trace i could do on the DNS server to tell me what is happening? ...
    (microsoft.public.windows.server.dns)
  • Re: unable to load ONE web site - unknown zone
    ... If you like try setting prompts and see if you at least get a prompt. ... Let's check the DNS because it is the next easiest thing to do ... Open a command window (e.g. Run... ... enter just nslookup ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: Windows 2003 SBS DNS timeouts
    ... I've got a Windows 2003 Small Business Server running a DNS server. ... Usually resolving addresses (e.g. by using a web browser or by using ... try a query using nslookup: ...
    (microsoft.public.windows.server.dns)
  • Re: Can not resolve www.microsoft.com or www.yahoo.com
    ... Same type of search works via nslookup against a fully patched ... Windows 2003 DNS server. ... have also tryed with Netware DNS and it can also resolve. ... a friend of mine at another company also running windows 2003 DNS server ...
    (microsoft.public.windows.server.dns)
  • Re: Can not resolve www.microsoft.com or www.yahoo.com
    ... Same type of search works via nslookup against a fully patched ... Windows 2003 DNS server. ... a friend of mine at another company also running windows 2003 DNS server ...
    (microsoft.public.windows.server.dns)
Loading