It's not for DNS resolution (although it should work if "DNS Client" service is disabled), it's not to break OpenVPN servers on TCP/UDP port 53.
On 02/04/2016 06:05 AM, Selva Nair wrote: > Hi, > > > I tested this on Windows 10. While it works same as before as far as blocking > dns is concerned, the filter that allows openvpn.exe to do name resolution > through all interfaces does not appear to work. > > When a openvpn connection is running with block-outside-dns and no DNS server > is defined on the TAP adapter, all dns queries fail as expected. But starting > a > second openvpn.exe also fails at name resolution although the apparent > purpose of the permit filter is to allow that traffic through the LAN or any > other > interface > Valdikss: Is this filter useful at all? When openvpn does name resolution, I > suppose its the dns client service that would open the port 53 connection. > > Selva > >
signature.asc
Description: OpenPGP digital signature
