From owner-freebsd-questions@FreeBSD.ORG Thu Dec 29 16:55:30 2005 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6A7216A41F for ; Thu, 29 Dec 2005 16:55:30 +0000 (GMT) (envelope-from vaaf@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id C124643D9C for ; Thu, 29 Dec 2005 16:55:20 +0000 (GMT) (envelope-from vaaf@broadpark.no) Received: from broadpark.no ([217.13.4.96]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IS9006J2R80WY10@osl1smout1.broadpark.no> for questions@freebsd.org; Thu, 29 Dec 2005 18:00:00 +0100 (CET) Received: from [80.202.4.61] (Forwarded-For: [213.187.181.70]) by bgo1mstore1.broadpark.no (mshttpd); Thu, 29 Dec 2005 17:55:11 +0100 Date: Thu, 29 Dec 2005 17:55:11 +0100 From: Kristian Vaaf To: questions@freebsd.org Message-id: MIME-version: 1.0 X-Mailer: Sun Java(tm) System Messenger Express 6.1 HotFix 0.05 (built Oct 21 2004) Content-type: text/plain; charset=us-ascii Content-language: en Content-transfer-encoding: 7BIT Content-disposition: inline X-Accept-Language: en Priority: normal Cc: Subject: Going from bind9 to djbdns X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2005 16:55:30 -0000 Hello! My friend, who hosts most of my stuff, is using djbdns. Probably for security and simplicity. Anyway I thought I'd do the same. But I'm having serious difficulties finding a user-friendly howto. I've basically picked stuff from here and there and put them together. Would this be what I need to set up a djbdns equivalent to http://www.home.no/hedhnta/namedb? -- Create users: tinydns axfrdns dnslog dnscache -- Run these commands: mkdir /etc/tinydns mkdir /etc/axfrdns mkdir /etc/dnslog mkdir /etc/dnscache mkdir /etc/dnscache/root mkdir /etc/dnscache/root/ip mkdir /etc/dnscache/root/servers Should the above directories be set as home for the users above? -- Continue with: dnscache-conf dnscache dnslog /etc/dnscache 127.0.0.1 touch /etc/dnscache/root/ip/192.168.187.1 touch /etc/dnscache/root/ip/192.168.187.2 echo 127.0.0.1 > /etc/dnscache/root/servers/mydomain.lan echo 127.0.0.1 > /etc/dnscache/root/servers/187.168.192.in-addr.arpa tinydns-conf tinydns dnslog /etc/tinydns 213.187.181.70 axfrdns-conf axfrdns dnslog /etc/axfrdns /etc/tinydns 213.187.181.70 ln -s /etc/dnscache /service ln -s /etc/tinydns /service svc -t /service/dnscache -- Would djbdns now have created this file for me? If so, can I skip this? If not, I take it I should: vim /etc/tinydns/data And type in: .mydomain.com::ns1.mydomain.com @mydomain.com::mail.mydomain.com =myhost.mydomain.com:213.181.112.43 +mail.mydomain.com:213.181.112.43 +www.mydomain.com:213.181.112.43 Then: cd /etc/tinydns make -- To allow my 213.181.102.23 to be ns2.mydomain.com, I must do this? vi /etc/axfrdns/tcp And then type in: 213.181.102.23:allow,AXFR="*" I have a lot of domains. I want the ns2 to handle them all. Is the wildcard "*" valid, or should I list them all? Anyway: cd /etc/axfrdns make -- As for my zone files, I take it I could cram all my domains into the data file? How would that look? -- That's it. I'm hoping that once everything is up, my configuration will be stored in files that I can back up and easily redeploy incase of an accident (similar to my current namedb setup I posted above). Thank you all, and happy new year! Kristian Vaaf