On Mon, 22 Sep 2014, bert hubert wrote:
Feedback welcome! I note that there has been discussion on EDNS0 probing and other fancy things, but please note that this feature is needed to solve a problem we have today. This means it can't involve upgrades to infrastructure except for that operated by the people with the problem - authoritative servers.
If we can do this with auth only changes in a sane way, I'm all for it. But if a decent solution requires recursor updates, we should not leave that solution space out of scope. A bandaid for those that need this today is to delegate the A record of the apex and the www record to the CDN, and MX, NS and SRV records to their own infrastructure. And to refrain from using the apex A/AAAA for any other service. Paul _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
