Suppressing duplicate notify

[Henri J. Schlereth]

> 
> Your named.conf is not quite right. In BIND, the master name server
> sends NOTIFY messages to the IP addresses of the zone's NS records.
> [NS records should exist for most (all?) of the authoritative name
> servers for the zone: not only its master server.] So if your
> named.conf has also-notify clauses, these could be redundant. The name
> server already knows from the zone's NS records who it needs to
> NOTIFY. It would be better to keep the zone's NS records and remove
> the (unnecessary) also-notify clauses rather than the other way
> round. 
I dont have any also notify clauses in named.conf (see below)

named.conf (bind 8.2.2.P5)

// generated by named-bootconf.pl

options {
	directory "/var/named";
	version "Surely you must be joking";
	/*
	 * If there is a firewall between you and nameservers you want
	 * to talk to, you might need to uncomment the query-source
	 * directive below.  Previous versions of BIND always asked
	 * questions using port 53, but BIND 8.1 uses an unprivileged
	 * port by default.
	 */
	// query-source address * port 53;
};

// 
// Official and stealth secondaries 
// 
acl "neandertal-xfer" {
	{ 192.168.1.4;	// shonjir.neandertal.org (slave)
	};
};


zone "." {
	type hint;
	file "named.ca";
};

zone "0.0.127.in-addr.arpa" {
	type master;
	file "primary/0.0.127.in-addr.arpa";
};

zone "1.168.192.in-addr.arpa" {
	type master;
	file "primary/1.168.192.in-addr.arpa";
	allow-query {
		any;
	};
	allow-transfer {
	localhost;
	neandertal-xfer;
	};
};

zone "neandertal.org" {
	type master;
	file "primary/neandertal.org";
  	allow-query {
		any; 
};
	allow-transfer {
	localhost;
	neandertal-xfer;
	};
};

Henri

-- 
-------------------------------------------------------------
"All data leaves a trail. The search for data leaves a trail.
The erasure of data leaves a trail.The absence of data, under
the right circumstances,can leave the clearest trail of all-
Dr. Kio Masada" 
-------------------------------------------------------------