Skip to content
DnsCloud

Public DNS · Recursive resolver

Quicker answers for every lookup.

DnsCloud Public DNS resolves domain names to IP addresses quickly and reliably, so browsing and apps feel more responsive on any device or office network.

resolve.log
query  example.com. Acache  MISS → recursechain  . → com. → example.com.dnssec secureanswer 203.0.113.10  ttl=300query  example.com. Acache  HIT  ttl=287

Recursive resolver

Overview

Every time someone opens a website or an app connects to a service, a resolver has to find the right IP address. Many networks simply use whichever resolver came with the connection, which may be slow, overloaded or not validating answers.

Public DNS gives individuals and small businesses a dependable alternative. It answers from cache when it can, resolves everything else efficiently and validates DNSSEC-signed answers, so tampered responses are not passed on.

Key features

  • Smart caching

    Frequently requested answers are served from cache and refreshed according to each record’s TTL, so repeat lookups return quickly without serving stale data.

  • DNSSEC validation

    Signed responses are checked against the chain of trust. Answers that fail validation are rejected instead of reaching your device.

  • IPv4 and IPv6

    Resolves A and AAAA records alike, so devices reach services over whichever protocol is available.

  • Built-in abuse protection

    Rate limiting and traffic filtering protect the resolver from misuse and keep it responsive for legitimate users.

  • Simple setup

    Nothing to install. Point a device or your office router at the resolver and every connected device benefits.

How it works

A lookup takes a few steps. Public DNS keeps each one short.

  1. 01

    Your device asks

    A browser or app needs the address for a name such as example.com and sends the query to Public DNS.

  2. 02

    Cache check

    If a valid answer is already cached, it is returned straight away.

  3. 03

    Recursive resolution

    Otherwise the resolver queries the root, TLD and authoritative servers, validating DNSSEC signatures along the way.

  4. 04

    Answer returned

    The verified address goes back to your device and is cached for the record’s TTL.

Typical use cases

  • Home and personal use

    More responsive browsing and validated answers on laptops, phones and home routers.

  • Small offices

    Configure it once on the office router to give every device consistent, reliable resolution.

  • Retail and guest Wi‑Fi

    Dependable resolution for point-of-sale systems and guest networks, where downtime is visible to customers.

  • Remote teams

    A consistent resolver for staff working across different home and mobile networks.

Frequently asked questions

What are the resolver addresses?

Resolver addresses and setup guidance are provided when you get started. Contact us for details.

Will changing my DNS make my internet faster?

It shortens the lookup that happens before a connection is made, which can help pages and apps start loading sooner. It does not change the bandwidth of your connection.

Does Public DNS validate DNSSEC?

Yes. Signed answers are validated, and responses that fail validation are not returned to your device.

Can I use it for my whole office?

Yes. Setting it on your router or DHCP server applies it to every device on the network. We can help with the configuration. Contact us for details.

Next step

Ready to switch resolvers?

Tell us about your devices or office network and we will send setup guidance.