Which DNS poisoning scenario uses a Trojan to modify a user's proxy settings to redirect to the attacker’s site?

Which DNS poisoning scenario uses a Trojan to modify a user's proxy settings to redirect to the attacker’s site?

• A. DNS cache poisoning
• B. Proxy server DNS poisoning
• C. Internet DNS poisoning
• D. Intranet DNS spoofing attack

Answer: (B)

This scenario focuses on how DNS poisoning can be carried out by tampering with a user’s proxy configuration, causing traffic to be routed through an attacker-controlled proxy. A Trojan on the victim’s machine changes the local proxy settings so that requests go to the rogue proxy instead of a legitimate one. That malicious proxy can then forward the traffic to attacker-controlled sites or return manipulated results, effectively redirecting the user’s DNS-enabled requests through the attacker’s path. This form of poisoning leverages the trust in the proxy path to redirect traffic, rather than directly altering DNS resolver caches. DNS cache poisoning, by contrast, involves corrupting the DNS data in a resolver’s cache to misdirect domain lookups, without necessarily changing the user’s proxy configuration. The terms internet DNS poisoning or intranet DNS spoofing are broader or vague and don’t specifically describe the act of altering a user’s proxy settings to force redirection through an attacker’s proxy.

This scenario focuses on how DNS poisoning can be carried out by tampering with a user’s proxy configuration, causing traffic to be routed through an attacker-controlled proxy. A Trojan on the victim’s machine changes the local proxy settings so that requests go to the rogue proxy instead of a legitimate one. That malicious proxy can then forward the traffic to attacker-controlled sites or return manipulated results, effectively redirecting the user’s DNS-enabled requests through the attacker’s path. This form of poisoning leverages the trust in the proxy path to redirect traffic, rather than directly altering DNS resolver caches.

DNS cache poisoning, by contrast, involves corrupting the DNS data in a resolver’s cache to misdirect domain lookups, without necessarily changing the user’s proxy configuration. The terms internet DNS poisoning or intranet DNS spoofing are broader or vague and don’t specifically describe the act of altering a user’s proxy settings to force redirection through an attacker’s proxy.