Mass Slave Creation

Re: Mass Slave Creation

From:

Date:

Time:

Men & Mice Support said:

>As Jer and I discussed on the phone, the best way to do this with
>QuickDNS 3.5 is to use the AppleScript we included with the Mac OS
>versions of QuickDNS Manager called "Add Slave Server".

I would like to publicly thank Chris for calling me. As he mentioned
above we ran his Apple Script "Add Slave Server" and completely
recreated every single slave zone on our secondary.

Why did we do this? Well our Secondary Data File become corrupted when I
sought to diagnose a problem I was having with SOA's.... Anyway, upon
looking at the "Secondary Data" folder on the Secondary server, I found
that there were hundreds and hundreds of erroneous slave files dating
back 4+ years. There were duplicate file names, misspellings, zones
without periods, etc... Basically the culmination of 5 years of DNS
record additions, deletions, corrections, etc.

So I decided to manually clean out the Secondary Data Folder of all this
erroneous garbage only to end up corrupting the Secondary Data File when
I tried to modify it with the old 2.x version of QDNS Admin. I used the
old admin to get a better visual picture of how I had acquired so many
dups of various domains with different spellings, or missing periods,
only to find that in the old version of QDNS admin, apparently if you
made a correction, addition/deletion of a slave zone, the old/bad or
misspelled slave zone, (while it was gone from the admin/secondary data
file) remained on the secondary in the Secondary Data Folder. This would
not appear to be the case with 3.5.3 and the new Admin.

Needless to say years of upgrading, downgrading, changes, additions,
deletions, etc., left my secondary hosed with years of junk.

So to clean this up Chris suggested I just delete everything in the
Secondary Data Folder, and then replace the Secondary Data File with a
"fresh"/new version. From there we ran the Apple Script and made a fresh
new Secondary Data File. After that was completed we looked in the admin
for QDNS 3.5.3 and on the Secondary server in the Secondary Data Folder
to confirm that the same number of domains existed in both places.

I would suggest that anyone out there that has used QDNS over the years
do the same thing to their secondary, ie., clean it up. Why? Because
eventually things will become corrupt. My Secondary Data File was
corrupt both before and after I messed with the old admin and caused
numerous goofy problems...

The best thing you can do right now if you use QDNS 3.5x is to go to your
admin and load ONLY your Secondary server. Look at the number of zones.
Then TB2 to your Secondary server directly and manually look at the
Secondary Data Folder. See if that number is the same.

However, I am sad to report that what precipitated my Christmas time
madness and mucking around with my secondary was the "SOA" problem, which
sadly seems to still exist. At least now I have a fresh version of QDNS
and the Secondary Data on my secondary which should make this problem
easier to diagnose.

take care.

jer (jer@mia.net)

Bella Mia, Inc.
High Speed Wireless - www.dslone.com
Domain Registration - www.thednsplace.com
Web Hosting and Colocation - www.hostdrive.com
Nation Wide Dialup 4 years and running - www.mia.net

*** Ask us about our "Multi-Burst" Product! ***

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." Benjamin Franklin

Sales:
888/4-DPOINT

Support:
858/452-3696