rcconf provided partial solution maradns process no longer starts

[Remco Rijnders]

> I dug around and figured out that the tool I needed to stop the maradns
> autostart was either rcconf or sysv-rc-conf. So, I installed rcconf and
> ran
> it and have now stopped maradns from autostarting. However, I'm still
> having
> trouble because ether the install of maradns or something else seems to
> have
> locked down port 53 so that it shows as "in use" when any process tries to
> access it. As a result, I can no longer start maradns manually.
>
> All I'm trying to do is get back to where I can run the process manually
> and
> stop and restart it easily while I'm testing the darn thing.
>
> Any suggestions about how I can get back to that point would be VERY MUCH
> appreciated!

I think it is the maradns zoneserver (aptly called zoneserver) which is
hanging on to port 53. You may wish to stop the zoneserver permanently as
you don't need it unless you want to run a 'slave' server on another
machine. You can use a command like '/etc/rc2.d/S20zoneserver stop' for
that on your debian machine to stop the current running zoneserver
process. Similary, on your debian box you can also issue
'/etc/rc2.d/S20maradns stop' to stop maradns, or use the argument start or
restart to kick mara back up again.

Kind regards,

Remco