Connection troubleshooting

Clash Verge Rev DNS override mismatch

After a subscription update, is Clash Verge Rev's DNS override on but not merged? Distinguish DNS Overwrite from Enable DNS, check the subscription and runtime configuration against the v2.5.10 fix, then verify a restart and real requests.

  • Clash Verge Rev
  • DNS override
  • Subscription changes
  • Runtime config
  • v2.5.10
On this page

You saved your local DNS settings, but a subscription update leaves a different setup in use. First identify the active subscription and whether you are looking at the main DNS Overwrite switch or Enable DNS inside the DNS editor.

Check both switches, not just Enable DNS

DNS Overwrite controls whether the active subscription uses the local DNS override saved by the app. The editor’s dns.enable switch belongs to the DNS configuration itself. An enabled switch inside the editor does not, by itself, show that the local settings were merged into the current runtime config.

Official issue #8431 included confusion between these two switches; the reporter later confirmed what the main override switch does. The discussion helps identify the symptom, but it does not prove that the v2.5.10 state-sync patch fixes every DNS failure.

Start with the state you can observe

What you seeNext step
Only Enable DNS inside the editor is onReturn to the main DNS Overwrite switch for the active subscription and check the runtime config
The main switch stays on after subscription DNS changes, but local values are not appliedCheck the app version, subscription protection state and final config
The main switch and runtime fields are correct, but domain lookup still failsContinue with the DNS upstream, proxy path and specific error

Disabling the override after a subscription change can be intentional

The v2.5.10 stable release notes identify a state mismatch: after subscription DNS settings change, the override is effectively off, yet the switch still looks on and no notification appears. The fix synchronizes the effective state, saves the settings and refreshes the UI so the reason for disabling the override can be shown.

The fixed implementation checks the original subscription DNS for nonempty proxy-server-nameserver, proxy-server-nameserver-policy and nameserver-policy values. If a previous confirmation no longer matches this content, an override that was requested on can become inactive.

Confirmation is also tied to the subscription identity, so another subscription’s state is not a valid reference. Not every DNS field change necessarily triggers this protection. Fields supplied by Merge or a script are not, by themselves, evidence that the original subscription triggered it.

The goal is to choose between keeping the current subscription’s DNS and continuing with a reviewed local override. If the same subscription’s protected content has not changed and confirmation is lost only after a restart, see our separate v2.5.7 restart guide.

Check the current config, then update and reconfirm

Back up the active subscription, local DNS settings and persistent overrides, and record the previously working mode and node. Work with the same active subscription. Changing subscriptions and DNS upstreams at the same time makes the results difficult to compare.

The app release verified for this fix is v2.5.10. Update the full Clash Verge Rev app through its official release channel; updating only the Mihomo core cannot repair app-side state synchronization. There is no need to downgrade a later stable release that is confirmed to include the same fix.

Check one active subscription at a time

  1. Compare the main switch with the local DNS settings

    Open Settings → Clash Setting and find the main DNS Overwrite switch. Use the gear beside it to view the local DNS configuration. Record the upstreams and policies you intend to use; do not mistake the enable switch inside that editor for the main override state.

  2. Inspect the DNS fields in the runtime config

    Open Settings → Verge Advanced Setting → Runtime Config and compare the actual dns.enable, nameserver and relevant policy values. This shows the runtime config, rather than the original subscription editor. Do not directly edit runtime YAML that the app regenerates.

  3. Choose subscription DNS or the local override

    To use the subscription’s DNS, leave the main override off. If you need the local DNS settings, review the subscription changes before turning the main switch on. If a protection prompt appears, read the explanation and either confirm your choice or keep it disabled.

  4. Wait for the update, then check again

    Wait for the app to finish updating the settings and config, then recheck the main switch and runtime fields. If saving or reloading fails, record the first error. Repeatedly toggling the switch can obscure the failure.

Verify the fields, restart state and fresh requests

First check that the expected DNS fields are present in the runtime config. If the main override is off, confirm that the result matches your choice to keep subscription DNS. If it is on, check the result after local settings, other persistent overrides and scripts have been combined.

Next, make a fresh request to a domain that previously failed, using the client logs and connection result to check the affected task. Browser caches, old persistent connections or a displayed node latency cannot, on their own, prove that this DNS choice and the actual outbound path are correct.

Completion checklist

  • The installed app includes the v2.5.10 state-sync fix, and the active subscription is clearly identified.
  • The main DNS Overwrite switch is distinguished from dns.enable inside the editor.
  • The main switch matches the effective override decision, and runtime DNS fields match the intended choice.
  • After closing and reopening normally, the same unchanged subscription still reflects that choice. If the subscription changes again, check the protection prompt again.
  • Fresh domain requests and everyday tasks work. If they still fail, specific logs are available for further diagnosis.

This article was checked against official releases, fixed source code and the project’s issue discussion. We did not reproduce the upgrade in a real client. Website localization and browser checks do not replace DNS path verification on your device.

If states still disagree, restore a working setup and follow the first error

Confirmation is requested again after a subscription change

Compare the changed original subscription with the active selection before deciding whether to continue overriding it. This may be expected protection; repeatedly forcing the switch on is not a repair.

The main switch is correct, but final DNS values still differ

Check Merge, scripts and other persistent overrides outside the active subscription, and keep the before-and-after differences. Manual edits to generated files are not a lasting configuration.

Saving, updating the config or reloading reports an error

Stop adding changes. Preserve the current state and first error, then restore the subscription, local DNS settings and choice that previously worked. If you cannot update the app yet, use this recoverable setup to continue working.

DNS fields are correct, but queries still fail

Investigate the specific upstream connection, certificate, proxy path or query error. The state-sync fix does not guarantee DNS server reachability or resolve every respect-rules configuration problem.

For a report, include the full app version, a redacted identifier for the active subscription, the separate main-switch and editor settings, the necessary differences between original subscription DNS and final DNS, and the first error. Keep the original config under your control; remove subscription tokens, node passwords and sensitive domains from the copy you share.

References