In article <[EMAIL PROTECTED]>, Arnt Karlsen wrote: >> > When I start Bind from '/etc/init.d/bind9 start', everything looks >> > fine, like nothing wrong. But I found out that Bind acctually not >> > working properly. /etc/init.d/bind9 reload/restart will give this >> > error message: >> > >> > Stopping domain name service: named >> > rndc: connect failed: connection refused > > ..I've seen these too. ;-) > >> The magic is in /etc/bind/rndc.conf (and the corresponding key >> in /etc/bind/named.conf). >> >> Create the magic using rndc-confgen. >> >> In my case, lwresd was somehow installed, messing up the >> communication. > > ..how???
How was lwresd installed? I don't know. Maybe from first install, maybe it was pulled in with some other package. How did lwresd mess up the communication between rndc and named(bind9)? Apparently, lwresd was listening on port 953, so that named couldn't bind on that port (and thus rndc could not communicate to named). >> Removing lwresd (and kill-ing the process that stayed on even after I >> removed the package) solved it. > > ..in my case, this took 3 minutes and 9 to 25 seconds What took 3 minutes? >, lwresd on or off > made at best a 2 second difference _if_ it mattered, and I'm not sure of > that. I guess it depends on who was started first, lwresd or named. If named is started first, it will listen on port 953, and then everything should work OK. As I don't know why I would want to have lwresd, I just removed it. I should file a bugreport against one of the packages, but don't do that now, as I don't have time to investigate what package is wrong etc. -- joostje -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
