Running your own caching resolver is pretty trivial on RHEL/Fedora. Just need to install the caching-nameserver package (which pulls in deps when you use yum to install it). You then need to have: nameserver 127.0.0.1 first in your /etc/resolv.conf file so it gets used. If your computer is directly attached to the cox modem, that'll be a pain as dhcp resets your resolv.conf file. If you're using cox, you really should have a router with nat between your computer and the cox modem though, so your computer isn't sitting on a public address.
I don't know off hand how to set up a local resolver on Ubuntu. I don't really need one myself because my IPCop is my resolver. ;) Brian Cluff wrote: > I've always found that cox's DNS server have been less that desirable. > I was actually surprised to find that I was using their dns at all. > I've usually setup my own, to get around their DNS problems. > > Now with cox hijacking all the typos, I would recommend more than ever > that people setup their own DNS servers. > > Brian Cluff > > On 02/28/2010 07:53 AM, Steven A. DuChene wrote: >> Yes, I am using cox but I guess the bigger question is WHY >> is cox reporting an incorrect IP for the plug web server? >> >> -----Original Message----- >>> From: Brian Cluff<[email protected]> >>> Sent: Feb 28, 2010 1:56 AM >>> To: Main PLUG discussion list<[email protected]> >>> Subject: Re: Installfest this Saturday - PLUG website dead? >>> >>> It looks like the cox name server at 68.105.29.12 is reporting back the >>> wrong address for the plug server. If you simply remove that nameserver >> >from your resolv.conf, you should be able to get to the server again. >>> Brian Cluff >>> -- -Eric 'shubes' --------------------------------------------------- PLUG-discuss mailing list - [email protected] To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
