What makes a DNS resolver “open”?

A DNS resolver looks up answers on behalf of a client. When someone enters a domain name, their device usually asks a resolver for information such as the address needed to reach the site. A recursive resolver may contact other DNS servers, cache what it learns and return an answer to the client.

An open resolver accepts recursive queries from clients beyond its intended users. That can happen when a resolver meant for a home, office or hosting network is reachable from the internet without suitable access restrictions. Some public recursive services are intentionally available to broad audiences; being publicly reachable does not by itself mean a service is misconfigured. The concern is an operator unintentionally offering recursion to anyone, without the controls needed to manage abuse.

How reflection and amplification work

DNS commonly uses UDP, which does not establish a connection before sending a reply. An attacker on a network that permits forged source addresses may send a DNS query that appears to come from a victim’s address. The resolver then sends its answer to that victim instead of to the sender. This redirection is called reflection.

Amplification occurs when the reply is larger than the query that prompted it. Certain legitimate DNS answers can be relatively large, depending on the records requested and the server’s configuration. If many requests with a forged source address reach one or more willing resolvers, the resulting replies can add unwanted traffic to the victim’s connection. The attacker has not made the victim ask for those answers; the victim receives them because its address was placed on the requests.

Not every DNS exchange produces a large reply, and protections may limit the size or rate of responses. The key risk is the combination of spoofable requests, a server willing to answer them and replies sent to someone who did not request them. An open resolver can therefore become a participant in an attack even when its owner has no intention of harming anyone.

Why the distinction between DNS servers matters

A recursive resolver and an authoritative DNS server have different jobs. A resolver finds answers for clients, while an authoritative server publishes answers for the domains it serves. Restricting who may use recursion is an important defense for a private resolver. An authoritative server, however, generally needs to answer queries from the wider internet so that people can reach its domains. Simply blocking all unfamiliar clients would defeat that purpose.

Authoritative servers can also be used for reflection under some conditions, but their safeguards differ. Operators may use appropriate response-rate controls and other server-specific protections while keeping legitimate answers available. For either type of server, measures that limit abuse should be tested carefully: overly broad blocking can make ordinary lookups fail.

Practical ways to reduce the risk

If you operate a resolver for a particular network, limit recursive service to the clients that should use it. Review both the resolver’s access settings and the firewall rules that govern who can reach it. Remember to check IPv4 and IPv6 where both are in use. A configuration that looks private on one address or interface may still be reachable on another.

Keep DNS software maintained and review the defensive options supported by your chosen server. Depending on the deployment, these may include limits on query or response rates and controls for unusually large responses. Networks can also help at a different point in the chain by filtering packets with forged source addresses. That filtering reduces the opportunity to launch reflection attacks; it is not something a resolver operator can accomplish solely by changing DNS records.

DNS records for a domain do not normally determine whether a separate recursive resolver is open. Changing an A, MX or TXT record is therefore not a substitute for checking the resolver service itself. If a provider manages your DNS infrastructure, clarify whether it operates authoritative DNS, recursive DNS or both before requesting a configuration change.

Check exposure without disrupting service

Start with an inventory: identify which systems run DNS software, what role each system plays and which networks are supposed to query it. From an authorized location outside the intended client network, check whether a private resolver answers recursive requests. Use your provider’s approved diagnostic tools or procedures, and avoid sending repeated or high-volume test traffic.

If you find unintended access, restrict it and then confirm that approved clients can still resolve names. Watch normal service logs or traffic summaries for unexpected query sources and unusual response volumes, while handling any logged client information according to your organization’s practices. A small, deliberate configuration review is more useful than waiting for a complaint: it helps keep DNS available to legitimate users without offering an unnecessary path for reflected traffic.

Back to category ↗