What is a common consequence of DNS cache poisoning?

What is a common consequence of DNS cache poisoning?

• A. Encrypting data in transit
• B. Redirecting users to malicious websites
• C. Improving network speed
• D. Preventing phishing

Answer: (B)

DNS cache poisoning corrupts the information stored in a DNS resolver’s cache so that domain lookups return an IP address controlled by an attacker. When a user tries to reach a legitimate site, the browser ends up connecting to the attacker’s server instead. This is why redirecting users to malicious websites is the typical, and most common, consequence: the user is misdirected to a site that could phish for credentials, host malware, or perform other harmful actions. The other options don’t fit because DNS cache poisoning doesn’t provide encryption for data in transit, nor does it improve network speed. In fact, while DNS caching is meant to speed up lookups, poisoning undermines trust and can create security risks. And it certainly doesn’t prevent phishing; it can enable it by guiding users to fraudulent sites.

DNS cache poisoning corrupts the information stored in a DNS resolver’s cache so that domain lookups return an IP address controlled by an attacker. When a user tries to reach a legitimate site, the browser ends up connecting to the attacker’s server instead. This is why redirecting users to malicious websites is the typical, and most common, consequence: the user is misdirected to a site that could phish for credentials, host malware, or perform other harmful actions.

The other options don’t fit because DNS cache poisoning doesn’t provide encryption for data in transit, nor does it improve network speed. In fact, while DNS caching is meant to speed up lookups, poisoning undermines trust and can create security risks. And it certainly doesn’t prevent phishing; it can enable it by guiding users to fraudulent sites.