From owner-freebsd-questions Wed Nov 24 10:58: 5 1999 Delivered-To: freebsd-questions@freebsd.org Received: from raq.tabernae.com (raq.gashalot.com [208.197.146.18]) by hub.freebsd.org (Postfix) with ESMTP id 2934814DF2 for ; Wed, 24 Nov 1999 10:57:55 -0800 (PST) (envelope-from gashalot@gashalot.com) Received: from localhost (gashalot@localhost [127.0.0.1]) by raq.tabernae.com (8.9.3/8.8.8) with ESMTP id NAA02830 for ; Wed, 24 Nov 1999 13:54:55 -0500 Date: Wed, 24 Nov 1999 13:54:54 -0500 (EST) From: Robert Gash X-Sender: gashalot@raq.tabernae.com To: freebsd-questions@freebsd.org Subject: BIND 8.2.2pl5 NOTIFY problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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? (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.) -Robert Gash To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message