On Apr 4, 2018, at 11:49 AM, Paul Vixie <p...@redbarn.org> wrote: > this is a far thinner solution than a full-service resolver, which would > require local configuration and monitoring and so on, as well as topology > stability that can't be guaranteed.
For your laptop use case, why wouldn't you just have the thing running on the laptop do truncation if the answer is too long? I admit that this is more code, but it's not a lot more code, and what you're doing instead is pretty hacky. The fact that it's not required to implement doesn't mean that it doesn't contribute to the camel problem.
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
