Firefox + NextDNS + Windscribe on macOS
This is a question regarding a configuration that I am trying to get it work. However I might be wrong and it can't be done, let me know.
1. macOS 12.4 with NextDNS configuration profile installed.
2. I installed Firefox 101.0.1 and I configured the connection settings with my NextDNS profile.
3. Finally I installed Windscribe VPN extension within Firefox.
4.Issue: when I check my NextDNS page or when I do a DNS leak, NextDNS isn't active. Windscribe DNS is taking over.
Strangely I don't have this problem with Safari. The only difference is that Windscribe desktop is installed because there is no extension for Safari.
So why isn't working on Firefox? Thanks for the help and advices.
9 replies
-
If you have the apple config profile installed you shouldn’t need to have DoH set in Firefox.
What happens if you disable the windscribe extension and use the desktop version? (i.e. like the Safari setup)
-
R P M +1 pretty sure that the native implementation is taking over the VPNs DNS but when the Proxy is crested in the browser it might not take over. You could check the settings on the extension to see if they have a manual DNS option.
-
R_P_M
Sorry I should have mentioned that I obviously tried it and it worked.
Also, I should have mentioned that opted 'Prohibit Disablement' when downloading the configuration file. So, I thought Windscribe couldn't take over NextDNS. I guess I was wrong.
@hey
There is not proxy created from Windscribe extension and the proxy is not used in the settings. Also, the extension doesn't offer a DNS configuration. However, Windscribe desktop offers such option and it has been configured with NextDNS DNS address.
Nevertheless, if I activate WS desktop and WS extension in Firefox, WS DNS is still taking over NextDNS. So, I am just back to square one. But maybe what I want to achieve is just impossible.
-
Pierre Cartier What exactly are you trying to achieve? Why use the browser extension when desktop works, is there some benefit?
-
Pierre Cartier The extension has Robert that's also a DNS AdBlock of sorts. So if that's turned on could be an issue. If that all doesn't work maybe try to use another VPN provider as some VPNs take over the DNS and some don't.
I also have the same question that RPM has, why use the extension since the App has full VPN functionality when the extension from what I know does a proxy.
-
R P M It adds an extra layer of security with multihop connectivity.
-
Hey ROBERT isn't the issue here. It is integrated on WS DNS server level. As I mentioned no issue with the desktop application even with ROBERT activated on my account.
WS extension adds ublock Adblock though on the browser layer. However I don't care about it as because I am using AdGuard on FF and Safari and also the desktop application where, guess what, NextDNS is also configured :)
As I told RPM the extension offers multihop.
Still I don't understand that WS DNS succeeds to connect when NextDNS is configured on my router and on my Mac in macOS network settings and with the configuration file and within AdGuard desktop. Not mentioning that DNS bypass is also checked. So it is just incredible that WS still can get through.
-
-
Pierre Cartier said:
So it is just incredible that WS still can get through.Not really, with tunnelling involved all data can go through without the need for system DNS. With it being a browser extension it’s pretty easy.
-
Then, I guess I will stay with Safari
Content aside
- 1 yr agoLast active
- 9Replies
- 154Views
-
3
Following