Ranger802004
Very Senior Member
No I don't believe so@Ranger802004, Do you have particular recommendations for this option in ?Does this setting make any difference in your script given the frequency of lookups?
No I don't believe so@Ranger802004, Do you have particular recommendations for this option in ?Does this setting make any difference in your script given the frequency of lookups?
I am not sure if it's been testing by any user but if you want to test and provide feedback I'll surely take a look.Hi,
Could you please confirm that Domain VPN Routing works well with Unbound installed?
Thank you,
amplatfus
Thank you for the timely update. I cannot seem to update from the latest beta version to this one nor can I uninstall the previous version of the script to be able to install the new one. Any help would be greatly appreciated.***v3.2.2 has been released to the production channel***
Release Notes:
v3.2.2 - 08/06/2025
Fixes:
- Fixed state_desc error in generateinterfacelist function.
- Fixed Major Version reported
- Added retry loop for query ASN with delay on additional attempts.
- Reverse Path Filtering configuration has been updated to properly set for all WAN interfaces regardless if policy for interface exists.
- Added logic to save over blank IPSet files
Open an issue on GitHub.Thank you for the timely update. I cannot seem to update from the latest beta version to this one nor can I uninstall the previous version of the script to be able to install the new one. Any help would be greatly appreciated.
What's the value of your VPN Client configuration option "Accept DNS Configuration"?Is there any configuration to resolve the DNS leak issue?
What's the value of your VPN Client configuration option "Accept DNS Configuration"?
Make sure you provide this value from the same VPN client you're using in the script for that domain.
I believe this issue is caused by your VPN Client configuration not the DomainVPNRouting script.
The option should be "Exclusive" to always use the DNS of your selected VPN location exclusively, which prevents using your WAN's DNS servers.
This option is available for OpenVPN clients and I use it in my setup (see attachment). Now I guess it's a bit different for WireGuard clients.I can't see "Accept DNS Configuration" in WireGuard Client
This option is available for OpenVPN clients and I use it in my setup (see attachment). Now I guess it's a bit different for WireGuard clients.
I can't help anymore as I don't have WireGuard feature in my own router. We need this to be answered by other members or the script owner. I'm interested in getting to know the solution for future usage.
If you have just setup your VPN using an OpenVPN client instead of a WireGuard client, you need to update the interface used into the Policy which has your desired domains inside DomainVPNRouting script.even I set "Exclusive" in OpenVPN client , it still leak my DNS Geo info
If you have just setup your VPN using an OpenVPN client instead of a WireGuard client, you need to update the interface used into the Policy which has your desired domains inside DomainVPNRouting script.
So, now make sure you're using the OpenVPN interface you just setup, into the DomainVPNRouting's policy you're using for TikTok domain(s).
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!