Clash DNS and Fake-IP Troubleshooting

DNS problems often look like node problems. Check resolver mode, nameserver, fallback and rule matching before judging node speed.

Reading tip

Identify the scenario first, then follow the checks in order. Jump to the linked download, subscription or configuration page when the issue becomes specific.

Three Terms First

  • nameserver: the default resolver list.
  • fallback: alternate resolvers used for selected domains or abnormal results.
  • enhanced-mode: commonly fake-ip or redir-host, affecting domain restoration and rule matching.

Check Order

  1. Disable complex overrides and keep only the DNS config generated by the current profile.
  2. Confirm whether enhanced-mode is fake-ip or redir-host.
  3. Read logs for the resolved domain and the final matched rule.
  4. If only some sites fail, add fake-ip-filter entries or adjust nameserver-policy.
  5. If everything fails, restore system DNS or disable TUN, then enable settings one at a time.

fake-ip or redir-host?

ModeStrengthWatch For
fake-ipOften stronger for transparent proxy and rule matchingSome LAN, banking, gaming, casting and time services need filters
redir-hostEasier to reason about because real records remain visibleComplex routing can lose domain context more easily

Common Filter Example

dns:
  enable: true
  enhanced-mode: fake-ip
  fake-ip-filter:
    - '*.lan'
    - '*.local'
    - time.*.com
    - '+.ntp.org'

The example shows placement only. Adjust domains based on logs and device behavior.

Reducing DNS Leaks

  • Avoid letting the system, browser and client use conflicting DNS policies.
  • In TUN mode, confirm DNS hijack and routing are both active.
  • Do not publish internal domain names or log screenshots that reveal private network details.

Reference Sources