Hi Michael, On 7 Nov 2025, at 16:50, Michael Richardson <[email protected]> wrote:
>> So >> this is an example of a chained resolver processing a query. > > I'm not familiar with such a configuration; I guess it's a forwarders thing? It's usually a forwarder with a cache thing. >> 3. Change resolver behaviour. Resolver B SHOULD return a more useful >> signal than SERVFAIL, maybe with an EDE or something. Resolver A SHOULD >> avoid retrying if it receives such a signal. This would avoid the >> behaviour Mark is concerned about in this draft, but would also clean >> up other uses of the hostname ".". The camel is slightly sad, but >> perhaps it's worth it to avoid the cost of retries for all the cases >> where "." is used in place of a real hostname to mean "not provided". > > Can we do both? > Return NS ., but also EDE? The job of the resolver is to follow a referral, not to return it. Joe _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
