From owner-freebsd-questions@FreeBSD.ORG  Tue Aug 30 10:09:13 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: questions@freebsd.org
Delivered-To: freebsd-questions@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C3DA616A41F
	for <questions@freebsd.org>; Tue, 30 Aug 2005 10:09:13 +0000 (GMT)
	(envelope-from savage@savage.za.org)
Received: from pyro.cenergynetworks.com (pyro.cenergynetworks.com
	[196.30.191.122])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3621143D48
	for <questions@freebsd.org>; Tue, 30 Aug 2005 10:09:12 +0000 (GMT)
	(envelope-from savage@savage.za.org)
Received: from localhost.cenergynetworks.com ([127.0.0.1]
	helo=pyro.cenergynetworks.com)
	by pyro.cenergynetworks.com with smtp (Exim 4.51) id 1EA33j-000CMK-sd
	for questions@freebsd.org; Tue, 30 Aug 2005 12:09:40 +0200
Received: from wbs-146-187-07.telkomadsl.co.za ([165.146.187.7] helo=MEGADROID)
	by pyro.cenergynetworks.com with esmtpa (Exim 4.51)
	id 1EA33Z-000CME-rS
	for questions@freebsd.org; Tue, 30 Aug 2005 12:09:29 +0200
Message-ID: <00cc01c5ad4a$d9dc5d50$0a02a8c0@MEGADROID>
From: "Chris Knipe" <savage@savage.za.org>
To: <questions@freebsd.org>
Date: Tue, 30 Aug 2005 12:09:01 +0200
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2670
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	pyro.cenergynetworks.com
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 required=5.0 tests=BAYES_00,RCVD_IN_NJABL_DUL,
	RCVD_IN_SORBS_DUL autolearn=no version=3.0.4
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.0.3.0,
	Antispam-Data: 2005.3.10.17
Cc: 
Subject: bind9 issue?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2005 10:09:13 -0000

Hi,

I'm not on the bind9 mailing lists, hopefully someone can help me out here, 
or as I suspect, perhaps just fill in a bug report....

My server has a primary IP, with various aliases:
x.x.x.136 (Primary)
x.x.x.131 (Alias)

named.conf:
options {
  listen-on port 53 { x.x.x.131; };
  query-source address x.x.x.131 port 53;
  transfer-source x.x.x.131;
};

Yes, notifies at my slave, comes from x.x.x.136!!!!  The slave thus, 
complains notify from non master (because 136 is not a name server), and as 
such, no updates happens on my slaves.

How can I force bind9 to send notifies from the query-source address?  IMHO, 
if bind uses the query-source address do to lookups, it *should* also use 
this address to send notifies - hence, my initial claim above re bug...

Can anyone perhaps confirm this?? Alternatively, give some pointers to a 
working way for the above scenario?

Thanks,
Chris.