On 22/09/04 13:20, Paul Maric wrote: > Just before I go through checking everything I need to ask. > > When using VegaDNS, should it be used when TinyDNS is first configured so > it knows no other settings, and should the 'data' file be empty when > running the update file?
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. 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 > > Paul > > -----Original Message----- > From: Bob Hutchinson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 22 September 2004 9:29 PM > To: [EMAIL PROTECTED] > Subject: Re: [users] update-data.sh not functioning correctly... > > On 22/09/04 09:01, Paul Maric wrote: > > Ok, > > > > So I should remove all existing information from the 'data' file and then > > proceed to use VegaDNS? > > To figure out what is going wrong, break the job up > > run something like > wget -d -O /etc/tinydns/root/data-srv-1 http://127.0.0.1/vegadns/ > index.php?state=get_data > > that's all one line. Edit to suit and make sure the perms are in vegadns. > -d should give you gobs of debug. > > then look at data-srv-1 and see if it looks good, if it does copy to data > and > run make. > > edit update-vegadata.sh > #rm $TINYDNSDIR/root/data > mv $TINYDNSDIR/root/data $TINYDNSDIR/root/data.old > > if you want to keep a static part try something like this before the make > > cat "$TINYDNSDIR/root/data.static" >>$TINYDNSDIR/root/data > > where data.static contains the static data ;-) > > I use this for some reverse dns records. Although they can be put into > vegadns > it's easier this way. > > Another handy piece of code... > > # Don't make if the files havn't changed > OLD=$(sum $TINYDNSDIR/root/data.old) > NEW=$(sum $TINYDNSDIR/root/data) > > if [ "$OLD" != "$NEW" ]; then > (cd $TINYDNSDIR/root ; make -s) > fi > > see Karl Shea's email dated 23/08/2004 on this list > > Hope this helps... > > > Paul > > > > -----Original Message----- > > From: Bill Shupp [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, 22 September 2004 4:47 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [users] update-data.sh not functioning correctly... > > > > Paul Maric wrote: > > >Hi, > > > > > >I input data manually into the 'data' file and tried adding another > > domain > > > >via VegaDNS to test it, ran the update file and it simply removed all > > > the information from 'data' and made another file in the 'root' > > > directory. > > > > > >It had never worked previously. > > > > > >Any ideas? > > > > By default, update-data.sh creates a new data file whose contents are > > solely from the database. It overwrites existing information. It is > > recommended that you keep all tinydns records in VegaDNS if you plan to > > use VegaDNS to manage domains. If you do need to split up domains > > between VegaDNS and a static file, you'll need to modify update-data.sh > > to accomodate that. I believe one of the perl scripts in the contrib > > directory on www.vegadns.org has already addresses this, but I've never > > used it. > > > > Regards, > > > > Bill -- ----------------- Bob Hutchinson Midwales dot com -----------------
