Bob Hutchinson wrote:
It does not matter, any existing data file is moved/removed by the update
script and the new one installed. There is no connection between VegaDNS and
TinyDNS except for the data file.
I think that's what confuses new users... you need to axfr your
existing data into vegadns *before* starting to use the update script...
They don't have to be on the same machine, you can have several VegaDNS
instances and merge them into one data file, that's already built in to the
update script. You can test if your data is delivering what you want without
TinyDNS running, just cd into the root dir and run
tinydns-get any example.com
This is what makes VegaDNS so unbelievably attractive to me... I set up
a "secondary" nameserver in about 2 minutes and it auto-populated itself
because VegaDNS uses a single database.. It's great!
--
---------------------------
Jason 'XenoPhage' Frisvold
Engine / Technology Programmer
[EMAIL PROTECTED]
RedHat Certified - RHCE # 803004140609871
MySQL Pro Certified - ID# 207171862
MySQL Core Certified - ID# 205982910
---------------------------
"Something mysterious is formed, born in the silent void. Waiting alone and unmoving, it is
at once still and yet in constant motion. It is the source of all programs. I do not know its
name, so I will call it the Tao of Programming."
