Paul Vixie <[email protected]> wrote: > > Tony Finch <mailto:[email protected]> > > Sunday, November 30, 2014 6:26 AM > > > > You can do that with the current DNS protocol: just send all the queries > > and wait for all the replies. (This is particularly easy over TCP.) > > There's no need for more than one round trip in most cases, or maybe two > > if the answer involves CNAME/MX/SRV etc. > > so, you're willing to send a query for every ancestor domain, even the > ones that turn out not to be zone cuts.
That will usually be only one, and the server will have to send back a proof of no zone cut whether you ask for it separately or as part of a bulk query. > you're also willing to transmit microburst UDP, or to depend on RDNS > servers having effectively unlimited TCB capacity. i am not hip to any > of that. Those are fair complaints. However your initial reason was latency, but chain queries do not improve latency compared to the current protocol. And chain queries will often require TCP so your TCB complaint applies to them as well. (And if you start with UDP and have to do a TCP fallback you lose the latency benefits.) Tony. -- f.anthony.n.finch <[email protected]> http://dotat.at/ Lundy, Fastnet, Irish Sea: Variable 4, becoming north 5 to 7, perhaps gale 8 later. Slight or moderate, occasionally rough later. Fair then rain. Good, occasionally poor. _______________________________________________ dns-operations mailing list [email protected] https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
