having DNS issues with the new Kaspersky VPN Wire Gaurd update version 21.23.6.614-2

[User23837]

Specifically i try connecting to Canada - Toronto, which works but then i try connecting to dnsleaktest.com and i try and get this:

nslookup dnsleaktest.com
Server:  unn-149-50-222-3.datapacket.com
Address:  149.50.222.3

*** unn-149-50-222-3.datapacket.com can't find dnsleaktest.com: Server failed

so i had to go into the network adapter called "Kaspersky VPN WG Nt Adapter Tunnel" and manually set the DNS to 1.1.1.1 (Cloudflare’s DNS) and 8.8.8.8 and had to set "obtain ip address automatically" in the ipv4 properties.

im guessing there is a configuration issue on kaspersky's end since its a new vpn update? I also tried to set the firewall inbound UDP remote ports to allow any address from 53 and 51820 (supposedly a wire guard default port) i also tried with TCP ports but that didnt work. 

I hope this helps admin to realize and fix it, but yeah right now your VPN's DNS is kinda working for some sites and not for others.
also sad to see you removed montreal server, now theyre all gonna flock to toronto :c

also trying to use "Fastest Server" results in connecting to Bangladesh and having my ip show in paris, like what? lol

[Danila T.]

Hello,

Please contact us via:

https://support.kaspersky.com/b2c/#contacts

[NightWlkr]

9 hours ago, User23837 said:

Specifically i try connecting to Canada - Toronto, which works but then i try connecting to dnsleaktest.com and i try and get this:

nslookup dnsleaktest.com
Server:  unn-149-50-222-3.datapacket.com
Address:  149.50.222.3

*** unn-149-50-222-3.datapacket.com can't find dnsleaktest.com: Server failed

so i had to go into the network adapter called "Kaspersky VPN WG Nt Adapter Tunnel" and manually set the DNS to 1.1.1.1 (Cloudflare’s DNS) and 8.8.8.8 and had to set "obtain ip address automatically" in the ipv4 properties.

im guessing there is a configuration issue on kaspersky's end since its a new vpn update? I also tried to set the firewall inbound UDP remote ports to allow any address from 53 and 51820 (supposedly a wire guard default port) i also tried with TCP ports but that didnt work. 

I hope this helps admin to realize and fix it, but yeah right now your VPN's DNS is kinda working for some sites and not for others.
also sad to see you removed montreal server, now theyre all gonna flock to toronto :c

also trying to use "Fastest Server" results in connecting to Bangladesh and having my ip show in paris, like what? lol

Might wanna be careful swapping out that DNS.

That being said, DNS IS messed up since the update yeah. We need a fix please and thank you. 😉

[User23837]

10 hours ago, Danila T. said:

Hello,

Please contact us via:

https://support.kaspersky.com/b2c/#contacts

i did :)

 

4 hours ago, NightWlkr said:

Might wanna be careful swapping out that DNS.

That being said, DNS IS messed up since the update yeah. We need a fix please and thank you. 😉

not sure why to be careful, not sure how to be careful.

I did notice that keeping the first DNS address as their server then changing the backup to 1.1.1.1 seems to work best, and needs to be done manually and not by a script (unfortunately you need to do this every time you connect), checking the validate settings upon exit seems to help.

 

[NightWlkr]

1 hour ago, User23837 said:

i did 🙂

 

not sure why to be careful, not sure how to be careful.

I did notice that keeping the first DNS address as their server then changing the backup to 1.1.1.1 seems to work best, and needs to be done manually and not by a script (unfortunately you need to do this every time you connect), checking the validate settings upon exit seems to help.

 

Simply because using another DNS server might expose your data. You're sending you request to a public DNS server.
Even tho it should still be tunneling through the VPN, There a chance it might also leak out.

If you're not using all kaspersky's parameters it kind of defeats the purpose of using a VPN.
I'm afraid kaspersky needs to fix it or at least reach out to whoever next in the chain.