<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
-----BEGIN PGP SIGNED MESSAGE----- <br>
Hash: SHA256 <br>
<br>
<br>
<br>
27.10.2016 0:54, Jok Thuau пишет:<br>
<span style="white-space: pre;">><br>
> On Wed, Oct 26, 2016 at 11:45 AM, Yuri Voinov
<<a class="moz-txt-link-abbreviated" href="mailto:yvoinov@gmail.com">yvoinov@gmail.com</a> <a class="moz-txt-link-rfc2396E" href="mailto:yvoinov@gmail.com"><mailto:yvoinov@gmail.com></a>> wrote:<br>
><br>
><br>
><br>
> Jok,<br>
><br>
> it can be DNS leak. Does you tested it? 8.8.8.8 can be
poisoned (probably) or intercepted by ISP.<br>
><br>
><br>
> DNS is working fine and is not being
poisoned/intercepted/messed with. The records that come back from
the google servers appear to not be consistent (likely due to some
anycast system, and not talking each time to the same "host"). So
when i request the same records back to back, each results in one
record, and that record changes really fast (non-coherent set of
data, so the results are correct, but random). Setting up the
client and the proxy to use a common infrastructure for DNS
(dnsmasq on the network) helped a lot.</span><br>
Yes, this is common and best practice already. I think, time to
write article on Wiki ;)<br>
<span style="white-space: pre;">><br>
> Thanks,<br>
> Jok</span><br>
<br>
- -- <br>
Cats - delicious. You just do not know how to cook them.<br>
-----BEGIN PGP SIGNATURE-----
<br>
Version: GnuPG v2
<br>
<br>
iQEcBAEBCAAGBQJYEPw1AAoJENNXIZxhPexGIW0H/Rk82EjHy/UfQm44SvsHgBeq
<br>
Pw5b1yavLtFNXSpRsLyw8wekepJvLLk1XEtGWbLC33Z3O7REBYXL2nzXD9iNzFbp
<br>
RhdF4aaIgCfp+WqHtVxRgnqoHNAmDs2U7uhJqYmXIubvbFyddRwwh/vS2Ns89/t7
<br>
BK9GuqkkeG4PrGG3ogAX8YpRaE57LaTcDXrOlco5JU/wGkxbMJzUxOvmFyl+0SLI
<br>
4xbUBgEaFFAAmJ46PWm3c8e+zo5O6k2E86asfDJUCMtnKvRPnhce8MxTH8MwkLxl
<br>
GR5UNyVAIpYWlJAqjDRRwYlEcTGfxofyZD3SKKDUP4SduwicdZArBGGirtKUdJA=
<br>
=uXwb
<br>
-----END PGP SIGNATURE-----
<br>
<br>
</body>
</html>