Using custom DNS whilst VPN Policy Based on the Target Domain or IP is configured

Technical Support for Routers
23

Thanks, I will try to upgrade and test later

edit: confirmed this works on a clean install of beta 3

1 Like
24

Reported in Flint 2 (GL-MT6000 ) - bug reports - collective thread - #2179 by Pro4TLZZ

25

fixed in Flint 2 (GL-MT6000 ) - bug reports - collective thread - #2209 by hansome

26

Thanks for the report and confirming much appreciated.

27

Actually I did try the 4.6.0 snapshot 2024-06-18 18:04:32 (UTC+00:00) now.

Before I had just switched back to beta 3 4.6.0.

In the situation now the DNS leaks the same on both DNS Leak Test - BrowserLeaks & https://www.dnsleaktest.com/results.html.

image
image1093×1135 258 KB

image
image1093×1135 62.2 KB

cat vpnpolicy 

config policy 'global'
	option kill_switch '0'
	option wan_access '0'
	option service_policy '1'
	option vpn_server_policy '1'

config service 'route_policy'
	option proxy_mode '3'

config policy 'vlan'
	option private '1'
	option guest '1'

config policy 'domain'
	option default_policy '0'
	option manual '1'
	option domain 'browserleaks.com
browserleaks.org
browserleaks.net'

cat adguardhome 

config adguardhome 'config'
	option enabled '1'
	option dns_enabled '0'

Maybe this is a separate snapshot bug? Is there a way to test the op24 with the snapshot fix?

Either way I shall return to beta 3 4.6.0 for now and hope that gets released soon

@hansome