MaraDNS now runs automatically on reboot but always times out...

[Sam Trenholme]

> Since I was suddenly getting this error, I eventually discovered maradns was
> now starting automatically and was already running as a resident process
> (therefore, it had port 53 tied up). AFAIK, I had done nothing specific to
> make the auto-start of maradns happen. It just happened.

MaraDNS startup is very system-specific.  MaraDNS, when one does a
"make install", adds files to /etc/rc.d/init.d, and, as I recall,
/etc/rc.d/rc3.d and /etc/rc.d/rc5.d.  This is how RedHat and CentOS do
things.  However, in the tradition of doing things differently just
for the sake of being different, each Linux and *BSD version has it
own ways of determining how a program is started up at system boot.
So, which version of *NIX are you using?

Looking at the LSB, it appears that if your distribution is LSB
compliant, that init scripts are in /etc/init.d [1].  So, look in
/etc/init.d.  If your version of *NIX doesn't have an /etc/init.d
directory, well I can't help you but maybe the guys who make your
Linux or *BSD distribution know what to do.

- Sam

[1] http://refspecs.linux-foundation.org/LSB_3.2.0/LSB-Core-generic/LSB-Core-generic/initsrcinstrm.html

Note: If you send me a MaraDNS-related support question, I reserve the
right to post your support email to the Mara-DNS mailing list so that
the community at large can examine your issue. MaraDNS security
vulnerability reports, however, will be kept confidential.  No,
MaraDNS is not vulnerable to the "new" cache poisoning attack, and was
never vulnerable.