> Colm MacCárthaigh <mailto:c...@allcosts.net> > Sunday, September 21, 2014 3:33 PM > > > i'd be very interested in a standards-track (interoperable; > including DNSSEC support and AXFR/IXFR) version of this feature. > my hope is that you will remove out-of-zone capability here, that > is, the target of ALIAS should have to be authority data in the > same zone. > > > But then the feature is pointless; you could just include the record > directly at the apex if you knew what the value should be. you make a good point. i'm curious about the implication.
does the ANAME(/ALIAS) server proxy every request, so, no caching? or, if it caches, does it implement "client subnet"? and, either way: if the proxied request times out (or servfails), does the original authority request also time out (or servfail?) and i wonder-- if the proxy request returns NXDOMAIN, what does the authority answer with? what the implementers of this nonstandard feature seem to want is cname-and-other-data, by which i mean, a requester-visible alias that can live at the apex, and then have its target resolved in the requester's context. i'm not sure how best to do it, but i'm not liking the implications of always-proxy nor proxy-with-cache. -- Paul Vixie
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
