System-Wide and Additional VPN Not Working Correctly

B

Bob1234567

New Member
@avatar @vasily_bagirov

I am starting a new thread to hopefully get some response on this. I am using Windscribe VPN and Adguard Pro for iOS.

When first connecting to Adguard and then Windscribe DNS traffic is not sent through Windscribe at all. Which I think is why it is blocking ads. But this setup is leaking all of my DNS traffic to my ISP. It is my thinking that it should run like this: Adguard sees DNS requests, blocks bad ones, sends the rest through to the other VPN.

I've tested this by connecting to Adguard and then windscribe. Running tests at ipleak.net show my real ISP's dns service instead of my windscribe dns. But shows windscribe IP address.

If I connect to windscribe first and then Adguard, ipleak shows my windscribe dns but no ads are blocked by Adguard. Which is where I'm having problems.

I would imagine it is the same for other VPN that Adguard is "compatible" with but I don't know. Maybe it's a Windscribe problem but hopefully it's fixable.
 
avatar

avatar

Administrator
Staff member
Administrator
Here is a question then, what if you set AG to use Windscribe DNS along with the system-wide ad blocking?
 
B

Bob1234567

New Member
avatar said:
Here is a question then, what if you set AG to use Windscribe DNS along with the system-wide ad blocking?
Click to expand...
This was a good thought, sadly no matter which way everything is activated this lets ads through. When I run the tests it does show the correct ip and dns addresses though.

Even running only Adguard system-wide and the windscribe dns, ads are not blocked.

Windscribe does offer a free service, so this should be replicatable I would hope
 
B

Bob1234567

New Member
avatar said:
Filed an issue about it:
https://github.com/AdguardTeam/AdguardForiOS/issues/397
Click to expand...
Ok so after more testing I think I had the wrong server that I put in. I also found that any DNS I chose from the other options would work and block ads. So I found the correct DNS servers for Windscribe and put those in as custom and it IS working.

However, I feel this is a work around for and that the original issue still stands from a product standpoint. Unless you guys think this is how it should work.
 
B

Bob1234567

New Member
vasily_bagirov said:
@Bob1234567 sorry it took us so long. We performed the test and can confirm the behavior you had described. Unfortunately, we can't do much here besides updating this task where we keep track of VPN compatibility: https://github.com/AdguardTeam/AdguardForiOS/issues/162
Click to expand...
@vasily_bagirov Thanks so much guys, I appreciate the effort! Are you saying though that there is no way to fix this? Or you are looking into it?

Also would this not be the same behavior with all of the other "compatible" VPNs that are on the linked list?

Further I think your update to that list is misrepresenting Windscribe as being "incompatible." I am currently using it and it's working great, it just takes more configuration (using Adguard to point to Windscribe's DNS). I'd hate for you guys to lose out on pro purchases from users of Windscribe when it is "working"
 
vasily_bagirov

vasily_bagirov

Administrator
Staff member
Administrator
@Bob1234567 there's always a chance we will find a fix for this, but this task doesn't have the highest priority.

Also, your point is valid and I will move it to the 'compatible' VPNs with the respective comment.
 
You must log in or register to reply here.
Top