trading secondaries

Re: trading secondaries

From:

Date:

Time:

> >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? 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.

Thoughts?

paul

Sales:
888/4-DPOINT

Support:
858/452-3696