From owner-freebsd-isp@FreeBSD.ORG  Thu Dec 11 15:19:41 2003
Return-Path: <owner-freebsd-isp@FreeBSD.ORG>
Delivered-To: freebsd-isp@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1990F16A4CE
	for <freebsd-isp@freebsd.org>; Thu, 11 Dec 2003 15:19:41 -0800 (PST)
Received: from vette.gigo.com (vette.gigo.com [216.218.228.114])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6DB6243D1D
	for <freebsd-isp@freebsd.org>; Thu, 11 Dec 2003 15:19:40 -0800 (PST)
	(envelope-from jfesler@gigo.com)
Received: from localhost (localhost.gigo.com [127.0.0.1])
	by vette.gigo.com (Postfix) with ESMTP id 8C770A98B;
	Thu, 11 Dec 2003 15:18:22 -0800 (PST)
Date: Thu, 11 Dec 2003 15:18:22 -0800 (PST)
From: Jason Fesler <jfesler@gigo.com>
To: "::::Carlos:::Ariel:::Canta::::::::" <admin@redy.net.ar>
In-Reply-To: <oprz0sny1jg5bkrx@smtp.redynet.com.ar>
Message-ID: <20031211151652.X61349@vette.gigo.com>
References: <oprz0sny1jg5bkrx@smtp.redynet.com.ar>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-isp@freebsd.org
Subject: Re: djbdns
X-BeenThere: freebsd-isp@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Internet Services Providers <freebsd-isp.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isp>,
	<mailto:freebsd-isp-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isp>
List-Post: <mailto:freebsd-isp@freebsd.org>
List-Help: <mailto:freebsd-isp-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isp>,
	<mailto:freebsd-isp-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2003 23:19:41 -0000

> But my clients use de same ip for cache(dnscahe=my actully public ip) and

You can't (without patches at least) run both dnscache (resolver) and
tinydns (authoritive) on the same single IP.

On my own system, I run dnscache on 127.0.0.1; I run tinydns on my main
ethernet IP; and I run a resolver for clients on a virtual IP.  One
machine can handle it, but you'll need more than one public IP.