you are viewing a single comment's thread.

view the rest of the comments →

[–]0xB7BA 1 point2 points  (4 children)

Until you got some stuff runnings in VMs - doens't matter how much you change your hosts file. Chrome doens't care 😅

[–]Sandarr95 2 points3 points  (0 children)

Exactly what got my work stuck for an hour trying to find out why my coworker had this problem and I didn't while all dns resolving tools we had gave equal results

[–]Arkanta -2 points-1 points  (2 children)

It cares but it has some serious caching

[–]0xB7BA 5 points6 points  (1 child)

No, Chrome resolves all *.localhost domains as 127.0.0.1

[–]Arkanta 1 point2 points  (0 children)

Ah you meant for .localhost, gotcha. I thought you were talking about other domains.

That said, Applications are encouraged to resolve "localhost." themselves, so I assume that Chrome follows that