VPN domain lists for Keenetic
Choose what goes through your VPN. Keep the rest on your regular connection.
Set up DNS-based routes
Before you start
Use KeeneticOS 5.0 or later with an already connected VPN. Give your ISP connection higher priority than the VPN. Keep the client in the Default policy and use the router as its DNS server; client DoH or Private DNS can bypass it.
- Under Routing, open DNS-Based Routes. Create a Domain Name List for each TXT file and paste its contents, one hostname per line. Names include their children; do not add an asterisk.
- Create a routing rule for each list, select the connected VPN interface, enable Add automatically and save the enabled rule.
- Optional: Exclusive route stops fallback when that VPN interface is unavailable. Test the chosen sites after clearing the client's DNS cache.
What these lists do and do not do
These are domain lists, not BAT routes or a VPN configuration. A shared IP or CDN may also route unrelated traffic. Apps that connect directly to IP addresses may bypass domain matching. Catalogue inclusion does not mean a service is blocked, nor guarantee every app feature will work.
Catalogue and sources
The catalogue combines community domain data from V2Fly and IPList. Review the selection for your needs. Regenerate and replace router lists manually when needed; they do not subscribe to updates.
V2FlyIPListSources and licencesSource SHA (JSON)tldts / fflate