David <[EMAIL PROTECTED]> writes: > listening on 953. I've changed the named.conf and rndc.conf files as shown > below, but obviously that isn't effective for the daemon that is already > running.
Agreed. > does this mean that I should kill named, then restart it? That doesn't > seem to make much sense to me, but at the moment I'm not seeing an > alternative. Neither the init script or rndc will let me stop named. I think you're going to have to kill named. Theoretically everything will keep on working if the slaves are working OK. Just a guess at what is happening (too bad google doesn't know the difference). When named starts it reads the rndc key, you need that key to control named, to get it to reread its config, for example. If you change the key on the disk, as you've said, it won't affect the running named. It will stop you from being able to control named, though, because the key named loaded at startup, and the key on the disk that the rndc binary uses don't match any more. If it still doesn't work after a kill and restart, I don't know. -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
