On Mon, 2023-04-17 at 06:40 +0200, Franta Hanzlík via users wrote: > 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. For that kind of thing (I'm assuming some kind of load balancing, so people don't always use the same server), it being resolveable would have to be an issue that *their* end would have to solve. By your example, their DNS server for gw.mujsrv.org would either know what to do with the hashed subdomain, or simply ignore it and return a random IP for a particular host. Or, perhaps it works like virtual webserving: With webserving, that sort of thing would be all subdomains for that domain have the same IP, and different virtual webserver respond to different subdomains. But looking at this as an outsider, all I can see is that for it work, all the addresses would have to resolve, and *they'd* have to be the one managing that. If I try "dig gw.mujsrv.org" there is no results returned. Perhaps they have a fault at the moment, or is that a faked example? -- uname -rsvp Linux 3.10.0-1160.88.1.el7.x86_64 #1 SMP Tue Mar 7 15:41:52 UTC 2023 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. _______________________________________________ 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
