On Wed, Oct 06, 1999 at 11:58:31AM -0600, tf wrote: > which is unchanged from when everything worked right. > ah, so that I might avoid sounding stupid, how may I describe what's > happening>to me? can't connect to the name server? > (nslookup reported that... plus "default servers are unavailable") No DNS? > I>don't feel like I'm saying it right...
No dude, I think you are saying right. I know your problem, I am just not sure of the solution. Have you installed any packages lately? If so which ones. Try reconfiguring or reinstalling bind. Try bindconfig and set it up as a caching only nameserver. Also make sure the perms on your /etc/resolv.conf are like this: -rw-r--r-- 1 root root 70 Oct 4 08:08 /etc/resolv.conf Next I would tail -f some various log files, hell try em all while you attempt to get some name service. I must say that I am intruiged what may be the cause. What version of bind are you running. Did you check bugs.debian.org for a possible bug in there. There is twwo parts of bind you know, the client side is called the resolver (herein lies your problem I believe) This is why I say to really eye-fsck bind. Hope this helps. Ben
