> On 6 Jul 2018, at 6:59 pm, Philip Homburg <pch-dnso...@u-1.phicoh.com> wrote: > > In your letter dated Fri, 6 Jul 2018 18:50:44 +1000 you wrote: >> All it does is ensure that the DNS queries get to the DNS64 server. > > The way RFC 7050 works that you send queries to your local recursive > resolver. The problem there is that if the user manually configured > a public recursive resolver then you don't learn the translation prefix. > > In this context I don't see how serving ipv4only.arpa from dedicated addresses > would help.
When the local recursive server forwards the query to the ISP’s servers they get the AAAA records. With a dedicated prefix if the recursive server is iterative it will get the delegation from the ARPA servers and find the ISP’s servers ipv4only.arpa which will return the prefix. This is how I run my servers though it will be a cold day in hell by the time my ISP delivers IPv6 let alone IPv6-only. (I’ve only been asking for IPv6 since 2003). This doesn’t help with those that send queries to 8.8.8.8, only DPI or having the recursive server follow the learned DNS server for ipv4only.arpa will help with that scenario. It’s all about closing off failure paths. > We can define a new prefix discovery protocol where the node that needs to > discover the prefix directly queries the authoritative servers for > ipv4only.arpa. That would solved the issue with manually configured > resolvers. But it would also add yet another way off discovering the prefix > that needs to be supported. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
