Public DNS server list
Public resolvers and Chinese carrier DNS by province, with official sources, purpose and live test results
Check the test node and time at the top, then search by name, province, carrier or IP; green badges mean the address resolved from this site’s test node.
About the test results
- Test node
- 中国 福建 厦门 · 中国电信
- Tested at
- Method
- TCP port 53, 3 rounds; queries www.baidu.com and a random .invalid name
- IPv6
- The test node has no IPv6 connectivity; IPv6 addresses were not tested
- Summary
- 357 addresses: 81 resolved, 27 refused, 249 no response or error
Results only reflect this test node’s network at the time shown, and latency includes TCP connection setup, so treat it as a rough guide. Carrier DNS usually serves only its own subscribers, so no response from elsewhere does not mean failure. The test node’s network intercepts UDP 53, so this run used TCP; servers that answer only over UDP also show as no response. Confirm on your own network.
Public recursive DNS 18 entries · 58 addresses
Recursive resolvers offered to the public. Addresses listed on official pages show the check date; those found only in third-party directories or community lists are labeled separately.
| Name and purpose | IPv4 and result | IPv6 and result | Source |
|---|---|---|---|
AliDNS
Alibaba Cloud Plain resolution
DoH https://dns.alidns.com/dns-query DoT dns.alidns.com
|
|
|
Official source checked (2026-11-07) alidns.com |
Tencent Public DNS (DNSPod)
Tencent Cloud Plain resolution
DoH https://doh.pub/dns-query DoT dot.pub
|
|
|
Official source checked (2026-11-07) cloud.tencent.com/document/product/302/110786 |
| 114DNS (standard) Nanjing Xinfeng Plain resolution |
|
— | Official source checked (2026-11-07) 114dns.com |
| Baidu Public DNS Baidu Plain resolution |
|
— | Official source checked (2026-11-07) dudns.baidu.com |
360 Secure DNS
Qihoo 360 Plain resolution
The official page labels 101.226.4.6 and 218.30.118.6 for China Telecom networks; 101.198.198.198 and 101.198.199.200 appear in its DoT example.
DoH https://doh.360.cn/dns-query DoT dot.360.cn
|
|
— | Official source checked (2026-11-07) sdns.360.net/dnsPublic.html |
| 360 Secure DNS (China Unicom) Qihoo 360 Plain resolution The current 360 page lists only the China Telecom addresses; this Unicom pair comes from a third-party directory. |
|
— | Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers |
| Volcengine PublicDNS (ByteDance) Volcengine Plain resolution |
|
— | Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers |
| OneDNS (pure) ThreatBook Plain resolution |
|
|
Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers |
| CNNIC SDNS CNNIC Plain resolution The official site is online but no longer lists these addresses, so current public availability cannot be confirmed. |
|
— | Community list, not officially confirmed |
Google Public DNS
Google Plain resolution
DoT dns.google
|
|
|
Official source checked (2026-11-07) developers.google.com/speed/public-dns/docs/using |
| Cloudflare 1.1.1.1 Cloudflare Plain resolution |
|
|
Official source checked (2026-11-07) developers.cloudflare.com/1.1.1.1/ip-addresses |
Quad9 (malware blocking)
Quad9 Foundation Security filtering
Quad9’s recommended addresses block known malicious domains by default; the unfiltered service is 9.9.9.10 and 149.112.112.10.
DoH https://dns.quad9.net/dns-query DoT dns.quad9.net
|
|
|
Official source checked (2026-11-07) quad9.net/service/service-addresses-and-features |
Quad9 (unsecured)
Quad9 Foundation Plain resolution
DoH https://dns10.quad9.net/dns-query DoT dns10.quad9.net
|
|
|
Official source checked (2026-11-07) quad9.net/service/service-addresses-and-features |
| OpenDNS Cisco Plain resolution |
|
|
Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers |
| DNS.SB Plain resolution |
|
|
Official source checked (2026-11-07) dns.sb/guide |
| Oracle OCI recursive DNS (formerly Dyn) Oracle Plain resolution Oracle documents this recursive service as free for anyone and DNSSEC-validating. |
|
— | Official source checked (2026-11-07) docs.oracle.com/en-us/iaas/Content/DNS/Concepts/recursive-dns.htm |
| Quad101 (TWNIC) TWNIC Plain resolution |
|
|
Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers |
| Verisign Public DNS Verisign Plain resolution Mislabeled on the reference site as a Swiss bank. No current Verisign service page was found; only a third-party directory still lists it, so rely on test results. |
|
|
Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers |
Filtering and security DNS 11 entries · 36 addresses
Block malicious, adult or advertising domains according to the provider’s rules. Blocked sites will not load, so these are not suitable as plain resolvers when troubleshooting.
| Name and purpose | IPv4 and result | IPv6 and result | Source |
|---|---|---|---|
| 114DNS (security) Nanjing Xinfeng Security filtering Blocks phishing, virus and trojan sites. |
|
— | Official source checked (2026-11-07) 114dns.com |
| 114DNS (family) Nanjing Xinfeng Family filtering Adds adult-content blocking. |
|
— | Official source checked (2026-11-07) 114dns.com |
| Cloudflare (malware blocking) Cloudflare Security filtering |
|
|
Official source checked (2026-11-07) developers.cloudflare.com/1.1.1.1/ip-addresses |
| Cloudflare for Families Cloudflare Family filtering Blocks malware and adult content. |
|
|
Official source checked (2026-11-07) developers.cloudflare.com/1.1.1.1/ip-addresses |
| OpenDNS FamilyShield Cisco Family filtering |
|
— | Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers |
| CleanBrowsing Security Filter CleanBrowsing Security filtering |
|
|
Official source checked (2026-11-07) cleanbrowsing.org/filters |
| CleanBrowsing Adult Filter CleanBrowsing Adult-content filtering Mislabeled on the reference site as a California resolver. Adult sites are blocked, so it is not a general-purpose resolver. |
|
|
Official source checked (2026-11-07) cleanbrowsing.org/filters |
| CleanBrowsing Family Filter CleanBrowsing Family filtering |
|
|
Official source checked (2026-11-07) cleanbrowsing.org/filters |
| AdGuard DNS (default) AdGuard Ad filtering Blocks ads, trackers and phishing by default, which can break some site features; the unfiltered version is 94.140.14.140 and 94.140.14.141. |
|
|
Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers |
| OneDNS (block) ThreatBook Security filtering |
|
|
Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers |
| OneDNS (family) ThreatBook Family filtering |
|
— | Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers |
China Telecom · carrier DNS 29 entries · 77 addresses
Carrier DNS addresses by province from community lists, as carriers do not publish a single official list. They usually serve only subscribers on that carrier in the same province; use and test them there.
| Name and purpose | IPv4 and result | IPv6 and result | Source |
|---|---|---|---|
| China Telecom IPv6 Plain resolution | — |
|
Community list, not officially confirmed |
| Beijing China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Shanghai China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Tianjin China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Chongqing China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Anhui China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Fujian China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Gansu China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Guangdong China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Guangxi China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Guizhou China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Henan China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Heilongjiang China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Hubei China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Hunan China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Jiangsu China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Jiangxi China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Inner Mongolia China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Shandong China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Shanxi China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Shaanxi China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Sichuan China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Yunnan China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Zhejiang China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Hebei China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Hainan China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Liaoning China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Jilin China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| Xinjiang China Telecom Plain resolution |
|
— | Community list, not officially confirmed |
China Unicom · carrier DNS 31 entries · 59 addresses
Carrier DNS addresses by province from community lists, as carriers do not publish a single official list. They usually serve only subscribers on that carrier in the same province; use and test them there.
| Name and purpose | IPv4 and result | IPv6 and result | Source |
|---|---|---|---|
| China Unicom IPv6 Plain resolution | — |
|
Community list, not officially confirmed |
| Beijing China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Shanghai China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Tianjin China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Chongqing China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Guangdong China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Hebei China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Henan China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Heilongjiang China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Jilin China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Jiangsu China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Inner Mongolia China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Shandong China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Shanxi China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Shaanxi China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Sichuan China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Zhejiang China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Liaoning China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Guizhou China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Gansu China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Ningxia China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Jiangxi China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Guangxi China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Tibet China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Hainan China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Hunan China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Hubei China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Anhui China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Fujian China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Xinjiang China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
| Yunnan China Unicom Plain resolution |
|
— | Community list, not officially confirmed |
China Mobile · carrier DNS 33 entries · 122 addresses
Carrier DNS addresses by province from community lists, as carriers do not publish a single official list. They usually serve only subscribers on that carrier in the same province; use and test them there.
| Name and purpose | IPv4 and result | IPv6 and result | Source |
|---|---|---|---|
| China Mobile IPv6 Plain resolution | — |
|
Community list, not officially confirmed |
| Beijing China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Shanghai China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Tianjin China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Chongqing China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Anhui China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Shandong China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Shanxi China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Jiangsu China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Zhejiang China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Hunan China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Hubei China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Jiangxi China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Shaanxi China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Sichuan China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Guangdong China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Guangxi China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Guizhou China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Fujian China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Hebei China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Henan China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Gansu China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Heilongjiang China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Jilin China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Liaoning China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Yunnan China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Hainan China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Inner Mongolia China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Xinjiang China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Tibet China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Qinghai China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Ningxia China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
| Hong Kong China Mobile Plain resolution |
|
— | Community list, not officially confirmed |
China Tietong · carrier DNS 1 entries · 2 addresses
Carrier DNS addresses by province from community lists, as carriers do not publish a single official list. They usually serve only subscribers on that carrier in the same province; use and test them there.
| Name and purpose | IPv4 and result | IPv6 and result | Source |
|---|---|---|---|
| Guangdong China Tietong Plain resolution |
|
— | Community list, not officially confirmed |
China Broadnet · carrier DNS 2 entries · 4 addresses
Carrier DNS addresses by province from community lists, as carriers do not publish a single official list. They usually serve only subscribers on that carrier in the same province; use and test them there.
| Name and purpose | IPv4 and result | IPv6 and result | Source |
|---|---|---|---|
| Guangdong China Broadnet Plain resolution |
|
— | Community list, not officially confirmed |
| Pearl River Broadband (Guangdong) Plain resolution |
|
— | Community list, not officially confirmed |
Great Wall Broadband · carrier DNS 1 entries · 2 addresses
Carrier DNS addresses by province from community lists, as carriers do not publish a single official list. They usually serve only subscribers on that carrier in the same province; use and test them there.
| Name and purpose | IPv4 and result | IPv6 and result | Source |
|---|---|---|---|
| Guangdong Great Wall Broadband Plain resolution |
|
— | Community list, not officially confirmed |
Topway · carrier DNS 1 entries · 1 addresses
Carrier DNS addresses by province from community lists, as carriers do not publish a single official list. They usually serve only subscribers on that carrier in the same province; use and test them there.
| Name and purpose | IPv4 and result | IPv6 and result | Source |
|---|---|---|---|
| Guangdong Topway Plain resolution |
|
— | Community list, not officially confirmed |
Hong Kong, Taiwan and overseas 14 entries · 20 addresses
DNS addresses of regional carriers and organizations, mostly from community lists without official confirmation. Overseas resolvers add latency from mainland China and may return different answers.
| Name and purpose | IPv4 and result | IPv6 and result | Source |
|---|---|---|---|
| Chunghwa Telecom HiNet Chunghwa Telecom Plain resolution |
|
— | Community list, not officially confirmed |
| HKBN (Hong Kong Broadband) HKBN Plain resolution |
|
— | Community list, not officially confirmed |
| Hong Kong Plain resolution |
|
— | Community list, not officially confirmed |
| Hong Kong · Hutchison Plain resolution |
|
— | Community list, not officially confirmed |
| Singapore Plain resolution |
|
— | Community list, not officially confirmed |
| Singapore Plain resolution |
|
— | Community list, not officially confirmed |
| Japan · Tokyo Plain resolution |
|
— | Community list, not officially confirmed |
| Japan · Kanagawa Plain resolution |
|
— | Community list, not officially confirmed |
| South Korea · Seoul Plain resolution |
|
— | Community list, not officially confirmed |
| South Korea · Seoul Plain resolution |
|
— | Community list, not officially confirmed |
| South Korea · KT Plain resolution |
|
— | Community list, not officially confirmed |
| Malaysia · Kuala Lumpur Plain resolution |
|
— | Community list, not officially confirmed |
| Philippines · Manila Plain resolution |
|
— | Community list, not officially confirmed |
| Vietnam · Long An Plain resolution |
|
— | Community list, not officially confirmed |
Cloud-internal DNS 2 entries · 9 addresses
Resolvers that cloud providers offer to their own servers, not public DNS for home broadband.
| Name and purpose | IPv4 and result | IPv6 and result | Source |
|---|---|---|---|
| Tencent Cloud Private DNS default servers Tencent Cloud Plain resolution Intended for servers inside Tencent Cloud VPCs, not a public resolver for home broadband. |
|
— | Official source checked (2026-11-07) cloud.tencent.com/document/product/1338/106568 |
| Huawei Cloud addresses (from the reference list) Huawei Cloud Plain resolution No Huawei Cloud documentation publishes these as public resolvers. Its intranet DNS is assigned per region; check the cloud console. |
|
— | Community list, not officially confirmed |
Retired or unconfirmed old addresses 7 entries · 10 addresses
Addresses whose service was officially retired, that no longer appear in official documentation, or that were mislabeled on the reference site. Kept for lookup; not recommended for use.
| Name and purpose | IPv4 and result | IPv6 and result | Source |
|---|---|---|---|
| Norton ConnectSafe (retired) Norton Plain resolution Norton states that ConnectSafe was retired on November 15, 2018. |
|
— | Not recommended support.norton.com/sp/en/in/norton-utilities/16.0/solutions/v53246991 |
| DNS.SB former address DNS.SB Plain resolution DNS.SB now lists 45.11.45.11 as its second address; this one is no longer listed. |
|
— | Not recommended |
| DNSPod former address Tencent Cloud Plain resolution Current Tencent Public DNS documentation lists only 119.29.29.29 for IPv4. |
|
— | Not recommended |
| OneDNS former address ThreatBook Plain resolution Not among the currently listed OneDNS addresses. |
|
— | Not recommended |
| Baidu Public DNS IPv6 (from the reference list) Baidu Plain resolution Baidu currently lists only the IPv4 address 180.76.76.76. | — |
|
Not recommended |
| V2EX DNS Plain resolution No current official documentation was found. |
|
— | Not recommended |
| Level 3 (Lumen) resolvers Lumen Plain resolution Mislabeled on the reference site as Microsoft Cloud. These belong to Level 3 (now Lumen) and are not an officially public service. |
|
— | Not recommended |
No matching entries. Try another keyword or group.
Test on your own network
Browsers cannot send raw DNS queries, so run these commands in a terminal, replacing 223.5.5.5 with the address to test:
dig @223.5.5.5 www.baidu.com A
dig +tcp @223.5.5.5 www.baidu.com A
dig @223.5.5.5 test-random.invalid A
nslookup www.baidu.com 223.5.5.5
- The first command uses UDP and the second TCP; “status: NOERROR” with ANSWER records means the server resolves.
- The third command queries a nonexistent name and should show “status: NXDOMAIN”; an IP answer means redirection.
- Ping alone is unreliable: many DNS servers ignore ping, and answering ping does not mean resolving.
Example
Input
Search for 223.5.5.5
Example result
AliDNS · plain resolution · official source checked · 223.5.5.5 resolves from the test node
You can also search by province (e.g. Fujian), carrier (e.g. Unicom) or provider name; tick the option to show only addresses that resolved from the test node.
Technical details & limits
Testing uses script/dns_probe.php, which sends two real DNS queries to every address: an A query for www.baidu.com and a random name under the RFC 6761 reserved .invalid TLD, which must return NXDOMAIN; an IP answer means nonexistent-domain redirection. Timeout is 4 seconds with 1 retry. Before testing, the script queries RFC 5737 documentation addresses and aborts if any answer, since that means local DNS interception. Results only reflect the test node’s network and time; carrier DNS usually serves its own subscribers, so no response from elsewhere does not mean failure.
About this tool
A directory of public recursive resolvers, filtering resolvers, provincial DNS for China Telecom, Unicom, Mobile and other carriers, regional resolvers in Hong Kong, Taiwan and abroad, cloud-internal DNS, and retired or unconfirmed old addresses. Each entry states its source (official page with check date, third-party directory or community list) and purpose (plain, security, family or ad filtering), and every address shows live results from this site’s test node. Search by name, province, carrier or IP and copy addresses with one click.
How to use
- Read the test node, protocol and time at the top to understand what the results cover.
- Search by name, province, carrier or IP, or filter by group; carrier groups are collapsed by default.
- Copy an address and test it on your own network with the dig/nslookup commands at the bottom.
Input & output
- Input
- Name, province, carrier or IP keywords (up to 40 characters).
- Output
- DNS addresses (IPv4/IPv6), DoH/DoT endpoints, purpose, source and test-node results.
- Limits
- Your browser does not send DNS queries here; results come from this site’s test node and do not represent your network. Authoritative NS records are not covered.
Notes
Changing DNS can affect speed and reachability. Filtering resolvers block some sites; use carrier DNS only on that carrier’s network in the matching province.
FAQ
- How should I choose between 114DNS, AliDNS and Tencent DNS?
- No resolver is best for every network. 223.5.5.5, 119.29.29.29 and 114.114.114.114 have all been checked against their official pages. Use two different providers for primary and secondary DNS, and run dig against each about 3 times from your own connection to compare response times, because results depend heavily on your carrier, province and current routing conditions. Avoid filtering resolvers when you only need plain lookups.
- Why do many carrier DNS servers show no response?
- Carrier DNS servers usually serve port 53 only to their own subscribers in that province, so queries from other networks often time out or return REFUSED, which is RCODE 5. That does not mean the server has stopped working. To judge a carrier DNS server fairly, test it from a broadband or mobile connection on that carrier in the matching province.
- How can I tell whether a DNS server redirects or hijacks lookups?
- Query a name that cannot exist, such as a random label under .invalid. RFC 6761 reserves that top-level domain, so an honest resolver must answer NXDOMAIN, which is RCODE 3. If the server returns an IP address instead, it redirects nonexistent names somewhere else, often to a search or advertising page, and this page marks such addresses in the results.
Related tools