Jump to content


[Windows-only] Why in special cases DNS of IPv6 are not pushed by our server

  • This topic is locked This topic is locked
No replies to this topic

#1 Staff


    Advanced Member

  • Staff
  • PipPipPip
  • 7755 posts

Posted 31 January 2018 - 03:01 PM

[Windows-only]Why in special cases DNS of IPv6 are not pushed by our server

This topic explains why, only with Microsoft Windows and only if Eddie is a version <2.14.1, our servers don't push DNS6
OR why Eddie sometimes shows this message:
Detected an OpenVPN bug (On-Link route on VPN range), autofix.


This issue occurs ONLY under Windows.

Sometimes (the problem is not systematically reproducible) after the VPN connection, inside IPv6 routing table entries you can see routes in identical ranges with different gateways:
>route -6 print
 38    259 fde6:7a:7d20:16::/64     On-link
 38    259 fde6:7a:7d20:16::/64     fe80::8
When this occurs, DNS6 can't be reached with subsequent delays and issues.
>ping fde6:7a:7d20:16::1

Pinging fde6:7a:7d20:16::1 with 32 bytes of data:
Destination host unreachable.
We think the problem is caused by an OpenVPN bug (at least in 2.4.4), currently under investigation.

Current workaround

Eddie automatically detects the issue and resolves it.

For those who don't use Eddie (and generate .ovpn files with Config Generator), our servers don't push DNS6 directive if Windows (or older versions of Eddie) is detected, until the issue is resolved in OpenVPN code.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

Servers online. Online Sessions: 16248 - BW: 67266 Mbit/sYour IP: Access.