A Chrome Bypass Rule Cannot Choose Its DNS Resolver
Distinguish destination route exclusions from local name-resolution rules when checking a Chromium SOCKS setup.
Choose the flag for the stage you need to change:
--proxy-bypass-list- Selects destinations that avoid the configured proxy.
--host-resolver-rules- Changes how Chromium's local resolver handles selected names.
The bypass token <-loopback> subtracts an implicit direct-route exception. It gives no instruction to send DNS queries to SOCKS.
Chromium's SOCKS5 path normally asks the proxy to resolve destination names, while other browser features may still perform local lookups. One successful proxied page therefore cannot establish how every DNS query travels.
Do not block the lookup that finds the proxy
A broad resolver rule rejecting local lookups can also reject a hostname used to reach the proxy itself. Chromium's documented example accounts for that endpoint separately. Dropping its exception can stop the browser before SOCKS negotiation begins.
Identify the name and lookup owner before editing either control: a local destination lookup, a proxy-endpoint lookup and a proxy-side destination failure are distinct observations. An interface refusing one command-line switch does not establish that another switch replaces it. Use the browser session's supported configuration interface, then inspect route choice and DNS handling separately.