But that's a really nasty hack. Dnsmasq is sending the query to the
internal DNS via UDP, which is unreliable, so when a UDP packet is lost,
you'll get a random wrong answer to a DNS query that should have been
answered by the internal DNS server.
Cheers,
Simon.
On 21/02/18 13:40, Karol
On 2018-02-21 12:47, Simon Kelley wrote:
> In general "don't use --strict-order" is good advice. In hindsight I
> would never have provided that option.
>
>
> Simon.
>
Hi Simon,
This option has many use cases when you want to mainly use one DNS
server and only allow fallback in case of
Ah, that's correct! I missed this in the manual.
Thanks a lot.
--
Sent with ProtonMail Secure Email.
Original Message
On February 21, 2018 1:19 PM, Simon Kelley wrote:
>I'll take a guess that you have --strict-order in your config.
>
> If so,
In general "don't use --strict-order" is good advice. In hindsight I
would never have provided that option.
Simon.
On 21/02/18 12:43, meht...@protonmail.com wrote:
> Ah, that's correct! I missed this in the manual.
> Thanks a lot.
>
> --
>
>
> Sent with ProtonMail Secure Email.
>
>
>
I'll take a guess that you have --strict-order in your config.
If so, remove it and all will be well.
Cheers,
Simon.
On 21/02/18 08:19, meht...@protonmail.com wrote:
> Hello,
> is it possible for dnsmasq to prioritize upstream DNS servers based on
> their availability?
> I have 2 servers in