I second that you're probably better off running a local resolver box, it's
easy to do and saves you from having to be at other's mercy when their dns
dies.  Using that 68.1.17.7 address I wouldn't rely on as I don't think it's
official function is as a dns box, someone probably just screwed up and left
bind bound to a public interface or didn't plug a hole in the firewall.  Use
206.157.231.13 if you have to (ns1.coxmail.com) as a tertiary, it's the tld
roots for most of cox's domains and about most reliable of all the dns
boxen.

-mbutash

-----Original Message-----
From: plug-discuss-admin@lists.plug.phoenix.az.us
[mailto:plug-discuss-admin@lists.plug.phoenix.az.us]On Behalf Of Craig
White
Sent: Monday, March 18, 2002 5:43 AM
To: plug-discuss@lists.plug.phoenix.az.us
Subject: Re: Cox and DNS server


On Mon, 2002-03-18 at 01:31, Carl Parrish wrote:
> Okay I don't know what's wrong with cox  but I'm having dns problems
> (again). does anyone have the ip address of a *reliable* DNS server I
> can use for a bit?
>
----
I find that it often helps to run your own caching dns when using cox.

you would have to install bind - make sure that it only listens on the
internal lan - and you don't need anyone else's dns except root/TLD and
if you ain't got that - you are dead in the water anyway.

Craig
________________________________________________
See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post
to the list quickly and you use Netscape to write mail.

PLUG-discuss mailing list  -  PLUG-discuss@lists.plug.phoenix.az.us
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss