From owner-freebsd-isp Thu May 21 01:29:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24597 for freebsd-isp-outgoing; Thu, 21 May 1998 01:29:58 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt053nd2.san.rr.com [204.210.34.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24591 for ; Thu, 21 May 1998 01:29:54 -0700 (PDT) (envelope-from Studded@san.rr.com) Received: from san.rr.com (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id BAA22854; Thu, 21 May 1998 01:29:50 -0700 (PDT) (envelope-from Studded@san.rr.com) Message-ID: <3563E5FD.49504753@san.rr.com> Date: Thu, 21 May 1998 01:29:49 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE-0507 i386) MIME-Version: 1.0 To: Alan Batie CC: freebsd-isp@FreeBSD.ORG Subject: Re: very strange nameserver problem References: <19980520234216.35613@rdrop.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alan Batie wrote: > > I've got two virtual domains here; one is a clone of the other and the > first one works and the second one gives "server failed". I even used > this as an excuse to upgrade to 8.1.2, and it acts exactly the same way. > > Here are the two zone files: I don't see anything obviously wrong with the zone files. Are you watching the named.log when you reload the nameserver to see if it's giving you errors? I suspect an error in named.conf. Good luck, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud designer and maintainer of one of the world's largest *** Internet Relay Chat server with 5,328 simultaneous connections *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message