Hi,
On Thu, May 4, 2017 at 1:36 PM, ValdikSS <valdi...@gmail.com> wrote:
>
> Windows 10 before Creators Update used to resolve DNS using all available
> adapters and IP addresses in parallel.
> Now it still resolves addresses using all available adapters but in a
> round-robin way, beginning with random adapter.
>
Hmm... If it starts with a random adapter, this metric lowering is not the
right fix, isn't it? Or did you mean to say "starting from lowest metric
adapter"?
> This behaviour introduces significant delay when block-outside-dns is in
> use.
> Fortunately, setting low metric for the TAP interface solves this issue,
> making Windows always pick with TAP adapter first.
Well, I'm looking for to excuses to avoid the hard work of a careful review
:) If reducing metric is indeed the right approach in this cat and mouse
game with MS, I'll try to look through this over the weekend.
Selva
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
