In a standard V2Ray setup, DNS queries can become slow for three primary reasons:
(Best for latency) Install dnscrypt-proxy , unbound , or systemd-resolved on the same machine as V2Ray, then point V2Ray to 127.0.0.1:53 .
"dns": "servers": [ "1.1.1.1", // primary, fast "8.8.8.8", // backup "223.5.5.5" // local ISP (if trusted) ]
# UDP latency dig @1.1.1.1 google.com +timeout=2 v2ray slow dns server
| DNS Provider | Address | DoH/DoT Support | Best For | |---|---|---|---| | Cloudflare | 1.1.1.1 | ✓ | Privacy + global speed | | Google | 8.8.8.8 | ✓ | Reliability + global coverage | | Quad9 | 9.9.9.9 | ✓ | Security (blocks malicious domains) | | Alibaba (China) | 223.5.5.5 | ✓ | Domestic Chinese resolution | | 114DNS (China) | 114.114.114.114 | Limited | Fast domestic Chinese resolution | | OpenDNS | 208.67.222.222 | ✓ | Content filtering options |
Toggle Airplane Mode on and off to reset the network stack. Advanced Server-Side Diagnostics
If you must use public DNS, test alternatives that are less likely to be throttled: In a standard V2Ray setup, DNS queries can
"dns": "servers": [
: Visit a site like dnsleaktest.com while connected to V2Ray. Run the extended test. If you see your real ISP's name or country listed anywhere in the results, your DNS is leaking and slowing you down.
many users recommend using 223.5.5.5 (Alibaba) or 114.114.114.114 for domestic domains, combined with encrypted resolvers like 1.1.1.1 for international traffic. Run the extended test
This is especially problematic when using public DNS servers located far from your physical location. A DNS server halfway around the world may add 150–300 milliseconds of latency to every single lookup, directly translating to visible loading delays for users.
If your configuration forces V2Ray to query a remote, secure DNS server over an unoptimized proxy tunnel, every single web asset (images, scripts, trackers) must wait for that slow handshake to finish.
Ensure your routing rules are tight. If a domain is in your direct list, it should hit a local DNS. If it’s in your proxy list, it should be resolved by the V2Ray server itself (using remote DNS) to avoid the latency of your local connection. 4. The Ideal DNS Configuration Template A well-optimized DNS block in V2Ray often looks like this:
Run these commands from your server/PC (replace 1.1.1.1 with your V2Ray upstream DNS):