> There is no relationship between the data and the conclusion. Having a
> short TTL is not because you make changes often, it's because, when
> you decide to make a change, you want it to be effective rapidly. The
> actual number of changes does not matter, what matter are the
> expectations of users ("sorry, buddy, we made the change immediately
> but it will not be seen by all caches before one week").
I think that is totally fair. But, two things ...
- The TLDs are a little weird in that they are trying to control for
their load and yet serving someone else's names. So, yeah, there is
this sort of mismatch where the SLDs would like shorter TTLs because
they want the flexibility and don't pay the serving price.
Meanwhile, the TLDs don't directly care about the flexibility and so
they optimize for load shedding. So, um, yeah ....
- But, inside google.com this is all much more straightforward. I.e.,
they can be as flexible as they want to provision for.
allman
pgp4xvBaWNfEW.pgp
Description: PGP signature
_______________________________________________ dns-operations mailing list [email protected] https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
