Most of the special handling could be avoided if IANA was instructed to run the servers for ipv4only.arpa on dedicated addresses. Hosts routes could then be installed for those address that redirect traffic for ipv4only.arpa to the ISP’s DNS64/ipv4only.arpa server.
Perhaps 2 address blocks could be allocated for this purpose. One for ipv4 and one for ipv6. -- Mark Andrews On 5 Jul 2018, at 20:05, Philip Homburg <pch-dnso...@u-1.phicoh.com> wrote: >> draft-cheshire-sudn-ipv4only-dot-arpa document > > Section 7.1: > "Name resolution APIs and libraries MUST recognize 'ipv4only.arpa' as > "special and MUST give it special treatment. > > It seems to me that it is going way to far to require all DNS software to > implement support for a hack that abuses DNS for configuration management of > a rather poor IPv4 transition technology. > > I think the more obvious approach is to formally deprecate RFC 7050 and > require nodes that need to do NAT64 address synthesis use one of the other > methods for obtaining the NAT64 prefix. > > The only part of the draft that makes sense to me is to make ipv4only.arpa > an insecure delegation. > > Any other problems are better solved by deprecating RFC 7050. > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
