Clash Verge Advanced Config: DNS, Chain Proxy, Ports, Lite Mode, Auto-Test, Blocking

This page is a quick reference for Clash Verge’s advanced settings: DNS, chain proxy, ports, node protocols, Lite Mode, auto-test, and domain blocking. For the basics (adding rules, the override mechanism) pair it with adding rules and Global Extended Configuration.

Put the override-type configs below into the Extended Configuration (global or per-subscription) so they survive subscription updates.

DNS setup #

Put the dns block in the Global Extended Configuration to apply it to all subscriptions. fake-ip is recommended to prevent leaks:

dns:
  enable: true
  enhanced-mode: fake-ip
  fake-ip-range: 198.18.0.1/16
  nameserver:
    - https://223.5.5.5/dns-query
    - https://1.1.1.1/dns-query
  fallback:
    - https://8.8.8.8/dns-query

Chain proxy (dialer-proxy / landing node) #

For “local → airport node (front) → home/landing → target”, use Mihomo’s dialer-proxy (the old relay group is deprecated). Specify the front proxy on the landing node:

proxies:
  - name: "landing-home"
    type: vmess
    server: your.home.ip
    port: 12345
    uuid: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
    # ↓ key: go through the "airport-entry" front node/group first, then this landing node
    dialer-proxy: "airport-entry"

⚠️ Subscription converters usually strip dialer-proxy. Put this node in Edit Node or Extended Configuration to keep it after updates. Chaining adds up latency — pick a low-latency front node. See the Mihomo docs.

Port settings #

Change it in Settings, or manage it via Extended Configuration:

mixed-port: 7890     # shared HTTP and SOCKS port
allow-lan: true      # let other LAN devices use this machine as a gateway

Hysteria2 / VLESS Reality and other new protocols #

These new protocols are supported only by the Mihomo kernel (Clash Verge Rev), not the original. Nodes usually come from your subscription; to add one by hand, use Edit Node, e.g.:

# Hysteria2
- name: "hy2-node"
  type: hysteria2
  server: example.com
  port: 443
  password: your-password
  sni: example.com

# VLESS + Reality
- name: "reality-node"
  type: vless
  server: example.com
  port: 443
  uuid: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  network: tcp
  tls: true
  flow: xtls-rprx-vision
  reality-opts:
    public-key: "server public key"
    short-id: "short id"

If a node won’t connect, it’s usually a mistyped field — recheck the parameters your provider gave you.

Lite Mode (save RAM) #

Proxy stable and you won’t open the UI for a while? Enable Settings → Lightweight Mode: it closes the GUI while keeping the Mihomo core running in the background, cutting memory use noticeably. Bring the window back from the system tray or a hotkey.

Auto-select the fastest node #

Use a url-test group to auto-pick the lowest-latency node (most subscriptions already include an “Auto” group — just select it):

proxy-groups:
  - name: "Auto"
    type: url-test
    url: "http://www.gstatic.com/generate_204"
    interval: 300        # test every 300s
    tolerance: 50        # don't switch unless >50ms better, avoids flapping
    proxies: [NodeA, NodeB, NodeC]

You can change the test address — see 204 test URLs for Clash Verge.

Block ads / specific domains (e.g. block Adobe phone-home) #

Use REJECT rules. Block specific telemetry/activation domains rather than all of adobe.com (which breaks normal features). Add to the prepend area in Edit Rule:

# block Adobe telemetry/activation domains (example, adjust as needed)
DOMAIN-SUFFIX,adobestats.io,REJECT
DOMAIN-SUFFIX,adobedtm.com,REJECT
DOMAIN-KEYWORD,adobe-genuine,REJECT
# general ad-blocking
GEOSITE,category-ads-all,REJECT

Full rule guide: How to add rules / custom rules in Clash Verge.

#Clash Verge config #Clash Verge DNS #Clash Verge chain proxy #Clash Verge Rev #Mihomo

Table of Contents