Robert Canary <[EMAIL PROTECTED]> wrote:
>Still getting this damn things :-)
>Any ideas why?
>Dec 5 22:20:04 mchn3 named[1612]: Sent NOTIFY for "6.32.208.in-addr.arpa
IN SOA"
>(6.32.208.in-addr.arpa); 1 NS, 1 A
If you're running bind 8 this is normal. Anytime you restart named after
making a change it sends a notify to any other DNS servers it finds in your
zone(s) to let them know there's been a change. This allows updates to
happen right away instead of using the refresh value in the SOA record.
The "1 NS" indicates the notify message was sent to 1 other DNS server.
>Dec 5 22:20:09 mchn3 named[1612]: sysquery: sendto([0.0.104.81].53):
Invalid argument
>
>Dec 5 22:20:09 mchn3 named[1612]: sysquery: sendto([0.0.136.81].53):
Invalid argument
Haven't seen this message for awhile - are you running the latest version
of bind?
-Eric
Eric Sisler
Library Computer Technician
Westminster Public Library
Westminster, CO, USA
[EMAIL PROTECTED]
Linux - don't fear the Penguin.
Want to know what we use Linux for?
Visit http://gromit.westminster.lib.co.us/linux
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
