Download Binance App

How to Change DNS When Binance Fails to Resolve

2026/4/5 19 min
#Network Issues

DNS resolution failure is one of the most common errors for Binance users, with pages displaying "DNS_PROBE_FINISHED_NXDOMAIN" or "Server IP address could not be found." If you encounter this, don't panic. First, open status.binance.com next to the Binance Official Site to confirm the service itself isn't down. Then, try the 4G environment of the Binance Official APP to verify the link. If you need to install or reinstall the APP, refer to the iOS Installation Tutorial. To cut to the chase: 99% of DNS resolution failures are due to your current DNS server being polluted or timing out. Switching to Cloudflare's 1.1.1.1 or Google's 8.8.8.8 usually restores access immediately. The remaining 1% is due to system DNS cache or host file anomalies. Below are the specific methods for the four major platforms.

Public DNS Selection List

Not all public DNS are suitable for all users. Below are some that have been tested for low latency and minimal pollution.

DNS Provider Primary IPv4 Secondary IPv4 Latency Features
Cloudflare 1.1.1.1 1.0.0.1 20-40ms Fastest speed
Google 8.8.8.8 8.8.4.4 40-80ms Stable and established
Quad9 9.9.9.9 149.112.112.112 60-100ms With security filtering
AliDNS 223.5.5.5 223.6.6.6 5-20ms Fast in certain regions
OpenDNS 208.67.222.222 208.67.220.220 80-150ms Enterprise level

Recommendation: Use 1.1.1.1 as the primary DNS and 8.8.8.8 as the secondary for double insurance.

Changing DNS on Windows 10/11

GUI Method

  1. Right-click the network icon in the taskbar - "Network & Internet settings".
  2. Select "Ethernet" or "Wi-Fi" on the left to see the current connection.
  3. Click "Properties" for the current network.
  4. Scroll down to find "DNS server assignment".
  5. Click "Edit", switch to Manual.
  6. Turn on the IPv4 toggle.
  7. Fill in 1.1.1.1 for Preferred DNS.
  8. Fill in 8.8.8.8 for Alternate DNS.
  9. Select "Encrypted (automatic template)" for DNS over HTTPS.
  10. Save.

Fast Command Line Method

Run PowerShell as administrator:

Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses ("1.1.1.1","8.8.8.8")

Replace the interface name with your actual one, which can be found using Get-NetAdapter.

Clear DNS Cache

ipconfig /flushdns

Sometimes the old resolution is still used if the cache isn't cleared after modification, so be sure to clear it.

Changing DNS on macOS

Ventura/Sonoma

  1. System Settings - Network.
  2. Click the current connection (Wi-Fi or Ethernet).
  3. Click "Details".
  4. Select "DNS" on the left.
  5. Click + to add 1.1.1.1.
  6. Click + again to add 8.8.8.8.
  7. OK to save.

Terminal Clear Cache

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

Changing DNS on iOS

iOS can only set DNS for specific Wi-Fi networks, not for 4G/5G cellular data.

Specific Path

  1. Settings - Wi-Fi.
  2. Click the (i) next to the current Wi-Fi.
  3. Scroll down to find "Configure DNS".
  4. Change to "Manual".
  5. Delete existing servers below.
  6. Click "Add Server".
  7. Enter 1.1.1.1.
  8. Add 8.8.8.8 again.
  9. Save in the top right corner.

iOS Profile Method (Covers 4G)

If you want 4G to also use custom DNS:

  1. Open the 1.1.1.1 profile download page provided by Cloudflare in Safari.
  2. After downloading, install it in Settings - General - VPN & Device Management.
  3. Once the profile is active, 4G will also use encrypted DNS.

Changing DNS on Android

Method 1: Modify a Single Wi-Fi

  1. Settings - Wi-Fi - Long press current connection - Modify network.
  2. Advanced options - Change IP settings to Static.
  3. Manually fill in IP and Gateway, otherwise the network will disconnect.
  4. Enter 1.1.1.1 for DNS1.
  5. Enter 8.8.8.8 for DNS2.
  6. Save.

Method 2: Private DNS (Global Effect)

  1. Settings - Network & internet - Advanced - Private DNS.
  2. Select "Private DNS provider hostname".
  3. Enter 1dot1dot1dot1.cloudflare-dns.com.
  4. Save, effective for both Wi-Fi and 4G.

Method 3: DoH Encryption

Android 9 and above support DoT. Optional hostnames:

  • dns.google (Google)
  • dns.quad9.net (Quad9)
  • dns.adguard-dns.com (AdGuard)

Quick Check for Common DNS Error Codes

Different error codes from the browser represent different problems. Use the table below for quick positioning:

