On Thu, Apr 20, 2017 at 04:54:55PM -0400, Paul Wouters wrote: > If that is your use case, I also see no point in ANAME being used by > resolvers, and you should just create the new XFR type for this, so that > AUTH servers can update their A/AAAA records without needing any > recursive DNS protocol changes. Because what you seem to want is a > method for updating some information between two AUTH servers.
What I want is for queries for addresses at a zone apex to be redirectable, so that (for example) "www.example.com" and "example.com" have the same degree of flexibility. I'd love it if an authoritative server, configured with an ANAME, returned only the ANAME and let the resolver populate it. However, legacy resolvers won't know what to do with an ANAME answer, so the authority will need to provide addresses too. Several vendors are already doing that part of it. > Maybe if A and SRV could be returned in the same query they would, so > that leads back to generic support for multi-type queries (with I guess > _location support) being a better generic solution to the problem > compared to this ANAME draft that builds a validating recursive resolver > into any authoritative server. Once again, the recursive resolver needn't be built in. It only has to be accessible -- via resolv.conf, for example. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
