312-50 ยท Sniffing
Spoofing and DNS poisoning
MAC, IP spoofing, DNS cache poisoning, DNS spoofing, DNSSEC, and related detection.
Key points
- MAC spoofing copies another device's MAC address; IP spoofing forges the source address of packets.
- DNS cache poisoning plants forged records in a resolver so users get wrong IPs.
- DNSSEC defends by signing records so resolvers can verify origin and integrity; randomised source ports and IDs make forgery harder.
Practice questions
What does DNS cache poisoning do?
- Stores forged records in a resolver so users are sent to wrong IPs
- Fills a switch CAM table with fake MACs
- Exhausts the pool of DHCP addresses
- Encrypts all queries to the resolver
Show answer
Answer: A. Stores forged records in a resolver so users are sent to wrong IPs
The resolver caches a forged answer and serves it to every client until the TTL expires. The other options describe MAC flooding, DHCP starvation and encryption.
What does DNSSEC provide?
- Origin authentication of DNS data
- Integrity of DNS data
- Confidentiality of the queried names
- Protection from DDoS floods
- Hiding which sites a user visits
Show answer
Answer: A. Origin authentication of DNS data, B. Integrity of DNS data
DNSSEC adds signatures that prove records are genuine and unmodified. It does not encrypt queries or stop floods.
True or false: with IP spoofing the attacker normally receives the replies sent to the forged source address.
Show answer
Answer: False
False. Replies go to the address that was forged, not to the attacker, so spoofing is blind unless the attacker is also on the path (as in a man-in-the-middle).
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
