To check a KuaiLian DNS leak, confirm Connected and that normal pages load, then open any public DNS test page and compare resolver results with VPN off vs on. If the on-VPN result still shows your ISP or local DNS, verify the client “VPN DNS / anti-leak” toggle and rule out system DNS vs split-bypass conflicts—this page is detection and setting checks only, not a stealth or unlock promise.
Someone connected KuaiLian, every site loaded fine, yet a DNS tester still showed their ISP resolver. They blamed the app; split had kicked the tester off the tunnel, so lookups stayed on system DNS—not the same fault as “nothing loads.” Another common mess: the OS is pinned to 8.8.8.8 while the client’s “use VPN DNS” is off, so two paths fight and each refresh looks different.
Almost nothing loads → connected but no internet (nodes, system proxy, Kill Switch; DNS is only one step). A few apps or domestic sites take the wrong path → split / bypass list. Handshake never finishes → protocol switch. Status flips Connected/Connecting or drops after connect → reconnect loop / drops. This page only covers “sites work, but resolver egress may still be local” checks.
DNS leak check vs no internet vs split
- DNS leak check: tunnel is up, most sites open; you care whether lookups still hit ISP/local DNS
- Connected, no internet: browser, chat, most apps nearly all fail → nodes and proxy first, see the no-internet guide
- Split misconfig: only some domains/apps take the wrong path → bypass lists, see the split guide; bypassed names using local DNS is often expected
Name the symptom before you test: can browse but tester shows local DNS, almost offline, or one domestic site entered the tunnel. Keep the first here; send the others to no-internet and split articles so three pages do not fight over the same toggles.
How to run one VPN DNS check after connect
Prove resolver egress—not download peaks, not “full stealth.”
- Fully disconnect KuaiLian, open any public DNS test page, note the DNS provider/region (VPN-off baseline)
- Connect until status is Connected; confirm one or two ordinary pages load
- Same browser, same test page—refresh; compare whether on-VPN DNS still matches the ISP/router result
- On-VPN result shifts to another resolver set roughly aligned with the node: tunnel DNS likely took over; still ≈ ISP DNS with VPN on: move to the toggle checks below
If the tester itself is on a bypass list, VPN-on will “look leaked.” Before concluding, confirm split is not “proxy list only” and the test domain is not excluded—conflict details below; list edits in the split guide.
Find the client DNS / anti-leak controls
Labels differ. Look under settings / advanced / network for prevent DNS leak, use VPN DNS, DNS protection, or Private DNS—use what this device shows.
1. Snapshot current toggles
On/off, any custom DNS fields. Screenshot before edits so you can roll back.
2. Keep the same node
Do not swap regions during a contrast—or you will not know if DNS settings or the node moved.
3. Change only DNS-related items
Do not also flip protocol, clear cache, and rewrite split lists in the same pass.
4. Save, then reconnect
Most builds need a full disconnect/reconnect; Save alone may keep the old resolver path.
System DNS vs split conflicts: contrast order
Editing half at the OS and half in the client is the usual reason tests “jump.”
- System DNS: Windows/macOS NIC, router, Android Private DNS, iOS Wi-Fi manual DNS. Temporary public DNS is for contrast only—restore afterward
- Client VPN DNS: when on, lookups should prefer the tunnel side; OS Private DNS (especially Android) can still fight it
- Split / bypass: excluded apps or domains on direct path often keep system DNS—that is the rule working, not a whole-device leak label
- Suggested order: global (or bypass off) → enable client anti-leak only → reconnect and retest → if still odd, change one system DNS item temporarily
If almost no site loads, stop looping DNS toggles here—return to connected but no internet. Handshake never completes: protocol switch.
How to read results: leak, offline, split
- Likely leak signal: sites load; VPN-on tester still stably shows ISP/local DNS → verify client DNS toggle and whether the tester is bypassed
- More like no internet: even the tester fails to load, most sites time out → no-internet guide, not DNS-only flips
- More like split: browser test looks fine, one app still resolves locally → check that app on exclude/bypass lists
- Unstable results: three refreshes on one connection disagree wildly → you probably changed system DNS, split, and client toggles together; go back to one change at a time
A test does not prove anti-censorship, stealth, or streaming unlocks. Protocol or node changes may alter resolver paths; this article makes no speed or unlock claims.
Still wrong: what to record before FAQ / download
If contrasts still fail, gather this for FAQ or in-app support:
- Device, OS, KuaiLian version, and install source
- VPN-off and VPN-on DNS test screenshots (mask accounts)
- Client “VPN DNS / anti-leak” state; whether OS Private DNS / manual DNS is on
- Split mode (global / smart / bypass) and whether the tester or browser is excluded (never send passwords)
Menu labels mismatch old tutorials: check the download page first. Reinstall can refresh DNS options; it does not guarantee a forever-green test or unlocks. Setup paths: Guides.