0

c:\Windows\System32\drivers\etc\hosts

213.213.213.213  ken.bone.com kenneth.bone.com

I'm using a clean profile in both Firefox and Chrome with all privacy settings and prefetching disabled.

Verified:

  • pinging domains returns the correct IP
  • In Chrome: ref
    • Unchecked all the boxes under Privacy settings
    • Checked if the DNS prefetching is really disabled by going to chrome://dns
    • Host cache is cleared chrome://net-internals/#dns
    • Everything has been cleared since the beginning of time
    • Tried the --disable-async-dns option in Windows

In FF's Dev Tools under Headers, the remote address is a local IP as expected.

In Chrome's Dev Tools under Headers, the remote address is the remote IP which is not expected.

Why is Chrome not respecting the Windows hosts file?

Running Chrome 53 and Firefox 49 on Windows 10

Community
  • 1
SomeGuyOnAComputer
  • 577

1 Answers1

0

Turns out my Work computer sets up an automatic configuration script known as a .pac (proxy autoconfiguration).

Steps to disable

  1. Settings > Network > Change Proxy Settings...
  2. Under Connections, click LAN settings, disable Use automatic configuration script
  3. Click OK
  4. For each Dial-up and Virtual Private Network settings and click Settings
  5. Repeat steps 2 and 3

This still seems like a Chrome problem to me because I feel that Chrome should respect my local hosts file before an automatic configuration script.

SomeGuyOnAComputer
  • 577