Is djbdns right for me?

I'm setting up a service where I will host several different domains.   When
a new domain wants to host on my site I want them to point to
ns1.mydomain.com and ns2.mydomain.com.

All domains that I host will be available on my N hosts 1.1.1.1 - 1.1.1.N.


   - When foo.com decides to host with me I need to manually add the
   following lines to the djbdns data file

.foo.com::ns1.mydomain.com:259200
.foo.com::ns2.mydomain.com:259200

This format is frowned on but it seems the only way to allow me to have 1
set of nameservers for several domains.

   - Then I add alias N * 2 times (do I need both lines or will
*.foo.comlines do the trick?)

./add-alias foo.com 1.1.1.1
./add-alias foo.com 1.1.1.N
./add-alias *.foo.com 1.1.1.1
./add-alias *.foo.com 1.1.1.N


   - run make and then the owner of foo points to my nameservers  (
   ns1.mydomain.com and ns2.mydomain.com)


Is djbdns right for what I am trying to do?

One more wrinkle..  I plan on running these servers in the cloud either on
slicehost or aws.  The IP addresses already have in-addr pointers assigned
(as far as I can tell)

nslookup 67.23.34.123

Non-authoritative answer:
123.34.23.67.in-addr.arpa       name = 67-23-34-123.static.slicehost.net.

is this an issue?

And one final cloud question..   I usually disable root login on my cloud
hosts,   for now I changed permissions on /service/tinydns/root/data.cdb so
I can rsync as a different user.   Does anyone else have suggestions on how
I might do this differently?


Thanks in advance for any responses!
Tony Primerano