Why is Chrome ignoring /etc/hosts on OS X?
www.youtube.com to your hosts file.
youtube.com is redirected permanently to
www.youtube.com, so as long as you have visited
youtube.com once, your browser caches this response and redirects you to
www.youtube.com. This address isn't in your hosts file, so chrome logically resolves it correctly.
Google Chrome ignores your hosts file and does actual DNS lookups (despite what others may think,
/etc/hosts is not part of DNS, it is what was used prior to DNS). While Google Chrome should be honoring those hosts file entries it does not. The hosts file, being an alternative to DNS, will be read when no DNS server is available (like if you disabled your network connection).
You can test this by adding "127.0.0.1 foobar.dev" to your hosts file, then enabling wireshark and watching on your network interface. Open up Chrome and put
http://foobar.dev/ in your address bar and go. You'll see a DNS query in Wireshark, something like:
2 1.668727000 192.168.32.104 126.96.36.199 DNS 75 Standard query 0x663a A foobar.dev
FWIW, Google DNS returns 127.0.53.53 for foobar.dev.
3 1.706484000 188.8.131.52 192.168.32.104 DNS 91 Standard query response 0x663a A 127.0.53.53
A workaround would be to use HostAdmin which is an older Chrome extension that makes Chrome use the hosts. However, newer versions of Chrome (>38, apprently) no longer support it.
I fixed this problem by: Turn OFF "Protect you and your device from dangerous sites" in Chrome's Advanced Preferences.
Chrome's built in "protection" includes checking a domain against their own DNS directly and bypassing certain types of host entries it deems "suspicious" or entries for sites that exist that are being overridden, which means most custom host entries are ignored. Especially *.dev and *.local entries used for development.
Turning this off has resolved the issue 100% of the time for me. This was driving me mad for months when doing local development and i couldn't find the answer listed anywhere, everyone just kept saying it couldn't be happening. Turns out it was a simple toggle in advanced settings. Hope this helps you as well, cheers.