Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
DNS spoofing redirects users to a fake site by injecting false DNS records. DNS translates a domain name such as www.example.com into the IP address a device uses to connect. MITRE's attack-pattern catalog CAPEC describes an attack in which the attacker alters the result of this translation and sends the user to a different address than intended.
How does DNS spoofing work?
If the number listing in a directory is changed, looking up the right name still connects you to the wrong place. The same thing can happen with a DNS query. IETF's RFC 3833 explains that a DNS query and its response are normally carried in a single UDP packet with no signature and no encryption.
This means an attacker who can intercept traffic in transit, or who delivers a false response before the genuine one arrives, can make the querying side believe any answer. RFC 3833 describes two paths: false responses that arrive before the legitimate one, and cases where the attacker guesses and matches the response. If the querying side verifies DNSSEC signatures — a mechanism that attaches a signature to DNS responses to detect tampering — a false response can be detected. For a wider review of DNS configuration, see the DNS misconfiguration page.
Why does DNS spoofing matter?
A user who types a correct URL can still be sent to a fake site. CAPEC explains that attackers use this technique to steer users toward sites that install malware, and for pharming — the practice of luring users onto a counterfeit site. Because the URL in the browser looks correct, users cannot detect the problem through their own attention.
JPCERT/CC issued an advisory in 2008 about a cache-poisoning weakness found in multiple DNS server products, calling for updates to fixed software. After the update, the source port for queries became randomized, which significantly reduced the attack risk. For organizations that run their own caching DNS server, keeping the software updated is a basic precaution. When false responses are stored in a cache, the effect on subsequent users is described on the cache poisoning page.
The free URL check shows how your domain's configuration looks from outside. For reviewing your DNS management setup, contact us.
Related terms
- Cache poisoning: an attack that replaces stored content with fake content.
- Man-in-the-middle attack: an attack that intercepts communication between two parties to read or modify it.
- Email spoofing: a technique that fakes the sender field to make a message appear to come from a trusted source.
- Subdomain takeover: a technique that claims an abandoned DNS name to serve content under a trusted domain.
Frequently asked questions
What is the difference between DNS spoofing and cache poisoning?
Both lead users to the wrong destination using false DNS information. The term cache poisoning refers specifically to cases where the false information is stored in a DNS cache and continues to affect subsequent users.
Can typing the correct URL still send me to a fake site?
Yes. CAPEC explains that when DNS results are altered, users go to the address the attacker specified rather than the intended one. Close the browser if it shows a certificate warning.
Next step
For a wider review of DNS configuration, see the DNS misconfiguration page. The free URL check shows how your domain settings appear from outside. To review your DNS management setup, contact us.
Frequently asked questions
What is the difference between DNS spoofing and cache poisoning?
Both lead users to the wrong destination using false DNS information. The term cache poisoning refers specifically to cases where the false information is stored in a DNS cache and continues to affect subsequent users.
Can typing the correct URL still send me to a fake site?
Yes. CAPEC explains that when DNS results are altered, users go to the address the attacker specified rather than the intended one. Close the browser if it shows a certificate warning.