DNS error

Gidro76

Good afternoon. When connecting to an openvpn server, the DNS server stops responding after a while. There are no disconnections or losses. After the reconnect, the DNS is immediately restored and continues to respond for some time. Has anyone encountered this and how did you resolve it? Mac can be both on m1 and on intel processors. Repeats everywhere

ordex

Is the DNS in question reached over the VPN or on the LAN? If it's on the VPN, maybe it's the tunnel that is getting disrupted.

openvpn_inc

Hello Gidro76,

Additional, is this only occurring on macOS Ventura? And which client is being used? And which server?

Kind regards,
Johan

Gidro76

ordex wrote Is the DNS in question reached over the VPN or on the LAN? If it's on the VPN, maybe it's the tunnel that is getting disrupted.

DNS is reached and working. After a certain amount of time, it ceases to be available. At the same time, there is a vpn connection. As an example, internal resources become unavailable. Nslookup on internal resources fails

Gidro76

openvpn_inc wrote Hello Gidro76,

Additional, is this only occurring on macOS Ventura? And which client is being used? And which server?

Kind regards,
Johan

I can't confirm that only in MacOS Ventura. The version specifically on such clients was updated to 3.4. The server is using version 2.5.6

wesleykirklandsg

I also am having this one Ventura under 13.0.1. My DNS resolver will fail anywhere from 15 seconds to an hour. Most of the time it seems to fail within 15 minutes. My work is requiring a VPN for most things and I'm reconnecting around 20 times a day. Everything worked fine on Monteray.

Build: Version 3.4.0 (4506)

openvpn_inc

Hello,

While not entirely consistent, it does seem that on Ventura something changed with DNS that seems to break things, but it's not sure yet. We're gathering information. I don't have anything further than that to report unfortunately.

Kind regards,
Johan

Gidro76

openvpn_inc wrote Hello,

While not entirely consistent, it does seem that on Ventura something changed with DNS that seems to break things, but it's not sure yet. We're gathering information. I don't have anything further than that to report unfortunately.

Kind regards,
Johan

Good afternoon. Did you manage to find out anything?

openvpn_inc

Hello Gidro76,

Yes, we believe we've found a solution but it requires a new macOS release. We're now testing this and preparing it for a release. It's always a little difficult to estimate when a release can be made because if issues are found during testing the release may need to be pushed until later. However I am expecting a release to become available in the next week or so that should solve this. I'll try to remember to update this thread once it's out.

Kind regards,
Johan

Gidro76

openvpn_inc wrote Hello Gidro76,

Yes, we believe we've found a solution but it requires a new macOS release. We're now testing this and preparing it for a release. It's always a little difficult to estimate when a release can be made because if issues are found during testing the release may need to be pushed until later. However I am expecting a release to become available in the next week or so that should solve this. I'll try to remember to update this thread once it's out.

Kind regards,
Johan

Thanks a lot for your answer
Waiting for your decision then

openvpn_inc

Hello everyone,

We have released a new macOS OpenVPN Connect v3 build version 3.4.1 that enables a watchdog function for DNS settings. So if some process resets these DNS settings implemented by OpenVPN Connect, they should automatically be corrected again.

You can obtain the latest version here:
https://openvpn.net/client-connect-vpn-for-mac-os/

Kind regards,
Johan

izhmurikov

we have confirm from users - problem is solved

freerk

I had the same issue before 3.4.1, it then got fixed but now occurs again (exact same symptoms, DNS getting forgotten after a few minutes) since 3.4.4. Is there a possibility to get back to 3.4.1 until the issue is fixed?

JosephS

Hi freerk,

It's true that this issue has re-emerged with the release of v. 3.4.4 on macOS.
However, it has been fixed once again with 3.4.6.

With Regards,
Joseph