From owner-freebsd-isp Mon Oct 27 20:17:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA23323 for isp-outgoing; Mon, 27 Oct 1997 20:17:41 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from bert.club-web.com (bert.club-web.com [207.176.196.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA23311 for ; Mon, 27 Oct 1997 20:17:29 -0800 (PST) (envelope-from mark@club-web.com) Received: from mark.club-web.com (dial-102.club-web.com [207.176.196.22]) by bert.club-web.com (8.8.8/8.8.6) with SMTP id XAA09016; Mon, 27 Oct 1997 23:20:20 -0500 (EST) Message-Id: <199710280420.XAA09016@bert.club-web.com> From: "Mark Segal" To: Cc: Subject: Re: Secondary Setup/..... Date: Mon, 27 Oct 1997 23:18:13 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1008.3 X-MimeOle: Produced By Microsoft MimeOLE Engine V4.71.1008.3 Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >We are also trying to setup secondary ....but is there a trick or some >kind a config that will allow the NAMED to "update" automaticly in few >seconds....? Is there some kind of refresh setup. update? yes.. you just make the secondary server a slave to the primary.. just put this in your named.boot or named.conf (DNS startup file) For BIND 8.*: ----- zone "yourname.com" { type slave; file "db.yourname.com" masters { 10.1.1.1 #replace with your primary server ip }; }; ---- and in bind 4.* (i think) --- secondary yourname.com db.yourname.com 10.1.1.1 --- mark -- Mark Segal mark@club-web.com System Administrator - Club-Web Inc.