How to Stop the "unexpected RCODE (SERVFAIL)" Messages?

Stephane Bortzmeyer bortzmeyer at nic.fr
Sat Feb 4 21:12:12 UTC 2006


On Sun, Feb 05, 2006 at 02:13:47AM +0800,
 imacat <imacat at mail.imacat.idv.tw> wrote 
 a message of 44 lines which said:

> imacat at rinse ~ % grep 'unexpected RCODE (SERVFAIL)' /var/log/messages |
> grep '^Feb  4 21:'
> Feb  4 21:00:32 rinse named[2037]: unexpected RCODE (SERVFAIL) resolving
> '194.183.255.216.in-addr.arpa/PTR/IN': 127.0.0.1#50053
...
> My syslog file is growing up enormously,
> and I feel the life-span of my root harddisk shortened on every scratch. 

Reading the source code of BIND (because I cannot find it in the
documentation), it seems that this message is logged in the category
"lame-servers". So, adding:

logging {
        ...
        category lame-servers { null; };

should be enough (I never understood that category, anyway, since I
don't care in errors in other domains, there are much too common).

You can read the BIND ARM to learn more about categories and
logging. See chapter "logging Statement Grammar", which includes a
table of available categories.



More information about the bind-users mailing list