DNS in Clash Verge Rev: Fix Resolution Failures and Stop Leaks Without Breaking LAN

Proxy on but a few sites fail or land on weird errors—sometimes it’s DNS pollution or the wrong resolve path, not the node. Clash Verge Rev (Mihomo) handles DNS itself; defaults usually work, wild edits break LAN resolve.

Most users keep the provider’s fake-ip. For stubborn sites, AI blank pages, or LAN breakage, patch nameserver / fake-ip-filter via Merge. Use the connections page to separate “rule DIRECT” from “bad resolve”; rules: routing.

Is it actually DNS?

Connections appear but the browser fails, resolved IPs look wrong, swapping nodes does nothing—lean DNS. No connections at all → system proxy; single-site issues → sites still blocked. Logs: debug logs.

fake-ip and when to edit

fake-ip intercepts queries with fake addresses to cut pollution. Great for daily use; LAN names, some games, and corp DNS policies may need filters or a temporary disable. Don’t dump random public DNS first—snapshot provider defaults, then small patches.

Edit via Merge, not the subscription body

Append a dns block in Merge/override. Copy Merge first (backup, Merge). One change at a time. If corp policy forbids custom DNS, don’t fight it.

dns:
  enable: true
  enhanced-mode: fake-ip
  nameserver:
    - 223.5.5.5
    - 119.29.29.29
  fake-ip-filter:
    - '*.lan'
    - '*.local'
    - 'printer.local'

This keeps fake-ip for the open internet while letting local .lan / .local names resolve normally—add your NAS or printer host there instead of disabling fake-ip globally.

Accept and roll back

1. Reload; check target site resolve on the connections page.
2. LAN printer/NAS still works—or add fake-ip-filter.
3. Compare latency/sites to before (latency).
4. On failure, restore Merge—don’t stack a third “optimization.”

Phones on LAN share need a consistent DNS path (LAN share). Builds: download center.