strange error when receiving NOTIFY

[Rob Egan]

I'm only saying they're correct because they match entries that we have for
hundreds of other domains that don't experience this error. But since I
can't explain the error and everyone agrees it has to be a conf error,
here's the truncated named.conf files (sorry I was lazy in my first
posting):

In the below text, I changed the domain in question to "mydomain.com" and I
changed the primary IP address to 1.2.3.4 and secondary to 5.6.7.8. Other
info about the servers, they run BIND 8.2.2-p5 over Linux (RedHat 6.2). The
are configured to run as a non-root user in a chrooted filesystem. And,if
you do a "whois mydomain.com" the correct nameservers come up.

Can anybody see any errors, or options that I may have left out?
anks!   -Rob

Primary server's named.conf
---------------------------
options {
	directory "/etc/named.data";
	named-xfer "/bin/named-xfer";
	dump-file "named_dump.db";
	pid-file "/var/run/named.pid";
	statistics-file "named.stats";
	allow-transfer {
		5.6.7.8;
	};
};

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

zone "0.0.127.in-addr.arpa" {
	type master;
	file "named.local";
};

zone "mydomain.com" {
	type master;
	file "db.mydomain.com";
};

Secondary Nameserver's named.conf
---------------------------------
options {
	directory "/etc/named.data";
	named-xfer "/bin/named-xfer";
	dump-file "named_dump.db";
	pid-file "/var/run/named.pid";
	statistics-file "named.stats";
	allow-update {
		5.6.7.8;
	};
};

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

zone "0.0.127.in-addr.arpa" {
	type master;
	file "named.local";
};

zone "mydomain.com" {
	type slave;
	file "db.mydomain.com";
	masters {
		1.2.3.4;
	};
};


> -----Original Message-----
> From: kcd at daimlerchrysler.com [mailto:kcd at daimlerchrysler.com]
> Sent: Thursday, July 20, 2000 12:45 PM
> To: bind-users at isc.org
> Subject: Re: strange error when receiving NOTIFY
>
>
>
> What makes you so sure your named.conf files are correct? This message
> unequivocally states that "mydomain.com" is not any domain the nameserver
> thinks it is slaving.
>
>
> - Kevin
>
> Rob Egan wrote:
>
> > Hi,
> >
> > I get the following error on my secondary nameserver anytime I
> restart named
> > on my primary nameserver:
> >
> > Jul 20 10:59:03 localhost named[30040]: rcvd NOTIFY for
> "mydomain.com", name
> > not one of our zones
> >
> > The domain I'm referring to (I obscured the real name to keep
> my boss off of
> > my back) is registered with NSI with the primary and secondary
> nameservers
> > set to the two I'm referring to, and both the primary and secondary
> > definitely have correct configurations in their respective
> named.conf files.
> > Any clues why this error is generated? Thanks!
> >
> > -Rob
>
>
>
>
>
>