Date: Wed, 24 Nov 1999 13:23:20 -0600 From: "Damon M. Conway" <damon@chiba.3jane.net> To: Robert Gash <gashalot@gashalot.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: BIND 8.2.2pl5 NOTIFY problems Message-ID: <199911241923.NAA28203@chiba.3jane.net> In-Reply-To: <Pine.LNX.4.20.9911241352060.1932-100000@raq.tabernae.com> References: <Pine.LNX.4.20.9911241352060.1932-100000@raq.tabernae.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Gash wrote:
>I recently upgraded from bind 8.1.2 to bind 8.2.2pl5 (the FreeBSD port of
>bind 8.2.2pl5), and after the upgrade the NOTIFY's between ns1 and ns2
>quit working properly (I have to manually issue an ndc reload ZONE to get
>the nameservers to sync). I have specified the "notify yes;" directive in
>the named.conf file and everything else appears to be working fine, does
>anyone know why my nameserver wouldn't be sending the notify's
>properly?
since it was working i take it you were using the also-notify command to
specify the servers to notify. the entry should look something like this:
zone "mydomain.com" {
type master;
file "db.mydomain.com";
notify yes;
also-notify 10.0.0.2;
also-notify 10.0.0.3;
};
>(Just as a side note, the primary and secondary nameserver IPs are simply
>extra IP aliases to the primary mail and webservers. IE- primary IP for
>ns1 is .129, but ns1 resolves to .133 [it's an alias], primary IP on the
>ns2 machine is .130, but ns2 is bound to .134.)
this shouldn't cause any problems AFAIK.
damon
--
Damon Conway
Black Rock City Ranger...Riding the edge of chaos
"Ana Ng and I are getting old,
but we still haven't walked in the glow of each other's majestic presence."
-- TMBG
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911241923.NAA28203>