Re: Remote Desktop and VPN issues

On 9/8/05, Jones, John (US) <John.Jones@xxxxxxxxxx> wrote:
> 
> Yeah, OK your way out back to the Network Connections panel.
> 
> What this is doing is replacing the ISP-assigned DNS with a different
> one (unless, of course, Verizon IS your ISP). When you look for
> google.com <http://google.com> or any other site, the DNS is used to 
> change that name into
> the IP address. It would seem like your DNS (your ISP's DNS) is failing
> intermittently. This would be a way of confirming that by using a
> different DNS.
> 
> BTW, it is possible that your PC will default to using your router as a
> DNS and your router is forwarding the requests to your ISP's DNS. This
> should be fine, and if desired you can double-check the ISP's DNS entry
> on the router.
> 
> If the ability to resolve addresses is stable while using the Verizon
> DNS and becomes unstable if you go back in the settings and change it
> back to "Obtain DNS server address automatically", then you may want to
> talk to your ISP about their DNS being flaky.


Wow, I've got a lot to learn. Good stuff, John.

At the risk of exposing my ignorance, in lieu of hard-coding DNS entries, 
would not a functionally equivalent test be to use the IP address of a 
website I am trying to reach? If I know that
www.dan.net<http://www.dan.net>is at
44.55.66.77 <http://44.55.66.77>, and www.dan.net
<http://www.dan.net>"cannot be found", and
44.55.66.77 <http://44.55.66.77> does get me to the website, would that be 
proof of the ISP's "DNS being flaky"?