CoreDNS is faster and natively supports DoH, gRPC, and caching. ./Corefile :
timedatectl set-ntp true apt install chrony -y systemctl restart chrony Check your time sync: v2ray slow dns server
"My V2Ray connection is unbearably slow." CoreDNS is faster and natively supports DoH, gRPC,
"dns": { "hosts": { "domain:google.com": "223.5.5.5" }, "fakeDns": { "ipPool": "198.18.0.0/15" } } Warning: Fake DNS breaks sniffing on the local client. Only use this on the server side with xray (the V2Ray fork) for VLESS or Trojan protocols. Even with a fast DNS server, your routing rules can introduce delays. The "GeoSite" Trap V2Ray uses GeoSite for domain-based routing. If you have thousands of rules (e.g., geosite:cn , geosite:gfw , geosite:apple ), V2Ray must check every rule sequentially. Even with a fast DNS server, your routing
In this deep dive, we will explore why DNS becomes the bottleneck in V2Ray, the technical mechanics of DNS leaks and timeouts, and the exact configuration tweaks to turn a sluggish proxy into a lightning-fast tunnel. To understand why DNS slows you down, you must understand how V2Ray handles routing. The "Split Brain" Problem By default, most V2Ray setups use a split routing strategy (freedom for domestic traffic, proxy for international). For this to work, V2Ray must resolve a domain name to an IP address before deciding where to send the packet.
The culprit is almost always invisible:
timedatectl status Look for System clock synchronized: yes . A Reddit user reported the classic "V2Ray slow DNS server" symptom: curl https://google.com via proxy took 3.2 seconds, but curl https://1.1.1.1 took 120ms.