Skip to main content

Cache Poisoning vs DNSSEC

domains

Cache poisoning injects forged DNS answers into a resolver's cache, redirecting visitors to attacker-controlled servers until the entry expires. By contrast: DNSSEC cryptographically signs DNS records so visitors can detect tampering — a forged answer fails validation instead of silently redirecting traffic.

The pair is confused because both appear in the same settings screens and the same invoices. The working rule: when a requirement names cache poisoning, handle it there; when it names dnssec, 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