Yes, my test server is listed as a name server for these and other zones
with the relevant NS records in place so that would seem to explain the
behavior. I presume this is an added feature with 9.3 to notify admins of
this behavior since I hadn't seen this prior to now. I will request the
admin of this other server turn notifies off or at least limit them to what
is needed.

Thanks,

Bill

-----Original Message-----
From: bind-users-bounce@isc.org [mailto:bind-users-bounce@isc.org] On Behalf
Of Ronan Flood
Sent: Wednesday, October 13, 2004 9:47 AM
To: comp-protocols-dns-bind@isc.org
Subject: Re: Refused notify from non-master messages

On Tue, 12 Oct 2004 10:15:01 -0400,
"Smith, William E. (Bill), Jr." wrote:

> Since upgrading a test server to 9.3.0, I have begun seeing the
> following messages logged on my server that involve the same host.
> general.log:12-Oct-2004 09:08:24.031 general: info: zone
> _msdcs.jhuapl.edu/IN/internet: refused notify from non-master:
> 128.244.47.217#60673
> general.log:12-Oct-2004 09:15:05.566 general: info: zone
> 244.128.IN-ADDR.ARPA/IN/internet: refused notify from non-master:
> 128.244.47.217#60673
> general.log:12-Oct-2004 09:33:47.530 general: info: zone
> 244.128.IN-ADDR.ARPA/IN/internet: refused notify from non-master:
> 128.244.47.217#60673
> general.log:12-Oct-2004 09:52:54.630 general: info: zone
> 244.128.IN-ADDR.ARPA/IN/internet: refused notify from non-master:
> 128.244.47.217#60673
> notify.log:12-Oct-2004 09:08:24.031 info: client 128.244.47.217#60673:
> view
> internet: received notify for zone '_msdcs.jhuapl.edu'
> notify.log:12-Oct-2004 09:15:05.565 info: client 128.244.47.217#60673:
> view
> internet: received notify for zone '244.128.in-addr.arpa'
> notify.log:12-Oct-2004 09:33:47.530 info: client 128.244.47.217#60673:
> view
> internet: received notify for zone '244.128.in-addr.arpa'
> notify.log:12-Oct-2004 09:52:54.630 info: client 128.244.47.217#60673:
> view
> internet: received notify for zone '244.128.in-addr.arpa'
>
> The host 128.244.47.217 is a DNS also running BIND but it is
> configured to perform its zone transfers from other servers. I
> reviewed the named.conf for this server and saw no references to my
> test server at all. Thus, I'm a little confused as to why this host
> is attempting to send notifies to my server when my test server is not
> configured as its master. It's only an informational message so it's
> obviously not too serious but I would still like to get a better
> understanding of exactly what is going on here and if there is anything I

can do to stop the logging of these messages.

Is your test server listed as a nameserver for the zones _msdcs.jhuapl.edu
and 244.128.in-addr.arpa? Notifies go out to all the nameservers for the
zone, except the primary in the SOA, unless modified by named.conf settings.

--
Ronan Flood
working for but not speaking for
Network Services, University of London Computer Centre
(which means: don't bother ULCC if I've said something you don't like)


-----Original Message-----
From: bind-users-bounce@isc.org [mailto:bind-users-bounce@isc.org] On Behalf
Of Ronan Flood
Sent: Wednesday, October 13, 2004 9:47 AM
To: comp-protocols-dns-bind@isc.org
Subject: Re: Refused notify from non-master messages

On Tue, 12 Oct 2004 10:15:01 -0400,
"Smith, William E. (Bill), Jr." wrote:

> Since upgrading a test server to 9.3.0, I have begun seeing the
> following messages logged on my server that involve the same host.
> general.log:12-Oct-2004 09:08:24.031 general: info: zone
> _msdcs.jhuapl.edu/IN/internet: refused notify from non-master:
> 128.244.47.217#60673
> general.log:12-Oct-2004 09:15:05.566 general: info: zone
> 244.128.IN-ADDR.ARPA/IN/internet: refused notify from non-master:
> 128.244.47.217#60673
> general.log:12-Oct-2004 09:33:47.530 general: info: zone
> 244.128.IN-ADDR.ARPA/IN/internet: refused notify from non-master:
> 128.244.47.217#60673
> general.log:12-Oct-2004 09:52:54.630 general: info: zone
> 244.128.IN-ADDR.ARPA/IN/internet: refused notify from non-master:
> 128.244.47.217#60673
> notify.log:12-Oct-2004 09:08:24.031 info: client 128.244.47.217#60673:
> view
> internet: received notify for zone '_msdcs.jhuapl.edu'
> notify.log:12-Oct-2004 09:15:05.565 info: client 128.244.47.217#60673:
> view
> internet: received notify for zone '244.128.in-addr.arpa'
> notify.log:12-Oct-2004 09:33:47.530 info: client 128.244.47.217#60673:
> view
> internet: received notify for zone '244.128.in-addr.arpa'
> notify.log:12-Oct-2004 09:52:54.630 info: client 128.244.47.217#60673:
> view
> internet: received notify for zone '244.128.in-addr.arpa'
>
> The host 128.244.47.217 is a DNS also running BIND but it is
> configured to perform its zone transfers from other servers. I
> reviewed the named.conf for this server and saw no references to my
> test server at all. Thus, I'm a little confused as to why this host
> is attempting to send notifies to my server when my test server is not
> configured as its master. It's only an informational message so it's
> obviously not too serious but I would still like to get a better
> understanding of exactly what is going on here and if there is anything I

can do to stop the logging of these messages.

Is your test server listed as a nameserver for the zones _msdcs.jhuapl.edu
and 244.128.in-addr.arpa? Notifies go out to all the nameservers for the
zone, except the primary in the SOA, unless modified by named.conf settings.

--
Ronan Flood
working for but not speaking for
Network Services, University of London Computer Centre
(which means: don't bother ULCC if I've said something you don't like)