From owner-freebsd-isp@FreeBSD.ORG  Thu Dec 11 21:13:46 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 2908516A4CE
	for <freebsd-isp@freebsd.org>; Thu, 11 Dec 2003 21:13:46 -0800 (PST)
Received: from admin.wolfpaw.net (admin.wolfpaw.net [204.209.44.9])
	by mx1.FreeBSD.org (Postfix) with SMTP id C31E943D36
	for <freebsd-isp@freebsd.org>; Thu, 11 Dec 2003 21:13:44 -0800 (PST)
	(envelope-from admin-lists@wolfpaw.net)
Received: (qmail 32308 invoked from network); 12 Dec 2003 05:13:43 -0000
Received: from adsl246-118.incentre.net (HELO wolf) (207.216.246.118)
  by admin.wolfpaw.net with SMTP; 12 Dec 2003 05:13:43 -0000
From: "Wolfpaw - Dale Corse" <admin-lists@wolfpaw.net>
To: <freebsd-isp@freebsd.org>
Date: Thu, 11 Dec 2003 22:23:16 -0700
Message-ID: <AJENJFOLCLAHHIIGCCHNMEFDMGAA.admin-lists@wolfpaw.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <004401c3c045$665f1690$fbb4a741@cedata.net>
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: Fri, 12 Dec 2003 05:13:46 -0000

How does djbdns measure up to bind anyway? Bind works wonderfully
for us.. any reasons someone can come up with (other then the beaten
to deal security arguments) why a person should change over?

Thanks in advance :)
D.
--------------------------------
Dale Corse
System Administrator
Wolfpaw Services Inc.
http://www.wolfpaw.net
(780) 474-4095

> -----Original Message-----
> From: owner-freebsd-isp@freebsd.org
> [mailto:owner-freebsd-isp@freebsd.org]On Behalf Of Greg 
> Cirino - Cirelle
> Enterprises
> Sent: Thursday, December 11, 2003 5:18 PM
> To: ::::Carlos:::Ariel:::Canta::::::::
> Cc: freebsd-isp@freebsd.org
> Subject: Re: djbdns
> 
> 
> | > But my clients use de same ip for cache(dnscahe=my 
> actully public ip) and
> 
> The basic logic for djbdns
> 
> tinydns - authorative IP
> axfrdns - authorative IP
> 
> dnscache - alternate IP
> 
> tinydns used for resolving domains you own on UDP
> axfrdns used for accepting requests from TCP (larger than 512)
> 
> dnscache used for resolving the internet (and your 
> authorative domains)
> 
> Let's say your authorative domain server is registered with 
> the internic as 
> NS.YOURDOMAIN.COM at IP 1.2.3.4 (this only contains domains 
> you host)
> 
> tinydns should listen to 1.2.3.4
> axfrdns should listen to 1.2.3.4
> 
> dnscache needs to be on a different IP (i.e. 1.2.3.5)
> 
> If you want your internal servers/workstations to be able 
> to resolve the internet
> you will need to change all primary dns entries in 
> resolv.conf (or network on
> windows machines) to the IP of dnscache (in this case 1.2.3.5).
> 
> A good reference can be found at:
> http://lifewithdjbdns.org/
> 
> HTH
> Greg
> 
> _______________________________________________
> freebsd-isp@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-isp
> To unsubscribe, send any mail to 
> "freebsd-isp-unsubscribe@freebsd.org"
>