From owner-freebsd-isp Tue Aug 11 00:55:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23270 for freebsd-isp-outgoing; Tue, 11 Aug 1998 00:55:34 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from leaf.lumiere.net (leaf.lumiere.net [207.218.152.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23262 for ; Tue, 11 Aug 1998 00:55:33 -0700 (PDT) (envelope-from j@leaf.lumiere.net) Received: (from j@localhost) by leaf.lumiere.net (8.9.1/8.9.1) id AAA28321; Tue, 11 Aug 1998 00:55:18 -0700 (PDT) Date: Tue, 11 Aug 1998 00:55:18 -0700 (PDT) From: Jesse To: freebsd-isp@FreeBSD.ORG Subject: named sending out NOTIFY on alternate IP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Anyone know if it's possible to have named originate all outgoing connections from an aliased IP? Such a NOTIFY's. I have my ns on its own IP for portability, but it isn't the primary IP for the machine. When it sends NOTIFYs to inform the secondary DNS server about DNS record changes, the secondary DNS server always sees it as coming from a non-authorative server since it's not coming from the ns IP. I know I can just add the primary DNS servers' IP to the secondary servers' master server list, but that's just a work around. I'd prefer to make it send out the NOTIFYs via the right IP. It'd also make it possible to secure up my ipfw rules a bit more. If anyone has any ideas or comments, I'd appreciate it. Thanks. --- Jesse http://www.lumiere.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message