DNS forwarder
What is DNS forwarder?
A DNS forwarder, defined in RFC 8499, is a nameserver that hands queries to another nameserver instead of walking the authoritative chain itself -- the common setup on home routers and small-office networks. AdminKit's guide to a hijacked router explains how to confirm which upstream resolver a device's forwarder is actually sending queries to.
By AdminKit team, Netbase JSC · Updated
A DNS forwarder is a nameserver that resolves DNS queries by handing them to another nameserver instead of walking the authoritative chain itself, defined in RFC 8499’s DNS terminology (document record at the IETF Datatracker) as sending a query with the RD (recursion desired) bit set rather than iterating through root, TLD and authoritative servers directly. Home routers and small-office DNS servers commonly run as forwarders, sitting between a device’s stub resolver and an upstream recursive resolver — often the ISP’s, or a public one like 1.1.1.1 or 8.8.8.8 — so the forwarder itself does little more than cache answers and pass queries on. Resolver software exposes the same role as configuration: in Unbound’s unbound.conf reference, a forward-zone named ”.” with a forward-addr target forwards all queries to that other server unless Unbound can answer them from its cache. Because a forwarder decides which upstream resolver every device on its network actually uses, a router quietly reconfigured to forward to an attacker-controlled resolver — without ever changing any individual device’s own DNS settings — is a common, easy-to-miss form of DNS hijacking. Separately, DNS cookies (RFC 7873) let a forwarder’s upstream resolver confirm a reply actually came from the query it sent, a narrower defense against off-path spoofing rather than against a forwarder reconfigured outright. A forwarder that also answers queries from the public internet rather than only its own network is a distinct misconfiguration — see open DNS resolver for why that’s routinely abused for amplification attacks.
Why a hijacked forwarder is easy to miss:
- It changes which upstream resolver every device on the network uses, all at once.
- No individual device’s own DNS settings ever need to change for this to work.
- The forwarder still answers queries normally, so there’s no obvious outage to notice.
DNS forwarder is part of AdminKit’s DNS cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
What makes a nameserver a forwarder rather than a recursive resolver?
Sending every query on with the RD (recursion desired) bit set to another nameserver, instead of iterating through root, TLD and authoritative servers itself -- RFC 8499's definition of forwarding.
Why is a hijacked DNS forwarder easy to miss?
Because it changes which upstream resolver every device on the network uses all at once, with no individual device's own DNS settings needing to change, and the forwarder still answers queries normally with no obvious outage.
Do DNS cookies stop a forwarder from being reconfigured to an attacker's resolver?
No -- DNS cookies (RFC 7873) let a forwarder's upstream resolver confirm a reply came from the query it sent, a narrower defense against off-path spoofing, not protection against the forwarder itself being reconfigured outright.
What's different about a forwarder that answers public internet queries?
That's a distinct misconfiguration called an open DNS resolver, routinely abused for DNS amplification attacks rather than the hijacking risk a forwarder's own upstream choice creates.