try manually setting a DNS: run nslookup enter: server some.server.name (feel free to use mine ns1.firetrail.com or ns2.firetrail.com) then enter a domain or ip or something to query the server
if it times out it is more likely a network problem then a resolver problem. if it works, then try your other setup again(again by manually changing servers using the 'server' command) if it does not work make sure you can reach the server by using ping or traceroute(or both) hopefully it is not firewalled so you can diagnose it . nate On Wed, 22 Mar 2000, Guyren G Howe wrote: guyren >I have somehow managed to get things so that the computers going through my guyren >Debian 2.2 box for NAT can do DNS just fine, but I can't do a nslookup from guyren >the same box itself to save myself. guyren > guyren >nslookup never returns anything, even a timeout. My /etc/resolv.conf file guyren >shows the same things I have set on the other computers that work fine guyren >through my linux box. guyren > guyren >What could I have got wrong? guyren > guyren >TIA guyren > guyren > guyren >-- guyren >Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null guyren > ----------------------------------------[mailto:[EMAIL PROTECTED] ]-- Vice President Network Operations http://www.firetrail.com/ Firetrail Internet Services Limited http://www.aphroland.org/ Everett, WA 425-348-7336 http://www.linuxpowered.net/ Powered By: http://comedy.aphroland.org/ Debian 2.1 Linux 2.0.36 SMP http://yahoo.aphroland.org/ -----------------------------------------[mailto:[EMAIL PROTECTED] ]-- 3:09pm up 215 days, 3:42, 1 user, load average: 1.03, 1.11, 1.08
