Clash Verge Rev Fake-IP DNS Setup on Windows: Step-by-Step

Understand what Fake-IP changes

Fake-IP is a DNS handling mode supported by Mihomo, the proxy core commonly used by Clash Verge Rev. Instead of returning a website’s real destination address to an application, the DNS module assigns the domain a temporary address from a reserved range. When the application connects to that address, Mihomo uses its internal mapping to recover the original domain, then processes the connection through the configured rules and proxy groups.

This approach can make domain-based routing more reliable. Some applications connect to an IP address immediately after resolving a domain, which can leave the proxy core without the original hostname. With Fake-IP, the application receives a synthetic address, while Mihomo keeps the domain association needed to evaluate rules such as DOMAIN and DOMAIN-SUFFIX. Fake-IP is not a proxy server, an encryption protocol, or a replacement for routing rules; it changes the address returned during DNS resolution.

Fake-IP is often useful when a configuration uses domain rules, when apps make frequent DNS requests, or when a TUN connection needs to retain domain information for routing. It is not a universal fix for every connection problem. Local network discovery, some games, VPN software, and apps with their own encrypted DNS may need additional handling. If a particular app stops working after enabling Fake-IP, the right response is to identify which DNS and routing path that app uses rather than repeatedly changing unrelated proxy settings.

The instructions below apply to Clash Verge Rev on Windows with a Mihomo-compatible core. Menu names and available controls can differ between releases, and a subscription may supply DNS settings that the GUI displays as read-only. Confirm the active core and configuration before changing anything. A setting in an inactive profile cannot affect the traffic currently passing through the client.

Locate the active DNS controls in Clash Verge Rev

Start Clash Verge Rev and select the profile you actually use. Check that the profile has been imported successfully and that the client shows an active Mihomo core. Depending on the installed release, DNS options may appear in the profile editor, a settings or configuration page, or a configuration override area. Look for fields such as dns, enable, and enhanced-mode, rather than assuming that a switch with “DNS” in its name controls every DNS behavior.

Before editing, make a copy of the current profile or export its YAML if the client provides that option. Subscription profiles are frequently regenerated when updated. Directly changing a generated file may appear to work, then disappear at the next update. If the client offers an override, merge, or patch feature, use the supported mechanism to add persistent DNS fields. If the profile is locally maintained, edit that profile and validate it after saving.

Check whether the profile already contains a dns: section. YAML cannot have two independent top-level dns: sections and expect them to merge automatically; duplicate keys can cause one block to override another or make the configuration invalid. Add the required options to the existing section, preserving its other settings. Keep indentation consistent and use spaces, not tabs.

  • Confirm the selected profile is the one marked active or currently loaded.
  • Check the core name and version in the client’s core area, About page, or runtime log.
  • Back up the configuration before editing and note any existing DNS filters or policies.
  • After saving, reload the profile or apply the override so the running core receives the change.

Enable Fake-IP mode and review the essential fields

For a Mihomo configuration, the main switch is enhanced-mode: fake-ip inside the dns section. DNS must also be enabled. The following is a minimal structural example, not a complete replacement for a working subscription. Keep your existing nameservers, policy entries, filters, and other profile-specific options where appropriate.

dns:
  enable: true
  enhanced-mode: fake-ip
  fake-ip-range: 198.18.0.1/16
  nameserver:
    - https://1.1.1.1/dns-query
    - https://8.8.8.8/dns-query
  fake-ip-filter:
    - "*.lan"
    - "*.local"
    - "localhost"

enable activates the core DNS module. If it is false or omitted in a profile that does not enable DNS by default, setting the mode alone will not provide the expected behavior. enhanced-mode chooses how DNS answers are handled: fake-ip assigns synthetic addresses, while redir-host returns resolved addresses instead. Use one mode value at a time.

fake-ip-range defines the address range used for synthetic answers. The example uses the commonly selected 198.18.0.1/16 range. Avoid placing this range on a real interface or using it as an ordinary LAN subnet. If another network component already uses a conflicting range, follow the core’s supported options and choose a non-overlapping range rather than changing it casually.

nameserver lists resolvers the core can use to resolve domains. The two encrypted DNS URLs above are examples; they are not mandatory values and may not be reachable on every network. Keep the DNS providers already required by your profile, or choose resolvers that are accessible from your current connection. A valid URL does not prove that the resolver is reachable. If DNS fails after the change, test the resolver path and inspect the core log before adding more servers.

The fake-ip-filter list identifies domains that should not receive synthetic answers. The three entries shown are common examples for local names, not a complete list for every environment. Some profiles include additional entries for consoles, devices, or services that require real DNS answers. Preserve existing filters and add a domain only when there is a specific reason, such as an app failing to discover a local device. A broad filter can cause more domains to bypass Fake-IP than intended.

Some configurations also define default-nameserver, proxy-server-nameserver, or nameserver-policy. These fields serve different purposes and should not be copied blindly from an unrelated profile. For example, a policy can direct selected domain suffixes to particular resolvers, while a proxy-server resolver may be used to resolve the hostnames of proxy servers. Keep these relationships consistent with the subscription and the network where the client runs.

Apply the settings and choose a Windows traffic path

Save the profile or override, then use Clash Verge Rev’s reload or update action to apply it. If the client reports a YAML parsing error, do not keep toggling DNS switches: inspect the error line, duplicate top-level keys, quote characters, and indentation first. A DNS setting only takes effect after the active core has successfully loaded the updated configuration.

