Re: [DNSOP] New draft for ALIAS/ANAME type

In many cases, DNS Made Easy is seeing ANAME records requiring synthesized
A record updates every 90 seconds or so. Also, it is surprising to me that
our non-apex ANAME record count has surpassed apex ANAME record count by a
significant amount. We have approximately 25% fewer apex ANAME records than
non-apex, however apex ANAME records account for over 75% of ANAME zone
update activity. We currently process around 50,000 distinct ANAME records
and we are seeing an average of 60, max of 925, and min of 0 zone updates
per zone per day with an average of 1.74 synthesized A records per non-apex
ANAME record and 1.41 synthesized A records per apex ANAME record.

On Fri, Apr 7, 2017 at 2:44 AM, Petr Špaček <petr.spacek@nic.cz> wrote:

> On 4.4.2017 19:30, Matthew Pounsett wrote:
> > On 4 April 2017 at 13:21, Tony Finch <dot@dotat.at
> > <mailto:dot@dotat.at>> wrote:
> >
> >     > I believe that's a faulty assumption.   Here's some data:
> >     >
> >     > [...] During the month of February, [...] an average of 31 changes
> >     per zone. [...]
> >
> >     That seems to agree with what I meant, though I probably should have
> >     said
> >     "per-zone" somewhere :-)
> >
> > That's the average, but there's a not-insignificant number there being
> > updated many times per day.    Most of the time, you're right, there are
> > few changes, but one can't assume that any given alias will have a low
> > rate of change.
>
> Numbers, that really helps!
>
> If I consider the numbers above and the fact that IXFR is able to deal
> even dynamically updated zones, I conclude that pushing ANAME logic to
> provisioner side is reasonable approach and that added complexity in
> name server itself is not warranted.
>
> --
> Petr Špaček  @  CZ.NIC
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>