How to convert BIND to TinyDNS?

[Benson Wong]

This is the cheat sheet I have at the top of my tinydns data (definition) file:

###############################################################################
# TinyDNS Data File for domains hosted on our primary name server
# Notes:
#
#   Make sure all domains use [a.ns.domain.com] and [b.ns.domain.com] as the
#   authorative name servers. This is done at the registar.
#
#   Define the hosts and ns information here.
#   For each domain needs NS entries in order to be answered by tinydns.
#
#   Quick Reference: (see: http://cr.yp.to/djbdns/tinydns-data.html)
#   - each line starts with a special character:
#     # --> Comment
#     . --> NS record
#       use these as a default:
#         .domain.com::a.ns.domain.com
#         .domain.com::b.ns.domain.com
#     = --> An "A" record
#     + --> Alias, like an "A" record but no PTR created.
#     @ --> MX Record :
#            @domain.com:1.1.1.4:mail.domain.com:10
#            -> creates mail.domain.com with ip 1.1.1.4 as the MX,
#               with distance 10
#     C --> CNAME Record: (CAREFUL WITH USAGE) Use to point one domain to
#           another
#              Cdomain.com:otherdomain.ca:86400
#              Cchat.suttoncity.com:suttoncity-com.ch.outblaze.com:86400
#
#   - Wildcards
#     +*.domain.com:192.168.1.4:86400
#       - this will resolve for
#            www.domain.com, lfja.domain.com, xxx.domain.com, etc.
#
###############################################################################
--

In reply to the BIND vs TinyDNS debate, I've been running it as a DNS
server for about 2 years now on FreeBSD. Zero problems since I made it
live. And I run a pretty large domain.

I also use the resolver that comes with DJBDNS. Again extremely
stable, and no problems. These run on the same machine as the DNS
servers, different IP address, and both answer more than one million
queries a day.

Load on the machines never go over 0.2

The only problem I've ever had was that the resolvers didn't have
enough ram dedicated to them (slowed them down). After bumping that
up, they just run/work.

My only complaint is that tinydns doesn't have a great way to manage a
huge number of domains, since everything goes into one large file. Of
course, that can be easily maintained by putting each domain into a
separate text file, and writing a shell script that cat's them all
together before generating the cdb binary file.

Ben.