No actual DNS lookup but cached wrong remote IP address #502
Description
Describe the bug
OpenVPN connect does not resolve myhost.hopto.org to its correct A and AAAA record. Instead it has some cache that point to a wrong IP.
TCP/UDP: Preserving recently used remote address: 185.....
That IP seems to be a Turkish IP I never had any connection to.
On the same client, nslookup in terminal for myhost.hopto.org does not resolve the wrong IP but gives the correct A and AAAA record.
Background info:
We switched from pfsense to OPNsense, so clients had a working VPN config before.
I deleted the old config and inserted the new one. Configs are under program files, because users don't have admin right.
To Reproduce
- Start OpenVPN connect with a new config
- Connect
- See "Preserving recently used remote address: and wrong IP" in logs
Expected behavior
Do an actual A or AAAA record lookup.
Version information (please complete the following information):
- OS: Windows 11
- OpenVPN version: 2.6.9
Additional context
By manually inserting an IP instead of a FQDN, I found a funny workaround that solves the problem.
- Change config from myhost.hopto.org to 1.1.1.1
- Try to connect and of course fail
- change config it back to myhost.hopto.org
- Now it works