Error Code Meaning Is it a DNS Problem?
DNS_PROBE_FINISHED_NXDOMAIN Domain does not exist or has no resolution record Yes, changing DNS usually solves it
DNS_PROBE_FINISHED_NO_INTERNET No internet connection at all No, check the network
DNS_PROBE_FINISHED_BAD_CONFIG Local DNS configuration is abnormal Yes, restore auto or change DNS
ERR_NAME_NOT_RESOLVED Domain name resolution failed Yes
ERR_CONNECTION_TIMED_OUT DNS resolution successful but IP is unreachable No, it's a blockade or line issue
ERR_CERT_AUTHORITY_INVALID Certificate chain anomaly No, SSL layer issue

If it's the last two types of errors, changing DNS alone won't solve it, and further IP/SSL layer handling is needed.

Router-Level DNS Modification

Changing DNS for the router is more convenient than for every device, as it covers all connected devices (including smart TVs and speakers).

General Steps

  1. Access 192.168.1.1 or 192.168.0.1 in the browser to enter the router background.
  2. Log in with the administrator account (default is usually admin/admin; check the label on the back if unsure).
  3. Find the "Network Settings" or "WAN Settings" page.
  4. Change "DNS Server" from "Auto" to "Manual".
  5. Fill in 1.1.1.1 for Primary DNS and 8.8.8.8 for Secondary DNS.
  6. Save and restart the router.
  7. Reconnect devices to Wi-Fi to inherit the new DNS.

Common router brands (Xiaomi, Huawei, TP-Link, ASUS, Netgear) have slightly different menu paths. Look for the keyword "DNS" in "Advanced" or "Internet Settings" pages.

Handling Host File Anomalies

If changing DNS doesn't help, the local host file might be polluted or have incorrect mappings.

Windows Check

  1. Open C:\Windows\System32\drivers\etc\hosts in File Explorer.
  2. Open with Notepad as administrator.
  3. Check for entries involving binance or amazonaws.
  4. Delete extra lines (keep comments starting with # and 127.0.0.1 localhost).
  5. Save.

macOS / Linux Check

Execute in terminal:

sudo nano /etc/hosts

Similarly, delete suspicious entries, Ctrl+O to save, Ctrl+X to exit, and then flush DNS cache.

How to Tell if Host is Polluted

Execute ping binance.com. If the returned IP is 127.0.0.1 or 0.0.0.0 or another abnormal address, the host file has likely been modified.

How to Verify After Modification

Online Verification

Open 1.1.1.1/help in the browser. it will show the DNS you are currently using and whether DoH/DoT is enabled.

Command Line Verification

Windows:

nslookup binance.com

Check if the returned DNS Server is 1.1.1.1 and if the IP is a reasonable segment like 47.x or 3.x.

Mac/Linux:

dig binance.com

Check the SERVER field.

Browser Verification

Open binance.com. If the first screen loads, the resolution and connectivity are OK.

FAQ

Q1: What if the entire network slows down after changing DNS? A: It might be that the DNS you chose is too far away. Try a local DNS or a well-known one like 8.8.8.8. Use local DNS for speed and foreign DNS to bypass pollution.

Q2: Why is Binance still unreachable after changing DNS? A: This indicates it's not a DNS issue but an IP or TLS layer blockage. In this case, changing DNS won't help, and you need to solve it from other layers.

Q3: What if I can't change DNS on my company computer? A: If locked by enterprise policy, normal users can't change it. Coordinate with IT or enable DoH individually in the browser (Chrome supports this) to bypass system DNS.

Q4: Which is better, 1.1.1.1 or 8.8.8.8? A: Cloudflare 1.1.1.1 theoretically has lower latency and a stronger privacy commitment (logs deleted in 24 hours). Google 8.8.8.8 has a longer history and a reputation for stability. Filling in both is perfectly fine.

Q5: Will the ISP know if I change DNS? A: With plaintext DNS, ISPs can see which domains you are querying. After enabling DoH/DoT, ISPs can only see that you accessed 1.1.1.1, not the content of the queries.

Q6: Can I use AdGuard Home to build my own DNS? A: Absolutely. Building your own DNS with DoH forwarding to Cloudflare is an optimal solution and also allows for local ad filtering. Suitable for users with some technical foundation.

Summary

DNS is the first step in the entire internet link. Resolution failure will cause all requests to fail. In certain network environments, it is highly recommended to use 1.1.1.1 or 8.8.8.8 with DoH/DoT daily. It's not just helpful for Binance but for many international services. Follow the steps in this article for the four major platforms, and remember to clear the cache and run nslookup to verify. By getting the DNS layer right, you'll find the probability of "network anomalies" drops significantly.