Am running FBSD-4.5 with named 8.2.4-REL Every time there is a mailing to one of the larger majordomo mail lists, its seems that the named daemon breaks. It only happens when this list goes out 2 or 3 times a month. If I kill named and restart so it re-reads the named.conf, it fixes the problem for a while during the process. But, it breaks again usually before the list send process completes (several thousand on the list). A stop/restart of named again fixes it again and don't have the problem show up until the list is used for another broadcast.
I wonder if anyone could suggest a fix on this?? Here's a sample of the errors, which is a partial list: Jul 14 14:00:13 sage-one named[22098]: sysquery: no addrs found for root NS (ns) Jul 14 14:00:14 sage-one named[22098]: sysquery: no addrs found for root NS () Jul 14 14:00:16 sage-one named[22098]: sysquery: no addrs found for root NS (ns) Jul 14 14:00:16 sage-one named[22098]: sysquery: no addrs found for root NS () Jul 14 14:00:19 sage-one named[22098]: sysquery: no addrs found for root NS (ns) Jul 14 14:00:19 sage-one named[22098]: sysquery: no addrs found for root NS () Jul 14 14:00:58 sage-one named[22098]: sysquery: no addrs found for root NS (ns) Jul 14 14:00:58 sage-one named[22098]: sysquery: no addrs found for root NS () Jul 14 14:00:59 sage-one named[22098]: sysquery: no addrs found for root NS (ns) Jul 14 14:01:00 sage-one named[22098]: sysquery: no addrs found for root NS () Jul 14 14:01:04 sage-one named[22098]: sysquery: no addrs found for root NS (ns) Jul 14 14:01:04 sage-one named[22098]: sysquery: no addrs found for root NS () Jul 14 14:01:06 sage-one named[22098]: sysquery: no addrs found for root NS (nimble.mta.ca) Jul 14 14:01:06 sage-one named[22098]: sysquery: no addrs found for root NS (owl.nstn.ca) Jul 14 14:01:06 sage-one named[22098]: sysquery: no addrs found for root NS () Jul 14 14:01:06 sage-one named[22098]: sysquery: no addrs found for root NS (ns) Jul 14 14:01:06 sage-one named[22098]: sysquery: no addrs found for root NS () Jul 14 14:01:07 sage-one named[22098]: sysquery: no addrs found for root NS (pktradio.mohawkc.on.ca) Jul 14 14:01:07 sage-one named[22098]: sysquery: no addrs found for root NS () Jul 14 14:01:10 sage-one named[22098]: sysquery: no addrs found for root NS (ns) Jul 14 14:01:10 sage-one named[22098]: sysquery: no addrs found for root NS () Jul 14 14:01:14 sage-one named[22098]: sysquery: no addrs found for root NS (nimble.mta.ca) Jul 14 14:01:14 sage-one named[22098]: sysquery: no addrs found for root NS (owl.nstn.ca) Jul 14 14:01:14 sage-one named[22098]: sysquery: no addrs found for root NS () Jul 14 14:01:14 sage-one named[22098]: sysquery: no addrs found for root NS (ns) Jul 14 14:01:14 sage-one named[22098]: sysquery: no addrs found for root NS () Jul 14 14:01:15 sage-one named[22098]: sysquery: no addrs found for root NS (pktradio.mohawkc.on.ca) Jul 14 14:01:15 sage-one named[22098]: sysquery: no addrs found for root NS () etc, etc...... Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