Next, decide how Windows applications will send traffic to the core. With System Proxy enabled, Windows applications that respect the operating system proxy settings can connect through the local HTTP or mixed proxy. Some command-line programs, games, services, and apps with their own proxy settings may ignore this mechanism. Enabling Fake-IP does not force every application to use the system proxy.

TUN mode provides another traffic path by creating a virtual network interface and routing more system traffic through the core. On Windows, enabling TUN may require administrator permission and installation or activation of the required network driver. Do not enable it just to test Fake-IP if your current system-proxy setup already meets your needs. If you do use TUN, check the client’s TUN status, routing configuration, and DNS handling together; the exact controls vary by release and profile.

Only change one major setting at a time. First apply the DNS mode and test a normal domain lookup. Then, if necessary, test with System Proxy or TUN according to the applications you need to cover. This makes it easier to distinguish a DNS failure from a Windows proxy, route, permission, or firewall problem. If the client has a DNS override switch separate from the profile, verify that it is enabled only when you intend the GUI to replace or merge profile values.

  • Wait for the core to report that the configuration loaded successfully.
  • Confirm the client is using the intended profile and proxy mode, such as Rule.
  • Check whether System Proxy or TUN is active, and note which one you are testing.
  • Open the connection list and logs so DNS and routing results can be observed while testing.

Verify Fake-IP behavior on Windows

After the core reloads, test a domain that you have not just opened in the browser. In PowerShell, run Resolve-DnsName example.com or nslookup example.com. If the query is handled by the active Fake-IP DNS path, the returned address should fall within the configured synthetic range, commonly within 198.18.0.0/16. The exact displayed record can vary with the domain, client version, cache state, and query type, so use the result as one check rather than as the only proof.

Resolve-DnsName example.com
nslookup example.com

If the result is a normal public address, first check whether Windows sent the query to Clash. Another VPN, DNS filter, security product, browser feature, or local network adapter may be answering it. Also check that the active configuration has DNS enabled and Fake-IP selected, that the profile was reloaded, and that the query is not covered by a filter or policy that requests a real answer.

Then visit a site in a browser and inspect the Clash Verge Rev connection list. Look for the requested domain, its matched rule, the selected proxy group, and the connection result. A synthetic address appearing in a DNS query is useful evidence, but the connection list is the better way to confirm how a later connection was routed. If the domain matches a direct rule, the request may correctly bypass a proxy even though Fake-IP is working.

Browser tests can be misleading when the browser has Secure DNS, also called DNS over HTTPS, enabled independently. That setting may send DNS requests directly to a browser-selected resolver rather than using the Windows resolver path. For a controlled test, temporarily disable the browser’s separate secure-DNS setting or select the operating system provider, then repeat the lookup. Restore your preferred setting after confirming which path works for your setup.

Windows can also retain cached DNS answers. If you changed the mode or filter and still see an old result, close the test app and clear the Windows DNS cache from an elevated or ordinary terminal as appropriate:

ipconfig /flushdns

Clearing the Windows cache does not necessarily clear the core’s own DNS cache or a browser’s internal cache. Use the client’s supported DNS cache or core reload controls if available, and restart the affected app before retesting. Avoid deleting arbitrary client data directories; those can contain profiles and local settings in addition to temporary records.

Troubleshoot websites and apps that fail after enabling Fake-IP

If all domains fail to resolve, check the core log for DNS startup errors, resolver timeouts, invalid YAML, and address conflicts. Confirm that the chosen nameserver is reachable from the current network, then temporarily test with one known reachable resolver already permitted by your environment. Do not add many unrelated resolvers at once: mixed results make it harder to identify which server is being used and whether a policy is directing the query elsewhere.

If only one website fails, compare its DNS answer, rule match, and selected proxy group with a domain that works. The domain may be covered by fake-ip-filter, a nameserver policy, or an existing routing rule. Check whether a rule sends it to a direct connection, whether the selected proxy group has an available node, and whether the site requires a domain-specific exception. A DNS answer by itself does not establish that the proxy route is correct.

If a local device, printer, or network share stops working, the app may rely on local name resolution or broadcast discovery rather than a normal internet connection. Keep suitable local-domain filters, confirm that the device and PC are on the intended LAN, and test with the client’s proxy or TUN mode temporarily disabled. If adding a specific filter restores access, keep the exception narrow and document why it is needed instead of disabling Fake-IP for every domain.

If a game or desktop app displays an error but browsers work, check whether the app uses its own DNS-over-HTTPS service, a direct socket connection, or a hard-coded IP. Also verify whether its traffic enters Clash through System Proxy or TUN. A successful browser request only validates the browser’s current path; it does not demonstrate that a separate application follows the same DNS and proxy settings.

If connections appear in the Clash log but time out, the problem may be downstream of DNS: a rule could select an unavailable node, a remote server may reject the connection, or a firewall may block the core. Record the domain, rule, proxy group, and error message before changing configuration. Restore the previous DNS mode as a controlled comparison if needed; if the same connection still fails with redir-host, investigate the route or application rather than treating Fake-IP as the sole cause.

When the test is complete, keep the smallest set of changes that solves the identified issue. Preserve the original profile, retain only necessary filters and policies, and confirm the configuration still loads after a client restart or profile update. This gives you a reproducible setup and makes future troubleshooting much easier than maintaining several overlapping DNS overrides.

Download Clash