Re: DNS across a WAN



<kavedweller_68@xxxxxxxxx> wrote in message
news:1145385906.854313.163410@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hey Herb, this is what i get when i try various tests.

When i do ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : WENDY
Primary Dns Suffix . . . . . . . :

Not part of your MAIN problem but I would like to
see you set a DNS Domain name for this machine in
your SYSTEM CONTROL PANEL where you name
the machine....

Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connecti
on
Physical Address. . . . . . . . . : 00-13-20-CC-7F-E2
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.1.44
Primary WINS Server . . . . . . . : 192.168.1.44

When i try to nslookup the ip address i get
nslookup 192.168.1.44

The above is a request for a REVERSE lookup (IP to Name)
and likely doesn't prove anything to you right now.

You instead wish to check if you can LOOKUP a NAME to
an IP address.

AND THEN you might want to make an explicit request OF
THIS DNS server (that address is also your DNS server.)

nslookup Some.Name.YouExpect.ToWork 192.168.1.44

DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.1.44: Timed out
*** Default servers are not available

The error above is perfectly normal -- it is due to an artifact
of the way NSLookup works. It's bogus and you can ignore the
PART ABOVE as long as your real request gets and answer:


When i try nslookup by name

nslookup xxx.yyy.com

Try a specific DNS server for a name you KNOW it
will be able to resolve....

Server: UnKnown
Address: 192.168.1.44

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

When i ping the ip address
ping 192.168.1.44

Pinging 192.168.1.44 with 32 bytes of data:

Reply from 192.168.1.44: bytes=32 time=4ms TTL=125

At least (limited) routing is working.

Is 192.168.1.44 REALLY a DNS server?

Does it have any Zones?

Can it forward or otherwise resolve the Internet?

You can run the NSlookup commands from the console
of the DNS server (192.168.1.44) too -- prove that it is
WORKING as a DNS server, then prove the clients can
ask it questions and get answers etc.

Simplify and isolate the problem one level at a time.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]




Hope this helps!

Thanks!



.



Relevant Pages

  • Re: DNS and name resolution issues
    ... I forgot to add that I can ping if I use the FQDN of the host I am trying to ... can I resolve the name to an IP address using NSLOOKUP. ... NSLOOKUP and point it to the DNS server on 10.4.x.x and I get the results ...
    (microsoft.public.windows.server.dns)
  • Re: Round Robin DNS behaving strangely.
    ... Did you check the netmask ordering on the dns server advanced tab? ... BTW - /displaydns will only show what is in the local client cache - so you ... Utils like ping use the local cache, ... behavior is dig or nslookup as they do not use local cache. ...
    (microsoft.public.windows.server.dns)
  • 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: DNS Problems I think?
    ... > I could instantly see the site and an nslookup resolved the new IP but this ... > work but the I restarted the DNS server and I have some success. ... If I now ping www.domain.com I get the old IP and if I ping domain.com I get ... Keith ...
    (microsoft.public.windows.server.dns)
  • Re: Outlook 2003 wont verify Exchange account
    ... Interestingly enough..I ran nslookup on the machine and I did get an error. ... I found that my DNS server was configured a little strangely. ... If you open the 'Network Connections' folder then select the ... > The web has plenty of info for using this command as its not a Microsoft ...
    (microsoft.public.exchange.admin)