DNS resolver registry · Tencent Cloud

DNSPod Public DNS DNS servers

DNSPod Public DNS is run by Tencent Cloud and offers one service, reachable over DNS (53), DoT, DoH. Every address and endpoint below is taken from the operator's documentation; the behaviour is what we measured on 2026-09-24.
119.29.29.29
primary address
3
addresses in 1 variant
Does not validate
DNSSEC in our test
Sends /24
client subnet (ECS)
Addresses Check your resolver

Addresses

DNSPod Public DNS DNS addresses by variant

Set the IPv4 or IPv6 addresses as your DNS servers, or use an encrypted endpoint where one is listed.

DNSPod Public DNS

Not specified by the operator

IPv4
119.29.29.29
IPv6
2402:4e00::
2402:4e00:1::
DoH
https://doh.pub/dns-query
DoT
dot.pub

Measured

What we observed

Measured 2026-09-24 from one vantage point, three rounds per address, majority result. Anycast resolvers can behave differently from other networks. How we test

DNSSEC validation Does not validate

Returned addresses for dnssec-failed.org, rhybar.cz and badsig.go.dnscheck.tools, which a validating resolver would refuse.

Client subnet (ECS)

Sends /24. The authoritative server received that much of the client address, enough to locate a user to a block of addresses.

Plain DNS and NXDOMAIN

1/1 documented IPv4 addresses answered on port 53. Random non-existent names came back as NXDOMAIN, so errors are not rewritten into ads or search pages.

Encrypted endpoints

  • DoH https://doh.pub/dns-queryAnswered
  • DoT dot.pubAnswered

Networks

Which networks carry it

The announcing network comes from RIPEstat routing data for each documented address. The query network is where the resolver sent its own lookups during our probe, which a DNS leak test reports.

Announcing the service addresses

  • AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited
  • AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue

Queried from, in our probe

  • AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue

Check it

Confirm your device is using DNSPod Public DNS

Changing a DNS setting does not guarantee your lookups reach that resolver: a VPN, a browser's own secure DNS or a proxy can send them elsewhere. Our DNS leak test shows which resolvers actually received your queries.

From a terminal

# Which address did the resolver query from?
dig +short whoami.akamai.net @119.29.29.29

# Does it pass your subnet on (ECS)?
dig +short TXT o-o.myaddr.l.google.com @119.29.29.29

# Does it validate DNSSEC? SERVFAIL means yes
dig dnssec-failed.org @119.29.29.29

Behind a proxy

With an HTTP proxy, or a client set to socks5h://, the proxy side resolves hostnames, so your own resolver setting does not apply to that traffic. With socks5:// in curl or Python requests, your device resolves names first. The SOCKS5 vs SOCKS5h guide shows how to check which one you have.

Questions

DNSPod Public DNS questions

What are DNSPod Public DNS's DNS server addresses?

DNSPod Public DNS: 119.29.29.29, 2402:4e00::, 2402:4e00:1::.

Does DNSPod Public DNS validate DNSSEC?

Not in our 2026-09-24 test: it returned addresses for all three deliberately mis-signed domains.

Does DNSPod Public DNS support DNS over HTTPS or DNS over TLS?

DoH: https://doh.pub/dns-query. DoT: dot.pub. 2 of 2 answered our test query on 2026-09-24.

Does DNSPod Public DNS send my IP subnet to other servers (ECS)?

Yes on at least one address: we observed a /24 client subnet reaching the authoritative server.

How can I check that I am using DNSPod Public DNS?

Run a DNS leak test and compare the network it reports with the one DNSPod Public DNS queried from in our probe (AS132203). On the command line, dig +short whoami.akamai.net @119.29.29.29 returns the address the resolver used to query Akamai.

Sources

Sources and dates

Documentation checked 2026-09-24. Measured 2026-09-24. Registry reviewed 2026-09-24.

Compare

Other resolvers where DNSSEC does not validate

Comodo Secure DNS

8.26.56.26 · 8.20.247.20

DNSSEC: does not validate

Yandex DNS

77.88.8.8 · 77.88.8.1

DNSSEC: does not validate

AliDNS (Alibaba Cloud Public DNS)

223.5.5.5 · 223.6.6.6

DNSSEC: does not validate

114DNS

114.114.114.114 · 114.114.115.115

DNSSEC: does not validate

CIRA Canadian Shield

149.112.121.10 · 149.112.122.10

DNSSEC: does not validate

SafeDNS

195.46.39.39 · 195.46.39.40

DNSSEC: does not validate
All 20 resolvers

Research library

Network registries & open data

Find the reference behind a network decision. Browse the records, follow their sources and download the available datasets.

Explore research