Linux Server Security, Second Edition

This is the Title of the Book, eMatter Edition

Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.

djbdns

|

205

2. Pick a public IP address for tinydns. dnscache and tinydns must run on different

IP addresses, since they both use UDP port 53. If you’re running both on one

machine, use the loopback address (127.0.0.1) for dnscache and the public

address for tinydns. If you’re running dnscachex on the machine’s public address,

allocate another IP with ifconfig and use that for tinydns. The tinydns-conf syn-

tax is similar to dnscache-conf:

tinydns-conf acct logacct dir ip

Assuming that you’ve chosen to use the public address 208.209.210.211, config-

ure the service like this:

# /usr/local/bin/tinydns-conf tinydns dnslog /etc/tinydns 208.209.210.211

3. Activate the service by giving svscan a link on which to act:

# ln -s /etc/tinydns /service

4. tinydns will now be running, but without any data to serve. Let’s do something

about that.

Running tinydns

Now it’s time to add some data to your nameserver. You can do this in two ways:

• Use tinydns’s helper applications. These are shell scripts that call tinydns-edit with

default values and check the database for consistency as you make modifica-

tions.

• Edit the tinydns datafile directly. This gives you more control but less automatic

checking.

Helper applications

Let’s use the helpers first. These all modify the text file data while checking with ...