Write the website name
Use *.example.com for a whole site, or *keyword* when the domain only needs to contain a word.
Choose how each website opens
dns-flow
Set dns-flow once in your browser, then decide which websites go direct, use a proxy, use private DNS, or get blocked.
One entry
127.0.0.1:5353
Set the browser to dns-flow once, then manage changes in the app.
Many routes
DNS / DoH / Proxy / Block
Use plain website rules to decide how different sites should open.
Built for checks
Request records
Check which rule was used when a website does not behave as expected.
How it works
Three steps: start dns-flow, add rules, check the result.
01
Create a routing profile
Create a profile, start it, and point your browser to the local address shown by dns-flow.
02
Add website rules
Add domains such as *.example.com, then choose direct, proxy, private DNS, or block.
03
Review requests
Open the website and use request records to see whether the rule matched.
Rule basics
Most rules can be written like everyday website lists.
Choose what should happen
Pick direct/system DNS for normal access, proxy for selected sites, DoH for private DNS lookup, or block for sites you do not want opened.
Open the site and look at records
The request record tells you which rule matched, so you can adjust the expression without guessing.
Examples
Start with these common patterns.
*.company.com
Let all company internal pages use direct or system DNS.
*video*
Send domains containing "video" to a chosen proxy.
ads.example.com
Block an exact advertising or tracking domain.
When you need more control
Simple rules first, advanced routing when a website needs special handling.
Website routing
Group websites by domain name and choose a clear action for each group.
Post-resolve routing
For advanced cases, resolve first and continue by country, CIDR range, or private/public address scope.
LAN adapter binding
Keep local network devices reachable through a selected physical adapter when proxy or VPN tools are active.
Diagnostics
When a website behaves differently, start with the request record.
The request log shows the domain, profile, matcher, rule remark, target, and status so routing issues are easier to explain.
Screens
Screens for the daily workflow.
Create a profile, add website rules, inspect requests, and adjust settings from one desktop interface.
Download
Start with one browser profile and a few website rules.
Download dns-flow from the release page, start a routing profile, then point your browser to the local address shown by the app.