DNS Infrastructure

For the full breakdown on the doxx.net DNS infrastructure please visit dev-dns.doxx.net.

Anyone can use our Public Recursive DNS which resolves all doxx.net domains (.doxx, .x , etc) plus all standard internet domains.

• 207.207.200.200
• 207.207.201.201

Our DNS threat classifier AI runs on doxx.net hardware so no queries leave to an outside service.

You can also use the public resolver for DNS protection without routing all your traffic through the network to protect lookups on their own.

1.Features

• Resolve both standard internet domains and names in doxx.net's namespace.
• Use doxx.net's own DNS infrastructure instead of your internet provider's resolver.
• Use personalized encrypted DNS when you want a tunnel's filtering policy without routing all device traffic through that tunnel.

2.Common Questions

What does a DNS resolver do?

It looks up the address associated with a domain name so your device knows where to connect. It's the step between entering a name and reaching the service behind it.

Do I need a tunnel to use the public resolver?

No. DNS can be used separately. That protects or filters lookups according to the DNS service you've configured; it doesn't create a full network tunnel.

Does resolving a .doxx name give me access to the service?

No. Finding its address and having permission to connect are separate things. The service may still require a doxx.net connection and the appropriate access rules.

Is entering a resolver IP enough to turn on encrypted DNS?

No. Use a DNS over HTTPS or DNS over TLS configuration if you want the DNS exchange encrypted. Just selecting a resolver's IP address doesn't establish either of those protocols.