each / draft-aname

work on a draft to standardize ANAME/ALIAS records to allow CNAME-like records at the zone apex
7 stars 4 forks source link

note about forwarding resolvers #24

Closed stbuehler closed 5 years ago

stbuehler commented 6 years ago

Something like:

Forwarding resolvers not trusting their upstream to support ANAME MAY query for ANAME directly when queried for A/AAAA

matje commented 5 years ago

I don't think we should add special logic for ANAME processing: The ANAME is signed so it is trustworthy. Also there is no text prohibiting this so if an implementation wants to do an additional ANAME query because it is paranoid, there is nothing stopping him from doing that.