Suppressing duplicate notify
Tilman Schmidt
Tilman.Schmidt at sema.de
Fri Mar 3 10:24:58 UTC 2000
At 19:52 02.03.00 +0000, Jim Reid wrote:
>have helped if you'd provided the relevant information - like the zone
>file and named.conf - at the outset. If you're still getting warnings
>about duplicate NOTIFYs, then you must have a duplicate NS record. Or
>different NS records that have names pointing at the same IP address.
I am getting that message too since my upgrade to BIND 8.2.2-P5 and have
never been able to find out why. I had already resigned to just ignoring
it, but following this discussion has revived my curiosity. This is what
BIND gave me last time it was restarted:
--------8<--------8<--------8<--------8<--------8<--------8<--------8<--------
Feb 23 11:51:28 igate named[332]: starting. named 8.2.2-P5 Thu Dec 2 09:49:55 MET 1999 ^Its at igate:/usr/local/src/bind-8.2.2-P5/src/bin/named
Feb 23 11:51:28 igate named[332]: hint zone "" (IN) loaded (serial 0)
Feb 23 11:51:28 igate named[332]: master zone "localhost" (IN) loaded (serial 1999010401)
Feb 23 11:51:28 igate named[332]: master zone "0.0.127.in-addr.arpa" (IN) loaded (serial 1999010401)
[...]
Feb 23 11:51:28 igate named[332]: master zone "sema.de" (IN) loaded (serial 1999122201)
Feb 23 11:51:28 igate named[332]: master zone "semagroup.de" (IN) loaded (serial 1999092003)
Feb 23 11:51:28 igate named[332]: slave zone "sgbs.sema.de" (IN) loaded (serial 2000012800)
Feb 23 11:51:28 igate named[332]: slave zone "sgo.sema.de" (IN) loaded (serial 2000012800)
Feb 23 11:51:28 igate named[332]: slave zone "sgbs.semagroup.de" (IN) loaded (serial 2000012800)
Feb 23 11:51:28 igate named[332]: slave zone "sgo.semagroup.de" (IN) loaded (serial 2000012800)
[...]
Feb 23 11:51:28 igate named[332]: listening on [127.0.0.1].53 (lo)
Feb 23 11:51:28 igate named[332]: listening on [192.168.70.2].53 (eth0)
Feb 23 11:51:28 igate named[332]: listening on [194.123.157.114].53 (eth1)
Feb 23 11:51:28 igate named[332]: Forwarding source address is [0.0.0.0].1025
Feb 23 11:51:28 igate named[333]: Ready to answer queries.
Feb 23 11:51:34 igate named[333]: suppressing duplicate notify ("semagroup.de" IN SOA)
Feb 23 11:51:41 igate named[333]: Sent NOTIFY for "sema.de IN SOA" (sema.de); 2 NS, 2 A
Feb 23 11:51:41 igate named[333]: Received NOTIFY answer from 193.141.40.1 for "sema.de IN SOA"
Feb 23 11:51:41 igate named[333]: Received NOTIFY answer from 194.120.12.245 for "sema.de IN SOA"
[...]
Feb 23 11:51:57 igate named[333]: Sent NOTIFY for "semagroup.de IN SOA" (semagroup.de); 2 NS, 2 A
Feb 23 11:51:57 igate named[333]: Received NOTIFY answer from 194.120.12.245 for "semagroup.de IN SOA"
Feb 23 11:51:57 igate named[333]: Received NOTIFY answer from 193.141.40.1 for "semagroup.de IN SOA"
-------->8-------->8-------->8-------->8-------->8-------->8-------->8--------
It doesn't appear at every restart, and if it appears it's not always for
the same zone, even if the zone and configuration files haven't changed,
so I am really confused here. It also never happens on "ndc reload", only
on complete restarts, which are of course rather rare, so I have only
had three occurrences so far: two for my zone 112-127.157.123.194.in-addr.arpa
and the one above for zone semagroup.de.
Here's the relevant part of my named.conf:
--------8<--------8<--------8<--------8<--------8<--------8<--------8<--------
// local nets -- may query and transfer anything
acl "local" {
localhost;
10.0.0.0/8;
172.16.0.0/12;
192.168.0.0/16;
194.123.157.112/28;
};
// DE Hostcount server -- may transfer all zones
acl "hostcounter" {
129.70.132.4;
};
// Berechtigung zum Zonentransfer von unseren Primary Zones
acl "master-xferers" {
local;
hostcounter;
// secondary nameservers
193.141.40.1;
193.141.40.41; // ??
194.120.12.245;
};
// Berechtigung zum Zonentransfer von Zonen, für die wir Secondary sind
acl "slave-xferers" {
local;
hostcounter;
};
options {
directory "/var/named";
allow-query { local; };
allow-transfer { local; };
};
//
// Root Domain Bootstrap Cache
//
zone "." {
type hint;
file "named.root";
};
[...]
//
// Forward Mapping fuer sema.de und semagroup.de
//
zone "sema.de" {
type master;
file "sema.de";
allow-query { any; };
allow-transfer { master-xferers; };
};
zone "semagroup.de" {
type master;
file "semagroup.de";
allow-query { any; };
allow-transfer { master-xferers; };
};
//
// delegierte Subdomains, fuer die wir Secondary sind
//
zone "sgbs.sema.de" {
type slave;
file "slave/sgbs.sema.de";
masters { 62.157.188.114; };
allow-query { any; };
allow-transfer { slave-xferers; };
};
zone "sgo.sema.de" {
type slave;
file "slave/sgo.sema.de";
masters { 62.157.188.114; };
allow-query { any; };
allow-transfer { slave-xferers; };
};
zone "sgbs.semagroup.de" {
type slave;
file "slave/sgbs.semagroup.de";
masters { 62.157.188.114; };
allow-query { any; };
allow-transfer { slave-xferers; };
};
zone "sgo.semagroup.de" {
type slave;
file "slave/sgo.semagroup.de";
masters { 62.157.188.114; };
allow-query { any; };
allow-transfer { slave-xferers; };
};
//
// Reverse Mapping fuer 194.123.157.112/28
//
zone "112-127.157.123.194.in-addr.arpa" {
type master;
file "P194.123.157.112-127";
allow-query { any; };
allow-transfer { master-xferers; };
};
-------->8-------->8-------->8-------->8-------->8-------->8-------->8--------
And here, just for the record, the semagroup.de zone file as of the last
restart:
--------8<--------8<--------8<--------8<--------8<--------8<--------8<--------
$ORIGIN semagroup.de.
$TTL 1w
;
@ IN SOA ns.sema.de. hostmaster.sema.de. (
1999092003 ; Serial YYYYMMDDnn
86400 ; Refresh 24 Stunden
7200 ; Retry 2 Stunden
604800 ; Expire 7 Tage
86400 ) ; min. TTL 1 Tag
;
IN NS ns.sema.de.
IN NS koeln.nic.xlink.net.
IN NS Xlink1.xlink.net.
IN MX 10 mail.sema.de.
IN MX 200 relay.xlink.net.
;
www IN A 194.64.40.55
IN MX 10 mail.sema.de.
IN MX 200 relay.xlink.net.
;
www.ts IN A 194.64.40.63
IN MX 10 mail.sema.de.
IN MX 200 relay.xlink.net.
;
wswg IN CNAME www ; WSWG-FTP-Server
;
cgtec IN NS ns.cgtec.sema.de.
;
sgbs IN NS dns.sgbs.sema.de.
IN NS ns.sema.de.
sgo IN NS dns.sgbs.sema.de.
IN NS ns.sema.de.
;
so IN MX 200 hermes.btu.de.
*.so IN MX 200 hermes.btu.de.
www.so IN A 194.64.40.62
-------->8-------->8-------->8-------->8-------->8-------->8-------->8--------
Any ideas?
--
Tilman Schmidt E-Mail: Tilman.Schmidt at sema.de (office)
Sema Group Koeln, Germany tilman at schmidt.bn.uunet.de (private)
More information about the bind-users
mailing list