Re: DNS across a WAN
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Tue, 18 Apr 2006 14:11:23 -0500
<kavedweller_68@xxxxxxxxx> wrote in message
news:1145382404.961677.36490@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Herb and thanks for the quick reply!
The Site2 machines are only using the Site1 DNS server (192.168.1.44)
as their DNS server when performing the test. I just thought i would
throw out there the fact that the T1 connection is apparently good
because if i do put the address of a public IP server such as 4.2.2.2,
they can reach the internet.
I can ping back and forth between the two sites and ping the server
from Site2 with no problem. I will try what you suggest from Site2 in
a bit.
Technically Ping proves that ICMP works (is routable etc.)
so using the EXPLICIT NSLookup command you can
determine if something might be blocking the ports and
protocols used by DNS (Port 53 UDP and TCP).
Since you can ping, you have pretty good confidence in
routing.
If NSLookup works, I would SERIOUSLY go recheck the
address you have configured for the DNS and make sure
there isn't some silly typo.
If you can route, and if more explicitly you can resolve using
NSlookup then you pretty much HAVE to be able to resolve
DNS in general if you use STRICTLY that same DNS Server
(set).
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
Thanks
.
- Follow-Ups:
- Re: DNS across a WAN
- From: kavedweller_68
- Re: DNS across a WAN
- From: kavedweller_68
- Re: DNS across a WAN
- References:
- DNS across a WAN
- From: kavedweller_68
- Re: DNS across a WAN
- From: Herb Martin
- Re: DNS across a WAN
- From: kavedweller_68
- DNS across a WAN
- Prev by Date: Re: DNS forwarders
- Next by Date: Re: Windows 2003 DNS Design Question
- Previous by thread: Re: DNS across a WAN
- Next by thread: Re: DNS across a WAN
- Index(es):
Relevant Pages
|