Public Resolver

Public DNS, on our own network.

Three resolvers on the same anycast network worldwide. One answers everything; one refuses ads, trackers and known malware; one adds DNS64 for IPv6-only networks. All speak plain DNS, DNS over HTTPS, DNS over TLS and DNS over QUIC, and none keeps a log of what you asked.

01

Addresses

Unfiltered

Resolves everything, filters nothing.

  • IPv4177.177.83.83
  • IPv62602:f3ff:83::83
  • DoHhttps://dns.yunzheng.space/dns-query
  • DoT / DoQdns.yunzheng.space

Filtered

Refuses ads, trackers and known malware.

  • IPv4177.177.83.84
  • IPv62602:f3ff:83::84
  • DoHhttps://filter.dns.yunzheng.space/dns-query
  • DoT / DoQfilter.dns.yunzheng.space

DNS64

No filtering; a name with no IPv6 address is answered with one under 64:ff9b::/96. Only for IPv6-only networks that hand that prefix to a NAT64 gateway.

  • IPv4177.177.83.64
  • IPv62602:f3ff:83::64
  • DoHhttps://dns64.dns.yunzheng.space/dns-query
  • DoT / DoQdns64.dns.yunzheng.space
02

Where the answer comes from

AnycastThree visitors in three regions ask the same address. Each is answered by the location nearest to it, inside one network.Visitorregion AVisitorregion BVisitorregion CNearestlocationNearestlocationNearestlocationour network, one address everywhereThe route picks the location. The address never changes.
Each address above is announced from every location at once, so the resolver a device reaches is the one nearest to it. Which location that is can change without anything on the device changing.
03

What we keep

Nothing that says who asked for what. The resolvers keep no per-query log at all — not the name, not your address, not a hash of either. What does exist is counters, and they are counted in a way that cannot be turned back into a query: how many queries a node answered, how many were filtered, the mix of record types and results, and — separately — which networks and countries traffic arrived from and which names were popular. The last two are counted independently and never combined, so no stored record associates a network with a name. A name is counted only after it has been requested at least 50 times on one node within one five-minute window. Your address is used to look up a network and a country and is then gone. There is no account, nothing to sign in to, and nothing to sell.

04

Limits

A network gets 500 queries per second per node, counted per /24 or per /64 rather than per address, and the allowance refills continuously. Going over it does not block anything: address lookups are answered with a page that says what happened, and everything else gets an empty answer so mail and service lookups fail cleanly rather than being pointed at a web server. A household resolver typically issues fewer than 1 query per second in total, so the limit is not reached by ordinary use.

05

Questions

Where is the privacy policy?

At /public-resolver/privacy/ — specific to this resolver, not a site-wide document. It says exactly what is counted and what is not.

Is it free?

Yes, for everyone, with no account. It is run by a non-profit laboratory as a public service.

Do you log my queries?

No. There is no per-query log — not the name, not your address, not a hash of either. Only aggregate counters that cannot be attributed to anyone.

What is the difference between the two addresses?

177.177.83.83 resolves everything as it is. 177.177.83.84 refuses names on ad, tracker and malware lists and answers those with a short notice instead.

I saw this address in my firewall log. What is it?

It is a public DNS resolver. If a device on your network is talking to it, that device is using it to look up names — either because it was configured to, or because an app chose an encrypted resolver on its own.

Does it validate DNSSEC?

Yes. A name whose signatures do not check out is refused rather than answered, and an answer we proved genuine comes back with the authenticated-data flag set. Names that are not signed at all — still most of the internet — resolve normally: being unsigned is not a failure. If you validate on your own device, ask with the checking-disabled bit and we will not second-guess you.