VPN Policy Domain filtering

Dear GL Development team,

Please look for possibilities of reconstructing VPN domain filtering like below.

Existing:

Domain: google.com

action: Any subdomain will be redirected i.e., *.google.com

Proposed:

domain: google.com

action: only google.com should be redirected

note: if user mentions *.google.com then any sub-domains should be considered, and any other VPN policy have 123.google.com then this should be more preferred than *.google.com in other VPN policy.

Having this proposed domain filtering reconstructed will give users flexibility to redirect specific subdomain traffic.

@bruce please for your support.

Gl.Inet has Chinese New Year Celebrations and staff will not be responding this week due to public holidays etc. I am sure you will get a response as soon as possible when normal working resumes.

https://forum.gl-inet.com/t/chinese-new-year-holiday-notice/

2 Likes

Hello,

Although wildcard * is not supported, but subdomain routing for patterns like *.google.com is actually supported.


You can give the tunnel for a subdomain (for example mail.google.com) a higher priority so it will be matched first (for example Tunnel 1).
Other subdomains (*.google.com) will then use Tunnel 2 or lower.

2 Likes

Thanks @bruce much appreciated :clap: