On 23/08/2022 16:45, Peter Thomassen wrote:
I think their point is that the application (e.g. browser) may be
agnostic of the resolution system (= accept the name), but resolution
may fail because something switching layer like nsswitch would choke
on a non-DNS-style name, *even when* the downstream non-DNS resolver
would be available.
So, by making the non-DNS names DNS-style, one can allow for more
agnostic intermediate layers in the process that make DNS-like
assumptions.
Yes, that's in part what I was trying to say, although it may also apply
to stub-resolver-like functionality that is part of a userspace library.
Ray
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
