Or maybe not.....Here's what's happening. - I set up bind on my LM8.1 box as a caching nameserver - I issue the command "dig -x 127.0.0.1" and hit return. In a moment it comes back with a message that indicates that named is working correctly. - I issue the command "dig blahblahblah.com" and in a moment it comes back to tell me that it can't find any servers. I think it's having a problem with my firewall, but I can sort that out later (that is not my problem right now) - I make various changes to /etc/hosts, /etc/hosts.conf, /etc/resolv.conf, each time using the Mandrake Control Center to stop and start named. - Here's my problem......after stopping and starting named this way 4 or 5 time, it starts to tell me that it can't stop bind, but it still says it's OK when it starts it again. If I look for named with top or ps -A, it is not there, yet the Control Center and the SysV editor both report that it is running. If I use the SysV editor to stop and start named, I get the same wierd behaviour. Once this starts happening "dig -x 127.0.0.1" no longer works, and instead tells me that it can't find the server. So it looks like using the Mandrake Control Center to stop and start named eventually kills it, so that some how the system thinks it's still running even though it's not......Or maybe I'm an idiot..... I have checked the logs and found that indeed it fails when trying to stop named, ummmm, upgraded bind, rebooted, sacrificed gerbils...... Any hints or guesses would be appreciated.
Doug Gough Pacific Academy
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
