v2rayNCommunity guide
← Back to blog
Configuration·8 min read·09 / 30

DNS basics in v2rayN: make it stable before making it advanced

DNS turns names into addresses and influences routing. If defaults work, do not enable FakeIP, several DoH servers and complex rules in one change.

Steps

  1. Record the current core, proxy mode and default DNS behavior, then confirm that a normal hostname resolves.
  2. Separate local and remote resolution. LAN and direct destinations often need local DNS; proxied targets can use remote resolution according to your privacy model.
  3. A DoH hostname needs a working bootstrap path, or the core may need DNS in order to resolve the DNS server itself.
  4. Change one item, restart the core and inspect the DNS server, matched rule and first error before keeping it.

Why this matters

DNS and routing depend on one another. Small changes with a known baseline prevent the classic case where IP works but names fail for unclear reasons.

How to verify

Common names resolve consistently, direct and proxied domains use the intended resolvers, and startup logs contain no timeout or loop.

Things to watch

FakeIP is for compatible TUN scenarios. Enterprise discovery, LAN services and some games require real addresses.

Official references

System proxy and routing↗UI and advanced settings↗