6
1
After a recent Chrome update to v73, Chrome no longer uses my hosts file for IPv6 addresses. I have an entry like:
::1 some-project.test
Trying to go to https://some-project.test
results in ERR_NAME_NOT_RESOLVED
.
If I change the entry to 127.0.0.1
, the hostname resolves.
There's no problem with my hosts file entry. It's worked fine for months on previous versions of Chrome. I can ping some-project.test
. Firefox works fine. I can even run a proxy like Fiddler and Chrome can access it that way. I just can't use Chrome directly.
Any suggestions for working around this?
Update: It seems dependent on the network I'm connected to. After moving from a public WiFi network back home, this is working again. I'm not sure how that's possible... shouldn't the hosts file override anything in DNS? And, shouldn't Chrome be using the system resolver anyway? Everything else on the system does and works fine.
Update 2: Back on home wired Ethernet... broken again. The problem is intermittent.
I can confirm Chrome 73 absolutely uses the hosts file on Windows. There is some other unidentified reason you are unable to navigate to the
.test
domain you have configured. – Ramhound – 2019-04-04T22:12:40.067@Ramhound It's using the hosts file for me, but not for IPv6 entries. It only works for IPv4 entries in the hosts file. Can you confirm that IPv6 hosts file entries are working for you in Chrome v73? Thanks. – Brad – 2019-04-04T22:14:20.340
According to https://stackoverflow.com/questions/42636711/google-chrome-ignoring-hosts-file, Chrome doesn't like
– Doug Deden – 2019-04-04T22:26:24.237.test
for some uses of the Hosts file. Trysome-project.local
instead, just to rule that out.@Brad - Then as somebody as specified it's the name of the domain your using not the fact it IPv6. Chrome 73 absolutely still uses the
– Ramhound – 2019-04-04T22:29:11.370hosts
file for both IPv4 and IPv6. Related@DougDeden Using
something.local
or even justsomething
doesn't work. Additionally,something.test
works just fine for IPv4 addresses. It also worked fine for IPv6 addresses yesterday. – Brad – 2019-04-04T22:37:42.700@Ramhound It's not a caching issue. Cache has been cleared and I'm usually operating with my dev tools open anyway with cache disabled. The hostname isn't resolving... I'm not even getting to a point where the cache could be used. No matter what name I try, it doesn't work for IPv6. – Brad – 2019-04-04T22:39:21.487
You flushed the cache after you change it to
– Ramhound – 2019-04-04T22:45:53.303something.local
and obviously made the required changes to your web project?@Ramhound Yes, yes. Just updated the question... turns out this starts working again after switching networks. Very strange behavior. – Brad – 2019-04-05T05:12:07.373
@davidbaumann Yes, pinging works fine, as mentioned in the question. So does everything else. Just Chrome seems to be the issue. – Brad – 2019-04-05T14:27:25.667
Since only IPv6 has problem on some networks, is it possible that these networks do not support IPv6? – harrymc – 2019-06-24T15:57:22.587
@harrymc The problem is intermittent on some networks, whether they support IPv6 or not. And, I would expect
::1
to always work anyway, as I have IPv6 enabled on my machine. Indeed,::1
works, and the hostnames work in all applications except Chrome intermittently. – Brad – 2019-06-24T15:58:36.487Does Chrome give an error code when it fails? – harrymc – 2019-06-24T16:04:49.587
@harrymc Yes,
ERR_NAME_NOT_RESOLVED
. – Brad – 2019-06-24T16:05:27.003