After update a lot of failed DNS requests

[Geier97332]

Hi,

I'm using latest version 1.01.61 and with this version I'm getting a lot of failed DNS requests. Furthermore every two minutes the connection is unstable and the latency is very high while trying to resolve my address.
Before there were no DNS requests and the connection was stable.

I use an AdGuard Home AdBlocker in my network and all the DNS requests a routed to that, but in that log I can't see any failed requests. Also, I configured max handshakes to value 2 before reconnecting.

Can I revert back to older version or can I toggle off the new DNS requests?

Thanks and best regards!

[admin]

Hello

thanks for the bug report and sorry for the issue

The problem was due to a change made to resolve the VPN server hostname outside the VPN, but unfortunately it seems that on some devices this change creates side effects.
The problem will be resolved as soon as possible.

In the meantime, you can replace the hostname of the VPN server with its IP address. This should fix the problem...

[Geier97332]

Hi,

thank you for your fast response.

I cannot change the IP, because my IP is changing every night so that I must use dyndns.

At the moment I can live with the situation and can wait for the next update.

Best regards

[admin]

You're welcome.
The problem should be fixed in the new release 1.01.63.
Please, update the app...

[Geier97332]

I updated and the DNS requests timeouts are gone. But I still can't resolve my hostname. It always uses the last known address.
As I remember in previous versions there were always ipv4 addresses (I only use and have configured ipv4 and toggled on the option to block not configured ipv4/ipv6 protocol.

Update:
I often toggled on and off VPN and sometimes there is my ipv4 address in the log and sometimes my ipv6, but in both cases it can't resolve the hostname und uses the last known address.
In the attachment you'll see the ping times to my home router. Every two minutes or so when it tries to resolve my hostname the ping times increase significantly and the connection is unstable.

[admin]

Thank you for the feedback.

The problem switching from ipv4 to ipv6 should be due to an inadvertent change in the configuration on the client:

• edit the VPN profile

• tap on "Peers"

• tap on peer's hostname

• change the protocol to "UDP4"

• save the changes

The problem of the name not being resolved is instead due to an oversight on my part, but it can be solved manually in a simple way:

• edit the VPN profile

• tap on "App filter"

• edit the VPN profile

• set "App filter mode" to "The VPN can be use by any apps, except for the following apps

• tap on "+" button

• search for "VPN Client Pro" and tap on it

• save the changes

In the next version I will make sure that this manual intervention will be not necessary

[hvbakel]

Thanks for the quick resolution. With the changes above my wireguard VPN is working again.

[admin]

You're welcome.
Thanks for the feedback.

[Geier97332]

Thanks for the infos und guides. Now everything is working again without any problems!

Keep up your work! Your support is perfect and your app amazing!

[admin]

You're welcome.
Thank you!