From owner-freebsd-net Fri Jan 26 8:44:22 2001 Delivered-To: freebsd-net@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D09737B69B for ; Fri, 26 Jan 2001 08:44:04 -0800 (PST) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id JAA03787; Fri, 26 Jan 2001 09:44:02 -0700 (MST) Date: Fri, 26 Jan 2001 09:44:02 -0700 (MST) From: Nick Rogness To: Peter Brezny Cc: freebsd-net@freebsd.org Subject: Re: dns; default primary zone files get hard coded origin's on secondary. In-Reply-To: <002201c087ba$10c533c0$46010a0a@sysadmininc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 26 Jan 2001, Peter Brezny wrote: > I recently revamped a lot of my zone files, consolidating several into > generic files since many of our domains have mail, dns, and web hosting on > the same servers. This works fine on the primary server, substituting an @ > symbol in the zone file for the origin of the zone listed in the .conf file. > However, on the secondary The origin in the zone file is being hard coded > to what ever the server looked up first, which of course wrecks the > information for any subsiquent zone that uses the same default zone file. Let me see if I understand you correctly. In /etc/namedb/named.conf you have: zone "abc.com" { type master; file "generic_file.db"; } zone "bcd.com" { type master; file "generic_file.db"; } Am I correct in my assumption? Nick Rogness - Keep on routing in a Free World... "FreeBSD: The Power to Serve " To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message