From owner-freebsd-isp Tue Feb 27 13:57:57 2001 Delivered-To: freebsd-isp@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 1230337B719 for ; Tue, 27 Feb 2001 13:57:52 -0800 (PST) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.11.2/8.11.2) id f1RLvo103458 for freebsd-isp@FreeBSD.ORG.AVP; Tue, 27 Feb 2001 22:57:50 +0100 (CET) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.11.2/8.11.2) with UUCP id f1RLvmS02980; Tue, 27 Feb 2001 22:57:48 +0100 (CET) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.1/8.11.0) with ESMTP id f1RLvTx17031; Tue, 27 Feb 2001 22:57:35 +0100 (CET) (envelope-from leifn@neland.dk) Date: Tue, 27 Feb 2001 22:57:29 +0100 (CET) From: Leif Neland To: Troy Settle Cc: freebsd-isp@FreeBSD.ORG Subject: Re: tinydns In-Reply-To: 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 On Tue, 27 Feb 2001, Troy Settle wrote: > BIND is not an option here, I've been using it for years, and it's taken a > while, but it's proved itself completely unreliable to me. > Not to offend you, but what makes you so special so you are incompatible with BIND? I've had no problems which weren't my own faults. The only trouble has been somebody appearently has taken fun in killing bind's around here, which I haven't gotten around to upgrading to the latest version... Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message