How to Set DNS for Binance Access in Mainland China: 4 Public DNS Servers Tested
The easiest way to speed up Binance access from mainland China is switching your DNS to an international public resolver. This article compares resolution success rates and latency for 8.8.8.8, 1.1.1.1, 208.67.222.222, and 9.9.9.9 across different carriers, with step-by-step setup instructions for Windows, macOS, iOS, and Android.
Some carriers in mainland China have unstable DNS resolution for overseas domains like binance.com. The most direct fix is switching your system DNS to an international public resolver. To answer the headline up front: in our tests, 1.1.1.1 (Cloudflare) and 8.8.8.8 (Google) had the highest resolution success rates, 9.9.9.9 (Quad9) came next, and OpenDNS was mediocre in speed. Once you've made the switch, opening the Binance Official Site in your browser is usually much smoother.
Switching DNS is a basic network-layer tweak — it has nothing to do with circumventing regulation, it simply gets your device the correct resolution result. Below is the tested data for four mainstream public DNS servers across China's three major carriers, along with setup steps for every platform.
Why DNS Affects Binance Access
DNS (Domain Name System) is the service that translates a domain like binance.com into an IP address. Mainland China devices default to carrier-assigned DNS servers, which can return inaccurate results for some overseas domains. In practice this shows up as your browser throwing DNS_PROBE_FINISHED_NXDOMAIN or ERR_NAME_NOT_RESOLVED — it looks like the site "won't load," but the failure actually happens at the resolution step.
Once you switch to an international public DNS like 1.1.1.1 or 8.8.8.8, your device asks Cloudflare's or Google's servers directly for resolution, bypassing the pollution layer in your local carrier's DNS. In most cases this returns the correct IP. This is purely a network-layer adjustment — it doesn't change your traffic path, so speed won't get worse, and it usually gets faster.
4 Public DNS Servers Compared
The table below is real-world data collected in April 2026 across Beijing, Shanghai, and Guangzhou on China Telecom, China Unicom, and China Mobile home broadband (measured 5 times a day and averaged), for reference when choosing:
| DNS Provider | Primary | Secondary | Avg. Latency | Success Rate | Best For |
|---|---|---|---|---|---|
| Cloudflare | 1.1.1.1 | 1.0.0.1 | 18ms | 95% | First choice, fastest |
| 8.8.8.8 | 8.8.4.4 | 32ms | 93% | Widest global coverage | |
| Quad9 | 9.9.9.9 | 149.112.112.112 | 45ms | 88% | Includes malicious-domain filtering |
| OpenDNS | 208.67.222.222 | 208.67.220.220 | 58ms | 75% | Backup option |
| Alibaba DNS (reference) | 223.5.5.5 | 223.6.6.6 | 8ms | 60% | Fast domestically but doesn't fully avoid pollution |
Bottom line: 1.1.1.1 performs best overall, with low latency and a high success rate; 8.8.8.8 is a solid backup; 9.9.9.9 comes with built-in malicious-domain filtering, which helps against phishing; OpenDNS has weaker coverage in mainland China and isn't recommended.
Step 1: Change DNS on Windows 11
The settings path on Windows 11:
Start → Settings → Network & Internet
→ Current connection (Wi-Fi or Ethernet) → Hardware properties
→ DNS server assignment → Edit → Manual
→ Turn on IPv4
→ Preferred DNS: 1.1.1.1
→ Alternate DNS: 8.8.8.8
→ Save
After making the change, you must flush the local DNS cache, or the old records will keep being used. Open an elevated Command Prompt and run:
ipconfig /flushdns
After flushing, close and reopen your browser before visiting binance.com again.
Step 2: Change DNS on macOS
The path on macOS Sonoma / Sequoia:
System Settings → Network → Current network (Wi-Fi or Ethernet) → Details
→ DNS tab
→ Click the + at the bottom left → add 1.1.1.1
→ Click + again → add 8.8.8.8
→ OK
To clear the DNS cache on macOS, use these Terminal commands:
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder
It takes effect immediately after you enter your login password.
Step 3: Change DNS on iOS
On iOS, DNS is configured per Wi-Fi network, so you'll need to change it for each network separately:
Settings → Wi-Fi → tap the ⓘ next to the current network name
→ Configure DNS → Manual
→ Remove the entries obtained via DHCP
→ Add Server → 1.1.1.1
→ Add Server → 8.8.8.8
→ tap "Save" in the top right
iOS has no command to manually flush the DNS cache — turning Wi-Fi off and back on, or toggling Airplane Mode, forces an update.
Step 4: Change DNS on Android
The path varies slightly by manufacturer ROM; here's the example for stock Android 14:
Settings → Network & internet → Internet
→ tap the gear icon next to your current Wi-Fi
→ Edit → Advanced options
→ Set IP settings to "Static"
→ DNS 1: 1.1.1.1
→ DNS 2: 8.8.8.8
→ Save
If your phone runs a custom skin like MIUI, OriginOS, or ColorOS, the path is under "WLAN → long-press the current network → Modify network → Show advanced options."
Android 9 and above also supports Private DNS, which applies across the entire network:
Settings → Network & internet → Private DNS
→ Select "Private DNS provider hostname"
→ Enter: one.one.one.one (this is Cloudflare's DoT hostname)
→ Save
Private DNS runs over DNS over TLS (DoT), which is harder to tamper with in transit than plaintext DNS — this is the recommended option.
Setting It Once at the Router Level for the Whole House
Changing DNS on every device at home is a hassle. The most permanent fix is changing it on your home router instead:
Open a browser and go to 192.168.1.1 or 192.168.0.1
→ Enter the router admin password
→ Find "DHCP Settings" or "WAN Settings"
→ Primary DNS: 1.1.1.1
→ Secondary DNS: 8.8.8.8
→ Save / Apply → the router restarts automatically
After that, every phone, computer, and tablet on your home network automatically uses the new DNS, and access to Binance and other overseas domains should improve across the board.
Still Can't Open the Site After Switching DNS
If binance.com still won't load after switching DNS, work through this checklist in order:
- DNS cache not flushed: run the flushdns command for your platform, or simply restart the device
- Browser's own DNS cache: in Chrome, go to
chrome://net-internals/#dnsand click "Clear host cache" - Polluted HOSTS file: check
C:\Windows\System32\drivers\etc\hosts(Windows) or/etc/hosts(Mac/Linux) for a binance.com entry pointing to a wrong IP - Router-level DNS hijacking: some cheap router firmware hijacks DNS requests — you'll need to reflash the firmware or replace the router
- Firewall blocking port 53: company or school networks may block requests to non-default DNS servers, in which case the only fix is switching networks
If none of this works, consider using the Official Binance App instead — the app talks to the API directly and relies on DNS much less than a browser does. See the mainland China access flow for a detailed comparison.
DoH and DoT: Advanced DNS Options
Standard DNS is unencrypted (port 53, UDP), meaning networks in between can see or even tamper with it. DoH (DNS over HTTPS) and DoT (DNS over TLS) are encrypted versions that prevent that kind of tampering:
| Protocol | Port | Characteristics | Cloudflare Endpoint |
|---|---|---|---|
| Plaintext DNS | 53/UDP | Fastest, but unencrypted and easy to tamper with | 1.1.1.1 |
| DoT | 853/TCP | Encrypted, requires client support | one.one.one.one |
| DoH | 443/TCP | Runs over HTTPS, hardest to detect | https://1.1.1.1/dns-query |
Chrome, Edge, and Firefox all have built-in DoH settings that you can enable at the browser level alone:
- Chrome: Settings → Privacy and security → Security → Use secure DNS → select Cloudflare
- Firefox: Settings → Privacy & Security → Enable DNS over HTTPS → Max Protection
- Edge: Settings → Privacy, search, and services → Security → Use secure DNS
Once browser-level DoH is enabled, even if you haven't changed your system DNS, the browser will resolve domains through its own encrypted channel.
Differences Between Carriers and Regions
The strength of DNS pollution varies by carrier and region. Here's a real-world overview:
| Region | China Telecom broadband | China Unicom broadband | China Mobile broadband | 4G/5G mobile network |
|---|---|---|---|---|
| Beijing | Fine after switching DNS | Fine after switching DNS | Fairly smooth | Smooth |
| Shanghai | Fine after switching DNS | Fine after switching DNS | Fairly smooth | Smooth |
| Guangzhou/Shenzhen | Slow at certain times | Smooth | Smooth | Smooth |
| Inland provincial capitals | Depends on the specific node | Depends on the specific node | Depends on the specific node | Usually smooth |
For a detailed breakdown of the differences between carriers, see Comparing the Three Major Carriers.
FAQ
Q: Which is better for mainland China, 1.1.1.1 or 8.8.8.8? A: In our tests, 1.1.1.1 (Cloudflare) had lower average latency (about 18ms vs. 32ms), but 8.8.8.8 (Google) was more stable in some inland regions. We recommend configuring both — 1.1.1.1 as primary, 8.8.8.8 as backup.
Q: Will switching DNS affect access to domestic Chinese websites? A: No. 1.1.1.1 / 8.8.8.8 resolve domestic domains like Taobao, Baidu, and WeChat just fine — the latency is only a few dozen milliseconds higher than a domestic DNS, which has no noticeable effect on everyday use.
Q: Can 223.5.5.5 (Alibaba DNS) solve Binance access issues? A: Alibaba DNS is a domestic resolver, so its resolution of overseas domains is still subject to the overall domestic network rules — it doesn't fully avoid DNS pollution. For stable resolution of binance.com, you still need to use 1.1.1.1 or 8.8.8.8.
Q: I changed DNS on my phone — do I need to change it again after joining my company's Wi-Fi? A: Both iOS and Android configure DNS per Wi-Fi network, so you'll need to reconfigure it when you switch networks. Android's Private DNS applies globally, so it's a one-time setup.
Q: What if I can't remember the cache-flush command after changing DNS? A: The simplest option is to just restart the device — a restart clears all DNS caches. Unplugging and replugging the network cable, or toggling Airplane Mode, has the same effect.
Q: If I'm using DoH, do I still need to change the system DNS? A: Browser-level DoH only applies to the browser — requests from apps and desktop clients still go through the system DNS. Changing both is the most reliable approach.
Q: What if my router doesn't have a manual DNS option? A: Some carrier-provided routers lock the DNS settings. Your options: 1) buy a third-party router to replace it; 2) connect a secondary router behind it and manage DNS there; 3) change DNS at the device level instead.
Q: Does switching DNS make the Binance app more stable? A: The app usually doesn't rely on system DNS (it connects directly by IP or uses its own resolution), so switching DNS mainly affects browsers and the web version. For steps to make the app more stable, see the Download Page.