On 4/16/23 21:40, Franta Hanzlík via users wrote:
You are probably writing about the anonymization of the client - which is a case that still has some kind of substantiation. But in this case the connection specifies the target VPN server somehow (I called it gw.mujsrv.org), but the NM OpenVPN client tries to connect to 1a9107897c24.gw.mujsrv.org, 3abc1fd99dff.gw.mujsrv.org, 85f0005caa82.gw.mujsrv.org, f6046c7831be.gw.mujsrv.org, ... - which, of course, isn't DNS resolvable and thus the connection cannot be established at all. And I don't understand why it does that ;)
The only situation I can see this being useful is if the vpn server has a dynamic address and a wildcard domain, so that you can force a DNS lookup avoiding any cached values. But that seems like a very unlikely situation.
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
