Notifys are sent by default for all loaded zones. They go only to the
nameservers listed in the zonefile unless overridden with 'also-notify'
statements in the zone clause in named.conf.
Notify behavior is also tunable using several named.conf options
statements.
I'd recommend checking the BIND9 ARM (esp. section 4.1) for a more
extensive explanation.
On Tue, 2011-04-12 at 07:24 -0400, hugo hugoo wrote:
> Dear all,
>
> I would appreciate if someone can explain me why a notify is present
> on my logs (bind9) for a master zone:
>
>
>
> zone fbtest07.be/IN: loaded serial ==> zone loades after a
> reload
>
>
>
> fbtest07.be/IN: sending notifies (serial 8) ==> notify sent (but
> what is the destination?)
>
>
>
>
>
> Thanks in advance for your feedback,
>
>
>
> Hugo,
>
>
>
>
>
> Zone file
>
>
>
>
>
> $TTL 3600 ;Positive Caching
>
> fbtest07.be. 3600 IN SOA ns1.skynet.be. dnsmaster.skynet.be.
> (
>
> 8 ; Serial
>
> 10800 ; Refresh
>
> 3600 ; Retry
>
> 3600000 ; Expire
>
> 3600 ) ; Negative Caching
>
>
>
> fbtest07.be. 3600 IN NS ns.uat.
>
> ftp.fbtest07.be. 3600 IN A 3.3.3.7 ; ftp
>
>
>
>
>
>
>
> Includ file named.zones.inc (see named.conf)
>
>
>
>
>
> zone "fbtest07.be" {
>
> type master;
>
> file "/etc/bind/zones/master/fbtest07.be";
>
> };
>
>
>
>
>
> named.conf
>
>
>
> lennydnstest01:~# cat /etc/bind/named.conf
>
> // This is the primary configuration file for the BIND DNS server
> named.
>
> //
>
> // Please read /usr/share/doc/bind9/README.Debian.gz for information
> on the
>
> // structure of BIND configuration files in Debian, *BEFORE* you
> customize
>
> // this configuration file.
>
> //
>
> // If you are just adding zones, please do that
> in /etc/bind/named.conf.local
>
>
>
> //include "/etc/bind/named.conf.options";
>
> acl myself {
>
> 127/9;
>
> };
>
>
>
>
>
> options {
>
> directory "/var/cache/bind";
>
> listen-on {
>
> 127.0.0.1;
>
> 194.78.73.24;
>
> };
>
> allow-transfer {
>
> myself;
>
> };
>
> recursion no;
>
> //fetch-glue no;
>
> };
>
>
>
> logging {
>
> channel my_debug {
>
> file "named.run";
>
> severity dynamic;
>
> print-time yes;
>
> };
>
> category default { default_syslog; my_debug; };
>
> category config { default_syslog; my_debug; };
>
> //category parser { default_syslog; my_debug; };
>
> category queries { my_debug; };
>
> category lame-servers { default_syslog; my_debug; };
>
> //category statistics { default_syslog; my_debug; };
>
> //category panic { default_syslog; my_debug; };
>
> category update { default_syslog; my_debug; };
>
> //category ncache { default_syslog; my_debug; };
>
> category xfer-in { default_syslog; my_debug; };
>
> category xfer-out { default_syslog; my_debug; };
>
> //category db { default_syslog; my_debug; };
>
> //category eventlib { my_debug; };
>
> //category packet { my_debug; };
>
> category notify { default_syslog; my_debug; };
>
> //category cname { default_syslog; my_debug; };
>
> category security { default_syslog; my_debug; };
>
> //category os { default_syslog; my_debug; };
>
> //category insist { default_syslog; my_debug; };
>
> //category maintenance { default_syslog; my_debug; };
>
> //category load { default_syslog; my_debug; };
>
> //category response-checks { default_syslog; my_debug; };
>
> };
>
>
>
>
>
> // prime the server with knowledge of the root servers
>
> zone "." {
>
> type hint;
>
> file "/etc/bind/db.root";
>
> };
>
>
>
> // be authoritative for the localhost forward and reverse zones, and
> for
>
> // broadcast zones as per RFC 1912
>
>
>
> zone "localhost" {
>
> type master;
>
> file "/etc/bind/db.local";
>
> };
>
>
>
> zone "127.in-addr.arpa" {
>
> type master;
>
> file "/etc/bind/db.127";
>
> };
>
>
>
> zone "0.in-addr.arpa" {
>
> type master;
>
> file "/etc/bind/db.0";
>
> };
>
>
>
> zone "255.in-addr.arpa" {
>
> type master;
>
> file "/etc/bind/db.255";
>
> };
>
>
>
> ////add entries for other zones
>
>
>
> include "/etc/bind/conf/named.zones.inc";
>
>
>
>
>
>
>
>
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
