Going from bind9 to djbdns

[Kristian Vaaf]

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