During a security audit on a corporate Windows 11 desktop, an analyst observes that entering `payroll.internal` into any web browser redirects the user to a suspicious external landing page. Executing `nslookup payroll.internal` in the command prompt successfully returns the correct internal IP address (`10.0.4.25`). Additionally, browser inspection reveals no active extensions, proxy configurations, or custom DNS-over-HTTPS settings. Which of the following locations should the analyst inspect FIRST to locate the root cause of the redirection?
- The local operating system hosts fileCevap
- BThe Internet Options Connections tab within Control Panel
- CThe browser temporary web cache and session cookies
- DThe Windows Defender Firewall inbound policy rules
Cevap
The local operating system hosts file
In Windows, standard network applications (such as web browsers) check the local `hosts` file before issuing DNS queries to remote servers. Conversely, command-line diagnostic tools like `nslookup` query DNS servers directly. Because `nslookup` resolved the domain name correctly while browsers redirected to an unwanted address—and because browser extensions and proxy settings were ruled out—the redirection is caused by a malicious or modified entry in the local `hosts` file (`C:\Windows\System32\drivers\etc\hosts`).
Adım Adım Çözüm
Anahtar Kavram
Windows Name Resolution Order and Hosts File Hijacking
Tahmini Süre:2m 0s