trading secondaries

Re: trading secondaries

From:

Date:

Time:

At 6:06 PM -0400 8/12/02, ahclist wrote:
>>>Chris,
>>>
>>>Forgive the stupid question here, but if I wish to trade secondary
>>>services with another user (say, by simply swapping secondary data
>>>files) is there anything with the versions we should watch out for.
>>>I am still using 3.0.1 and they are using 3.5.x
>>
>>There are no version differences in the format of the Secondary
>>Domains file between version 2.2.1 and all later versions for classic
>>Mac OS, up to 3.5.3. However, unless you have a licensed copy of
>>QuickDNS Pro Admin 2.x somewhere, you won't be able to read it.
>>
>>Swapping the contents of your Secondary Data folders will not
>>accomplish anything.
>>
>>>Also, is there any pressing reason to upgrade to 3.5.3 if 3.0.1 is
>>>working without issue?
>>
>>3.5.3 fixes more than stability problems. 3.0.1 has problems in how
>>it handles certain DNS records and requests.
>
>Ah, so the secondaries list isn't built from just the contents of
>the secondary data folder?

It's not at all built from the contents of the Secondary Data folder.
It's built entirely from the contents of the Secondary Domains file,
which is stored in binary format and is not directly editable using
QuickDNS Pro Admin 2.x.

>Do understand that I'm aware I need to update all of my primary data
>zones prior to doing this, but what else needs to be updated.
>
>Example: Myself and a friend both have licenses for QDNS. We wish
>to offer secondary services to each other, but we are not willing to
>offer direct access to the other's machine for admin.
>
>Aside from a secondary zone file for each zone, what else on the
>secondary side would need to be updated to achieve this. From what
>I understand, running my primary and their secondary files from one
>server is covered under one license. If they also hold one license,
>and wish to offer the same services, how might this be most easily
>acheived? Is there a way to easily modify the secondary domains
>admin file (text editor)? I'd love to know how this can be achieved
>while still keeping things a bit uncomplicated and not requiring
>that we relinquish security to each other.

The only solution that comes to mind is AppleScript. I mean, you can
manually create each slave zone, but for more than a few that's kind
of annoying. AppleScript to the rescue.

A script could be written that takes a list of slave zones to create
(as a text file) and creates them. The script might look something
like this (details left to the reader):

property theMasterServer: "ip.add.re.ss"

on run
set theFile to (open file for access (choose file))
set keepGoing to true
set theZone to ""
repeat while keepGoing
set theZone to my getZoneName (theFile)
if theZone is not "" then
my addZone (theZone)
else
set keepGoing to false
end if
end repeat
end run

on getZoneName (theFile)
return [read a zone name from the file]
end getData

on addZone (theZone)
tell application "QuickDNS Manager"
create new zone ...
end tell
end addZone
____________________________________________________________________
Chris Buxton Men & Mice
support@menandmice.com Making DNS Easy

Sales:
888/4-DPOINT

Support:
858/452-3696