[dns-operations] Re: [dns-operations] 答复: [dns-operations] More Aggressive prefetch for popular names

[m3047]

You've articulated different stakeholders, and I'm not sure that their 
interests are truly aligned in all cases. What do you want to do about 
that?

1) If you're in a close enough relationship with an authoritative NS 
operator to receive NOTIFYs, then they can (are) going to essentially set 
you up as a slave operator.

1a) What motivates me as an authoritative to shard my DNS into zones so 
that the names I want prefetched are minimally contained? Are there 
examples in the wild of anyone doing this?

1b) What motivates me as a caching/recursive resolver to want to run a 
slave, and why some domains and not others?

2) A resolver operator is getting requests to do aggressive prefetch 
(stating it as a given for the purposes of testing the hypothesis): from 
who?

2a) Is this the authoritative operator who is requesting, and why?

2b) Is this clients of my resolver(s) who are requesting, and why?

3) How would this be different from running a local instance of some other 
recursive operator's offering, and letting them have the responsibility 
for managing the relationships?

--

Fred Morris

On Fri, 5 Apr 2019, Davey Song(宋林健) wrote:
> 
> If frequent prefetching generating annoying traffic is the main cause, we
> can reduce it dramatically by setting up hidden slave on resolver side
> receiving notify from the popular name owner’s master server. [...]

> 发件人: dns-operations [mailto:dns-operations-bounces at dns-oarc.net] 代表
> Davey Song(宋林健)
> 发送时间: 2019年4月5日 9:19
>
> I’m writing to ask if any resolver operator is doing or be asked to do
> aggressive pre-fetch for popular names in the case of urgent changes of
> owners’ names. [...]