Unfortunately, the reverse zone is very often out of reach for those who use the IP range and trying to do classless reverse delegation (RFC 2317) for those who have less than a /24 is even harder to get.
Paul Sent using a virtual keyboard on a phone On Jun 21, 2022, at 23:30, rubensk=40nic...@dmarc.ietf.org wrote:
That's my recollection as well, but as the saying goes, code is law. Although in this case only registry/registrar and DNS operator are required to interoperate for the bootstrapping process. In practice, I doubt that enough reverse zones are signed or that the provisoning crudware that people use for reverse zones would work often enough to be worth trying to do this. I did some surveys of zones and found that in-bailiwick NS are quite uncommon, only a few percent of the ones in large gTLDs.
I don't expect the IP space used for DNS servers to be managed thru an IPAM system of sorts. But if one is used, it's unlikely they provision a zone-cut as required in the draft.
Or if supporting this type of DNS servers can help the adoption of this draft for the 99.9% use case of out-of-bailiwick servers. If not, we could be adding a new piece to the DNS Camel...
Rubens
_______________________________________________DNSOP mailing listDNSOP@ietf.orghttps://www.ietf.org/mailman/listinfo/dnsop
|
signature.asc
Description: Binary data
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop