Vvv: .dev domain namecollisions

[wturrell]

I'm finding, I can no longer access .dev sites served by vagrant from my (host) browser, even with the usual hosts file entries present and correct.

This is apparently due to something ICANN did on purpose – namely unused .dev and certain other domains are resolved to 127.0.53.53 to alert people to name collisions; .dev is now, or soon will be, a valid TLD…

Weirdly though, the hosts file entries added by hostsupdater (192.168.50.4 for vvv.dev and the various WordPress branches) are being ignored by everything except Google Chrome – no matter how many times I restart the browser / clear it's history / clear the OS X DNS cache etc.

1) is there a way to make the browser/system honour /etc/hosts regardless?
2) should we change .dev to something else in the project to avoid future confusion – e.g. .vvv?

[wturrell]

Asked about this on StackOverflow and subsequently discovered the cause; if /etc/hosts file is a symlink OS X does a DNS lookup first and only looks at /etc/hosts if it doesn't resolve.

Unclear why Chrome still worked (and it was only Chrome stable that did, not Canary.)

[cfoellmann]

I am on Windows and do not have the issue but I like the idea of using .vvv

[evelynriossf]

Thanks for this answer. I had a similar problem while using Bedrock with VVV. For me, the problem only manifested with Chrome 40.0.2214.111 (64-bit) on OSX, and not with any other browser (Firefox, etc..).
Changing .dev to .vvv fixed the problem, as it doesn't resolve. In the long run, VVV should change its conventions to not use .dev.

[jeremyfelt]

Interesting stuff. .dev has always been weird, though seemed appropriate. I wouldn't mind switching to .vvv at some point in a backward compatible way.

[morganestes]

Just to update this, I'm starting to get errors from ICANN when trying to view VVV sites in Chrome (47.0.2526.106 on OS X 10.11.2):

dial tcp 127.0.53.53:80: connection refused

I can view the site by IP in Chrome, and by domain name in Safari. Dig returns the message:

vvv.dev.        3599 IN TXT "Your DNS configuration needs immediate attention see https://icann.org/namecollision"

It looks like my hosts file is being ignored because sure, why not?

[evelynriossf]

Morganestes, could be a symlink issue. As Wturrell mentioned earlier in the thread " if /etc/hosts file is a symlink OS X does a DNS lookup first and only looks at /etc/hosts if it doesn't resolve." That was the same issue I encountered earlier this year.

[morganestes]

@evelynriossf I thought about that, but my hosts file isn't symlinked and I'm not running any other hosts files, either. It's only Chrome and dig that are having problems; Safari, Firefox, and ping all return the correct site.

I did a full halt and reload, and it's working again in the browsers (dig still returns the ICANN notices). This kind of thing is just going to keep creeping up as Google updates Chrome and ICANN starts to enforce new, unused TLDs.

[f4bsch]

Regarding long term support, there is no other option than .local or .localhost, since .vvv or .test or anything else might be available in (far) future. Google wants to take them all over http://tech.slashdot.org/story/15/02/28/1333231/google-taking-over-new-tlds

[GhostToast]

This issue just popped up for me overnight as well, and it turned out TunnelBear Chrome extension was engaged. In case that rings true for anyone else.

[jeremyfelt]

Aligning some things and closing this ticket in favor of #583. I should pay attention in the future as to what was opened first before linking to the other. :)

Thanks for the conversation here everyone!

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.