In article <[email protected]> you write: >Authoritative servers / zone transfers >-------------------------------------- > >No special new behaviour. > > >Additional section processing >----------------------------- > >This applies to auth and rec servers. In response to an A / AAAA / >ANAME query, include any sibling A / AAAA / ANAME records, and any >ANAME target A / AAAA records. When DO=1, include DNSSEC proofs of >nonexistence for missing RRsets.
If I look up foo and it has an ANAME to bar, which of these do I get back? foo. ANAME bar. foo. A 1.2.3.4 foo. ANAME bar. bar. A 1.2.3.4 The second is a lot more like what CNAME does, and also avoids having to sign on the fly. There is of course the question of whether caches and stubs will treat them like cname results or like cache poisoning. R's, John PS: I still think fixing apex CNAME is a better way to go. _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
