Normen Kowalewski <nbkowalew...@gmx.net> wrote:
> apologies for this really very late reply, but FAIW it's IMHO not
> really a "Synchronization Server", because the flow is really
> hierachical - from home via the to-be-named-entity, and then to the
> place tha scales out, like the slaves of that entity. I think it is
> also not really a “Distribution Server", if the collecting
> to-be-named-entity is a fully grown-up DNS Auth by itself, in which i
> can/do also manage zones directly.
I never liked "Synchornization Server", and we removed that term.
We settled on Distribution Master, which is usually the stealth primary, and
transfers zones to the public secondaries.
> When I ran things in a chain like this, it saw the to-be-named-entity
> as acting in the capacity of a "DNS intermediary [master]", or "DNS
> provisioning proxy".
DNS intermediary Master, conveniently could also be abbreviated to "DM" :-)
> AFAIK already when we starting the early discussions on this (Hi
> Daniel, Hi Ralf!) for the former expired draft, we had not found a
> specific terminology for such a use of nn DNS Authorittive Server in a
> draft/doc anywhere, but i still think it is worth the effort to have a
> specific term for that.
--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
