Re: DNS across a WAN
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Tue, 18 Apr 2006 14:28:45 -0500
<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!
.
- References:
- DNS across a WAN
- From: kavedweller_68
- Re: DNS across a WAN
- From: Herb Martin
- Re: DNS across a WAN
- From: kavedweller_68
- Re: DNS across a WAN
- From: kavedweller_68
- DNS across a WAN
- Prev by Date: Re: Moving DNS from Windows 2000 to Windows 2003
- Next by Date: Re: DNS across a WAN
- Previous by thread: Re: DNS across a WAN
- Next by thread: Re: DNS across a WAN
- Index(es):
Relevant Pages
|