Skip to main content

Recursive Resolver vs DNS Caching

domains

A recursive resolver walks the DNS hierarchy on behalf of a client, querying root, TLD and authoritative servers, then caches the answer for its TTL. By contrast: DNS caching stores answers at resolvers and operating systems for the answer's TTL so repeated lookups are instant.

The pair is confused because both appear in the same settings screens and the same invoices. The working rule: when a requirement names recursive resolver, handle it there; when it names dns caching, handle it there. Settling that question before buying or configuring anything is what keeps the difference from costing rework later.

SteboHost support fields this comparison weekly — call +254 703 610 464 or write support@stebohost.com with the setup described in your own words, and the distinction will be applied to your case rather than quoted from a glossary.

Related topics