Or we could defined the "aaa" (A and AAAA) {E}DNS bit where the
server guarantees that the response contains both the A and AAAA
answers for A or AAAA queries if aaa=1 in the response.
Recursive servers would lookup A/AAAA records if cache is missing
them before returning a response.
If the A / AAAA does not fit into the additional section then TC=1
is set.
NOERROR NODATA is valid for both types if aaa=1 in the response.
This way you could signal that you want both A and AAAA records and
if you don't want both then the response does not have the other
type added.
Yes, we would have to nuke the stupid servers that reflect back
{E}DNS flags. We would also have nuke the stupid firewalls that
block {E}DNS queries with a unknown flag bit set.
Mark
Mark Andrews writes:
>
> Well we really want to get rid of A lookups. Why don't we just
> recommend that we publish mapped A records in AAAA RRsets and have
> master servers update AAAA RRsets if they are inconsitent with the
> A RRsets.
>
> We also need a way to signal that there are no A records in the
> AAAA RRset. ::ffff:255.255.255.255 or ::ffff:0.0.0.0 would be
> sensible records to indicate this.
>
> Mark
>
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
