Hi all,
I am working on an experimental implementation of ANAMEs in our authoritative
name server software, which shall perform its own ANAME lookup. I am a bit
puzzled what is really expected to be returned for regular address (A/AAAA)
queries.
- Is it right that the determined target address records shall appear twice,
first in the answer section, with the query name as the owner and the TTL
adjusted (based on the involved records), second in the original form in the
additional section?
- It is not yet quite clear to me what the purpose of recording the visited
ANAMEs and CNAMEs beyond the very first ANAME in the additional section, as
described in the section 3. Is it of any use for an aware resolver? Shall it
validate the path to the target addresses in order to recognize them as such?
And what about DNAMEs? I constructed a nice example, despite not knowing whether
such a situation would ever occur in real life:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3
;; flags: qr aa ; qd: 1 an: 1 au: 0 ad: 5
;; QUESTIONS:
;; multi.example., type = AAAA, class = IN
;; ANSWERS:
multi.example. 20000 IN AAAA fe:dc:ba:98:76:54:32:10
;; AUTHORITY RECORDS:
;; ADDITIONAL RECORDS:
multi.example. 86400 IN ANAME redir1.target.
redir1.target. 20000 IN CNAME redir2.sub.target.
sub.target. 86400 IN DNAME base.target.
redir2.base.target. 86400 IN ANAME redir3.target.
redir3.target. 30000 IN AAAA fe:dc:ba:98:76:54:32:10
;; Message size: 223 bytes
- if the name server chooses to cache the target address records (and the
intermediate xNAME records), shall the answer reflect the age of the cache
entries in the TTLs (i.e. be subtracted) of the records in the answer and/or
additional section?
Sorry in case that the questions do not make sense. I have to admit that I have
not yet fully understood the document in all aspects. But that's why I am asking.
Regards,
Klaus
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
