Comment 17 for bug 1745463

Hello,

On Tue, Nov 26, 2019 at 04:42:44PM -0000, Thayne wrote:
> Maybe there is a better way to do this, but here is my situation. I need
> to be able to send DNS queries to multiple dns servers in parallel and
> use the first response I get back (so that I use the fastest/closest dns
> server).

That's a pretty unusual requirement, which at the very least means that more
of your bandwidth is being used for DNS traffic than would otherwise be the
case. Can you help me understand the motivation underlying the requirement?
Do you have DNS servers in your configuration which are always farther /
slower? If so, why do you have them in your configuration at all? Do you
have a particular application requirement for low-latency DNS resolution -
and if so, wouldn't the use of a caching local resolver (a configuration
which resolved supports, and which we enable by default) have more of an
impact on satisfying that requirement?

We should certainly ensure that your use case is addressed with resolved
itself, and without the need to run dnsmasq as an alternative local
resolver.