Setting up your own caching nameserver is the best bet, but when you *do* have access, you grab a list of IP's for some of the "common" local domains' DNS (dare I say, efn.org, uoregon.edu, etc) which you can use. Find out about the 'dig' or 'whois' commands for easy ways to pull the nameservers -- when you *do* have access, that is. If you need quick access, EFN/OPN could oblige if you can drop by, or the Eugene Public Library, or one of the quiet UO computer labs... best of luck!
Ben PS - I think you'll find mention of caching DNS proxies in the list archives, or enjoy the docs at http://tldp.org On Wed, 20 Aug 2003 08:03:20 -0700 (PDT) Dave Wyatt <[EMAIL PROTECTED]> wrote: | It seems my ISPs' nameserver(s) were down yesterday | until after 3PM so I could only access the sites for | which I knew the IP address. Needless to say, I | didn't know too many so my surffing was very limited | yesterday. | | Any suggestions for public nameservers to use in such | a situation? Would it be too difficult for an | inexperienced Linux user to set up a local nameserver | or caching-only nameserver for just my computer(s)? | And if so, would that be any help if the situation | happened again. | _______________________________________________ EuG-LUG mailing list [EMAIL PROTECTED] http://mailman.efn.org/cgi-bin/listinfo/eug-lug
