On Saturday, 11 April 2020 13:22:42 UTC Shumon Huque wrote: > ... > > This might also be viewed (correctly) as a corner case in the RRR model > > > that doesn't get addressed; it seems to happen most frequently if a > > registrant changes registrars or if a domain lapses, where the previous > > registrar also acted as DNS operator for the zone. > > I've heard proposals in the past that TLDs should routinely scan all their > delegations to identify such problems, but I gather this is a challenging > requirement to impose on them for various reasons.
i think it's a corner case in the registry / registrar / registrant (RRR) model, as you say. what might be done here is that ICANN or DNS-OARC or the registry of last resort (ROLR) or perhaps all three in cooperation, could jointly operate an anonymizing reporting service to accept real time reports of lame delegations from participating full resolvers. in this case open source resolver makers such as nlnetlabs, cznic, isc, powerdns, and perhaps some commercial resolver makers like nominum and microsoft, and perhaps even some of the so-called "public dns" providers (quad-this, quad-that, etc) could report delegation problems they discover, in real time, to be then sliced and diced and trended and published and especially made available to registrants, registrars, and registries for policy-appropriate remedial action. this is off-topic for the draft at hand, but it's something a strong mature distributed naming system ought to have in it. we finally have enough CPU and enough bandwidth and enough competing cooperators (and enough cooperating competitors) that it's practical to build something like this. -- Paul _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
