From owner-freebsd-isp@FreeBSD.ORG Sun Aug 3 22:37:00 2003 Return-Path: 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 DD35F37B401 for ; Sun, 3 Aug 2003 22:37:00 -0700 (PDT) Received: from solar.isr.co.jp (solar.isr.co.jp [210.251.64.162]) by mx1.FreeBSD.org (Postfix) with SMTP id 8EEDA43F85 for ; Sun, 3 Aug 2003 22:36:59 -0700 (PDT) (envelope-from javi@isr.co.jp) Received: (qmail 1330 invoked from network); 4 Aug 2003 14:36:57 +0900 Received: from nat.isr.co.jp (HELO enrique.isr.co.jp) (proxyuser@210.251.64.163) by solar.isr.co.jp with SMTP; 4 Aug 2003 14:36:57 +0900 Received: (qmail 29438 invoked from network); 4 Aug 2003 14:36:57 +0900 Received: from dhcp02.isr.co.jp (HELO ?192.168.1.202?) (192.168.1.202) by enrique.isr.co.jp with SMTP; 4 Aug 2003 14:36:57 +0900 Date: Mon, 04 Aug 2003 14:39:02 +0900 From: Javi Lavandeira To: freebsd-isp@freebsd.org In-Reply-To: <3F2DE3B6.6050409@ensabahnur.net> References: <3F2DE3B6.6050409@ensabahnur.net> Message-Id: <20030804142008.AFE2.JAVI@isr.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Mailer: Becky! ver. 2.06.02 Subject: Re: DNS Server Farm X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2003 05:37:01 -0000 Hi, > Our company has inherited/bought an ISP outfit which has around 2=20 > million subscribers. Among our first priority is to upgrade the DNS=20 > service which has been abysmal according to the users >=20 > Can someone give me a head-start on a recommended configuration for such= =20 > DNS outlay which serves 2M+ dial-up users? I assume the DNS server(s) will be doing name resolution and caching for your customers , am I right? Will you also be hosting the DNS zones of your customers' domains? How many maximum concurrent users do you have? I would go for a djbdns box (http://cr.yp.to/djbdns.html). Use tinydns to serve your DNS zones, and dnscache to provide resolving anc caching. Pro= bably you won't be needing a very powerful machine, but since your company seems to have enough resources, I guess it won't hurt to buy a big one. About the performance, two quotes from the djbdns FAQ: "One site reported receiving 500 queries per second per server at peak times for data from a 350-megabyte data.cdb. The tinydns process handled about 7000 queries per second of CPU time. The CPU was a Pentium III-550. This example, and lab tests, suggest that tinydns can easily handle the =2Ecom server load. However, I don't have enough data on the distribution of .com queries to carry out a realistic experiment." "cr.yp.to, which among other things handles a million mailing-list deliveries in a typical week, has been using dnscache since Christmas 1999. In a typical 4-week period, dnscache used 128 minutes of CPU time on a Pentium II-350, handling 13.7 million queries and receiving 210 megabytes of data to cache. I did a huge Internet survey through dnscache, handling nearly a million PTR queries for random IP addresses in 4.5 hours on a Pentium-133." So, I would advice to install djbdns and do some stress tests. Then you can decide whether you'll be needing another machine or not. Best regards, -- Javi Lavandeira International Systems Research http://www.isr.co.jp