What the sources actually say
The official English documentation for bol-van/zapret defines two families of targeting filters. Hostlist filters match by hostname: --hostlist applies DPI desync only to the listed hosts, one host per line, with subdomains included automatically unless a line is prefixed with ^, while --hostlist-exclude does the opposite. There is also --hostlist-auto, which builds a hostlist automatically after repeated connection failures. Gzip-compressed lists and multiple lists per profile are supported.
Ipset filters work at the IP layer instead of the name layer: --ipset is an include filter and --ipset-exclude an exclude filter, each taking a file with one IP address or CIDR subnet per line, with both IPv4 and IPv6 accepted. The documentation notes an important caveat for Windows users: the user-mode ipset implementation was not designed as a kernel ipset replacement. It exists for systems that lack kernel ipset support, and the kernel version is much more effective.
In the Flowseal zapret-discord-youtube Windows build, the lists directory ships with list-general.txt and list-exclude.txt for domains, and ipset-all.txt and ipset-exclude.txt for IP ranges — we verified these files are present in the repository. The build README explains that user-editable files named with a -user suffix, such as list-general-user.txt and ipset-exclude-user.txt, are created automatically on first run so your additions survive list updates.
The practical guide places these files in C:\zapret\lists and gives an operational rule: after any change to the lists, reinstall the service through service.bat so the running configuration actually reloads them.
How the lists work, step by step
- The bypass engine (nfqws on Linux, winws on Windows) inspects outgoing traffic and tries to learn the target: the destination IP first, and the hostname once a TLS ClientHello or HTTP request reveals it.
- Hostlist filters are checked against that hostname. A plain entry like example.com also covers its subdomains; a ^ prefix disables that automatic subdomain matching, per the official parameter reference.
- Ipset filters are checked against the destination IP or subnet, independent of the hostname, so they can match traffic whose hostname is never visible.
- Exclude lists win over include lists for their entries, which is how the build keeps private or local ranges out of the bypass.
- With --hostlist-auto, the engine adds a hostname to an automatically built list only after repeated failures — the documented defaults are 3 failed attempts within 60 seconds, with a retransmission threshold of 3.
- In the Flowseal build, the IPSet Filter switch in service.bat selects the mode: none means no IPs are filtered, loaded means IPs are checked against ipset-all.txt, and any means every IP matches — the README warns that any breaks many ordinary sites and should not be used permanently.
Issue #6888 (opened 2025-12-03, version 1.9.0b, now closed) describes a user whose ipset switch stayed at loaded and whose ipset-all.txt contained the entry 203.0.113.113/32, which reappeared after deletion and relaunch — while friends on the same build had an empty file. Their ipset-exclude.txt held private ranges such as 10.0.0.0/8, 127.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 and 169.254.0.0/16. A single report, but it shows list contents can differ between installations and be regenerated by the build itself.
What is source-backed vs community-reported
- Source-backed (official documentation): the --hostlist, --hostlist-exclude, --hostlist-auto, --ipset and --ipset-exclude parameters, the one-entry-per-line formats, the ^ subdomain prefix, gzip support, and the user-mode ipset caveat.
- Source-backed (build README and practical guide): the names of the shipped list files, the auto-created -user files, the IPSet Filter modes, and the rule to reinstall the service after editing lists.
- Community-reported (Issue #6888): the stuck ipset switch, the reappearing 203.0.113.113/32 entry, and the differing list contents between two installations of the same build.
When the reported workaround may not apply
List contents and menu behavior change between build versions, so a list file described in a December 2025 issue may not match what a current release ships. Editing a shipped list directly is fragile because update functions can regenerate it — the -user files exist precisely to avoid that. And because the user-mode ipset on Windows is documented as less effective than kernel ipset, behavior observed on Linux routers does not transfer directly. No list configuration guarantees access for every ISP or region.