Re: on DNS records

On Wed, Nov 14, 2012 at 5:10 PM, Willy Tarreau <w@1wt.eu> wrote:

>
>
> That was one of the issue I raised several times a few months ago
> explaining why I think DNS alone cannot be a solution.
>
>
it cannot do the job alone - but it can provide the best service (i.e.
similar level of service as NPN on tls) for many best-practice use cases of
http://. Other cases can use an additional approach (alternate-protocol,
upgrade, etc..) which will certainly be necessary to fill in the gaps. SRV
is essentially a routing mechanism, if you're doing routing some other way
(i.e. a proxy, or a port in the URL, or something that manipulates your
dns) then don't use it. We'll need to also provide another option.

But it is totally forseeable to see http://www.example.com/ generate

A? www.example.com

return
A = 10.10.10.10
Additional Records: {SRV _http2-npn._tcp.www.example.com port=443 host=
www.example.com ,
                              SRV
_http2-cleartext._tcp.www.example.comport=81 host=
www.example.com}

and that's a pretty darn powerful sequence that should imo be enabled.

(obviously there are other incantations that don't require the additional
record.. the A and SRV lookups in parallel for instance.. but that's all
implementation dependent.).

I dare say we've been over all this ground. To move things forward on my
part, I have a PoC implementation as a todo item but its going to have to
wait several weeks for other prior commitments to clear.