Selva Nair wrote: >> >> Hope this information is sufficient. > > Not really. Sounds like DNS resolution is changing with metric of the > interface which very much points to a WIndows only behaviour. > > And, in that case whether a DNS server is set on the tun interface and > which DNS server gets used when its "working" as expected and when its > "not working" would be relevant. Also whether block-outside-dns is in > use. >
Thanks for the hint Selva. Indeed it looks like something DNS related. The primary wired network interface has 1 IPv4-listening DNS server (192.168.1.1, which uses 2 upstream IPv4-listening DNS server from the ISP). The tun device has 2 IPv4 listening DNS servers (google) and 2 IPv6 listening DNS servers (google) pushed via dhcp-option DNS. When it is "not working", the DNS server from the wired network interface (192.168.1.1) is used. When it is "working", as when the metric for the tun/tap adapter is changed to be lower than primary wired network interface, google IPv6 listening DNS server is used. I imagined that it is a problem because even if the IPv4 listening DNS server from the wired network interface is used, that should still be able to deliver AAAA records for dual-stacked hostnames and then the IPv6 route to be used for anything (ping,traceroute,whatever).
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-devel
