This one time, at band camp, Jared Pritchard wrote:
>Aug 25 16:32:51 linux01 named[5353]: lame server resolving
>'agreserves.com.au' (in 'agreserves.com.au'?): 203.2.192.124#53
These are mostly harmless and can be ignored, if you want to chuck them out
of the logs totally then the following
logging {
category lame-servers { null; };
};
in named.conf will hush it up.
>Aug 25 16:52:22 linux01 named[5353]: message.c:809: REQUIRE(*rdataset ==
>((void *)0)) failed
>Aug 25 16:52:22 linux01 named[5353]: exiting (due to assertion failure)
I think you have a bad zonefile somewhere.
And you shouldn't need to restart BIND to make any changes, if you have rndc
set up correctly then 'rndc reconfig' to reload any changes to named.conf
and 'rndc reload domain' to reload the zone without interrupting
nameservice.
--
[EMAIL PROTECTED] http://spacepants.org/jaq.gpg
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
