Need Fake-IP DNS in Clash Verge Rev for Windows? Follow this practical walkthrough to edit the right profile, apply the DNS configuration, verify the result, and troubleshoot the most common setup problems without changing unrelated proxy options.
Clash Verge Rev Fake-IP Setup on Windows: DNS Configuration Guide
Understand what Fake-IP changes before editing the profile
Fake-IP is a DNS handling mode provided by the Mihomo-compatible core used by many Clash Verge Rev builds. Instead of returning the real destination address to an application, the core assigns the domain a temporary address from a reserved Fake-IP range. When the application later connects to that address, Clash uses its internal mapping table to recover the original domain and apply domain-based rules.
This approach is different from traditional or redir-host DNS behavior. With redir-host, the application usually receives the real address returned by an upstream DNS server. With Fake-IP, the application receives a synthetic address, while the core keeps the relationship between that address and the requested domain. This can make domain rules more reliable when a program connects by IP after DNS resolution, especially when the traffic is handled through TUN.
Fake-IP is not automatically better for every Windows application. Some programs expect DNS replies to contain real addresses, some perform their own certificate or address validation, and some local-network services should never be sent through a synthetic mapping. Printers, router administration pages, enterprise intranet domains, captive portals, and applications that require direct local discovery may need exclusions.
The change also affects the DNS path rather than only the visible system proxy switch. Windows applications that use the operating system resolver may be handled differently from browsers with secure DNS enabled, applications with an embedded resolver, or command-line tools that connect directly to a configured DNS server. Therefore, enabling Fake-IP in the YAML file is only the first part of the setup. You must also verify that the active profile, running core, and traffic interception mode are using the same DNS configuration.
Before making changes, note the current profile name, the active proxy group, the local mixed port, and whether TUN is enabled. Take a copy of the original configuration or record the existing DNS section. If the profile is generated from a subscription, editing the generated YAML directly may be temporary because a later update can replace it.
Select the correct Clash Verge Rev profile on Windows
Clash Verge Rev can contain several configuration sources at the same time: a downloaded subscription, a local YAML file, a merged profile, and an active runtime profile. Editing a file that is not currently selected is one of the most common reasons a DNS change appears to have no effect.
Open Clash Verge Rev and go to the profile management area. The exact label can differ slightly between releases, but the interface normally shows a list of available profiles and identifies one as active. Select the profile currently used by the running core, then use the profile menu to open, edit, or reveal its source file. Do not assume that the newest item in the list is the active one.
If the profile came from a subscription, first determine whether the client supports a persistent override or merge option. A direct edit may work for testing, but the next subscription update can restore the provider’s original DNS section. A local profile or supported override is safer when the Fake-IP settings must survive updates.
Before editing, search the complete YAML file for dns:. There should normally be one effective top-level DNS section. YAML indentation determines the structure, so a DNS key placed under proxy-groups, rules, or another unrelated section will not configure the DNS module. Also check whether the profile uses anchors, merge fields, or a client-specific override that may replace the visible values at runtime.
dns:
enable: true
listen: 0.0.0.0:1053
enhanced-mode: fake-ip
The snippet above is only a starting structure. The listening address and port must not conflict with another local DNS service, and the correct values depend on how Clash Verge Rev and TUN are configured. If the client already provides a DNS listener, preserve that listener unless there is a specific reason to change it. Avoid changing ports, proxy groups, or routing rules at the same time as the DNS mode; limiting the change makes later testing much easier.
Check the active core and configuration preview
Fake-IP requires a core that supports the relevant DNS fields. In Clash Verge Rev, check the core or kernel information shown in the settings, About panel, or runtime log. A Mihomo-based core generally supports the modern DNS options used in this guide, while an older or different core may reject fields or silently behave differently.
After saving the profile, use the client’s configuration validation or reload function if available. A successful save only proves that the file was written; it does not prove that the core accepted every option. Inspect the startup log for YAML parse errors, unknown fields, address-binding failures, or messages indicating that DNS initialization was skipped.
Configure Fake-IP DNS without replacing unrelated proxy settings
A practical Fake-IP setup should define the DNS mode, at least one reachable upstream resolver, and an exclusion list for domains that should receive real addresses. The following example is intentionally conservative. It does not change the proxy nodes, proxy groups, rules, ports, or operating mode outside the DNS section.
dns:
enable: true
ipv6: false
enhanced-mode: fake-ip
fake-ip-range: 198.18.0.1/16
fake-ip-filter-mode: blacklist
fake-ip-filter:
- "*.lan"
- "*.local"
- "localhost"
- "+.msftconnecttest.com"
- "+.msftncsi.com"
- "time.windows.com"
nameserver:
- https://1.1.1.1/dns-query
- https://dns.google/dns-query
fallback:
- tls://1.1.1.1
- tls://8.8.8.8
enable: true activates the DNS module. enhanced-mode: fake-ip selects Fake-IP instead of redir-host. The fake-ip-range defines the synthetic address pool; 198.18.0.0/15 is commonly used for benchmarking and synthetic network mappings, and the example uses a subnet inside that range. Keep the default supplied by the client or core when you do not have a reason to change it.
The nameserver list contains upstream DNS services used to resolve domains. HTTPS and TLS resolvers can prevent simple plaintext DNS queries from being exposed on the local network, but their reachability depends on the local network and routing rules. A resolver that is technically valid but unreachable from your current connection can cause slow page loads or repeated timeout messages.
The fallback list is optional and should be used deliberately. It is not a universal repair for every DNS failure. Depending on the core version and the rest of the configuration, fallback behavior may interact with filtering, geolocation, or nameserver policy. If you use fallback-filter, review its country, IP, and domain settings instead of copying a filter from an unrelated configuration.
fake-ip-filter is particularly important on Windows. Entries such as *.lan and *.local cover common local names, while Microsoft connectivity-check domains can help Windows determine whether a network is online. The exact matching syntax depends on the core version; +.example.com is commonly used to match a domain and its subdomains, while a leading wildcard pattern may be used for broader matching. Check the syntax accepted by the installed Mihomo version if a filter does not behave as expected.
Choose the DNS listener carefully
Some configurations include a DNS listener such as listen: 0.0.0.0:1053, while others use a loopback address such as 127.0.0.1:1053. Binding to 0.0.0.0 can expose the listener on local network interfaces, so it should not be used casually when LAN access is unnecessary. A loopback listener is safer for local-only use, but TUN integration may require the client’s own DNS handling rather than a manually configured Windows resolver.
Do not change the Windows adapter DNS address merely because Fake-IP is enabled. Clash Verge Rev may configure DNS interception through TUN or its internal runtime. Manually pointing Windows to an arbitrary Clash DNS port can create a loop, a port conflict, or a resolver that is unavailable when the client is closed. Follow the client’s supported TUN and DNS workflow first.
Apply the configuration and verify that Fake-IP is active
Save the profile, select it as active if necessary, and reload or restart the core from Clash Verge Rev. If the client has separate switches for system proxy and TUN, keep your existing choice while testing DNS. Enabling both at once can be useful for applications that ignore system proxy settings, but it also changes more of the network path than a DNS-only test.
Open the client’s connection or DNS log and visit a new domain that is unlikely to be served from the browser cache. Look for a DNS request, the selected upstream resolver, and a subsequent connection entry. A new request appearing in the log confirms that traffic reached this Clash instance, but it does not by itself prove that Fake-IP was used.
On Windows, open PowerShell and run a DNS query for a test domain:
Resolve-DnsName example.com
nslookup example.com
The result may show a synthetic address rather than the public address returned by the upstream resolver. Do not treat one command as conclusive if the browser uses secure DNS, the Windows resolver cache is warm, or another VPN application is active. Compare the result after clearing or bypassing the cache, and check the Clash log at the same time.
You can inspect the local DNS cache with:
ipconfig /displaydns
To clear the Windows DNS client cache during testing, use:
ipconfig /flushdns
Flushing the cache does not clear Clash’s internal Fake-IP mapping in every situation. Reloading the profile or restarting the core may be required to create a clean test. Close and reopen the browser after changing DNS, because existing connections, connection pools, and HTTP/3 sessions can make an old path appear to remain active.
Check the difference between system proxy and TUN
System proxy mode generally affects applications that honor the Windows proxy settings. It does not automatically capture every process, every UDP request, or every application with its own networking stack. TUN creates a broader interception path, but it requires the appropriate permissions and may be affected by firewall rules, antivirus software, virtual network adapters, or another VPN driver.
For a controlled test, first use a browser without a proxy extension and with browser-specific secure DNS disabled temporarily. Confirm that the request appears in Clash. Then test a command-line request through the local mixed port if that port is enabled:
curl.exe -x http://127.0.0.1:7890 -I https://example.com
Replace 7890 with the actual HTTP or mixed-port shown by Clash Verge Rev. If the command works only when the proxy is specified explicitly, the local listener is functioning but the application is not using the Windows system proxy. If TUN is enabled, compare the result with and without the explicit proxy to determine which path is responsible for the connection.
Troubleshoot the most common Fake-IP problems
The configuration saves, but DNS remains unchanged. Confirm that the edited profile is active and that the core was reloaded after saving. Search for a second dns: section or an override that replaces enhanced-mode. Also check whether another VPN, security product, browser secure-DNS feature, or manually configured adapter DNS is handling the request before it reaches Clash.
Websites load slowly or fail intermittently. Check the reachability of every upstream resolver. A DoH endpoint may be blocked or unreachable on the current network, while a TLS endpoint may be affected by certificate inspection or incorrect system time. Test with one known reachable resolver before adding multiple fallback entries. Examine the runtime log for timeout, connection refused, or DNS server unavailable messages.
Windows says there is no Internet connection. Windows uses connectivity-check domains to determine network status. Add the relevant Microsoft domains to fake-ip-filter if they are receiving synthetic addresses that the check cannot handle. This status indicator does not always represent actual browser connectivity, so verify both the system notification and a real web request.
Local devices or intranet pages stop working. Add the local suffix or exact domain to the exclusion list, and make sure the local network itself is reachable. Common entries include *.lan, *.local, router hostnames, printer names, and internal company domains. If the service is accessed by a private IP address, review TUN and routing rules as well as DNS; Fake-IP alone may not be the cause.
An application rejects connections after Fake-IP is enabled. Some software performs its own DNS resolution, validates the returned address, or expects a direct connection to a known IP. Add only the affected domain to the filter and retest. If the application uses hard-coded IP addresses, changing DNS will not redirect it; check whether TUN, rules, or the application’s own proxy setting is required.
Rules match the wrong policy. Fake-IP can improve domain visibility, but it does not repair rule order. Clash evaluates rules from top to bottom. A broad MATCH rule, an earlier IP-CIDR rule, or a process rule can take effect before the domain rule you expected. Inspect the connection entry, matched rule, and selected proxy group rather than judging only from the final page result.
Fake-IP DNS FAQ
Does Fake-IP require TUN mode on Windows?
No. Fake-IP is a DNS mode, while TUN is a traffic interception method. Fake-IP can be used with system proxy mode for applications that honor Windows proxy settings. TUN is useful when applications ignore the system proxy, but it introduces additional permissions, routing, and driver considerations.
Why does nslookup show a real address instead of a Fake-IP address?
The query may be using a different DNS server, a cached result, browser secure DNS, or a resolver outside Clash. Verify the active profile, inspect the Clash DNS log, flush the Windows cache, and temporarily disable competing DNS paths during testing.
Will a subscription update remove my Fake-IP settings?
It can. If you edit a generated subscription file directly, the provider update may replace the edit. Use Clash Verge Rev’s supported override or merge mechanism, or maintain a local profile that incorporates the subscription data without modifying the original source.
Should every domain be added to fake-ip-filter?
No. The filter is for known compatibility cases, local names, and services that require real DNS answers. Start with a short list, confirm the affected application, and add specific domains instead of disabling Fake-IP globally.