Automatically update etc/hosts

[diegovogel]

Is Valet supposed to automatically update the etc/hosts file? I've heard that maybe it used to, but it doesn't anymore. There's no mention of the hosts file in the docs so it's unclear if this is a bug or a missing feature.

Anyway every time I use valet link I have to open up etc/hosts and add the new domain there. It would be great if Valet did this automatically.

[drbyte]

No, Valet doesn't touch the etc/hosts file. It doesn't need to.

Perhaps you have a custom DNS entry in your MacOS network configuration, ahead of 127.0.0.1, so that dnsmasq isn't getting called?

[diegovogel]

Ok thanks, good to know I shouldn't have to update the hosts file. I'm not sure what you mean by custom DNS entry. How would I check that?

[drbyte]

System Preferences->Network->Advanced->DNS

[diegovogel]

Oh gotcha. I set up a resolver to only send my local TLD (.off) to dnsmasq as outlined in option #2 here.

I think this may actually be a Chrome issue. If I ping any .off domain it resolves to 127.0.0.1 as expected.

And I just tested in Firefox and Safari and had no problem viewing my app. So only Chrome can't resolve the domain.

I've already tried clearing Chrome's DNS cache. Any idea what else I can try?

[diegovogel]

Finally got it to work! In case anyone else needs a solution: it was because of Chrome's secure DNS setting (chrome://settings/security). I switched it to "With your current service provide", but disabling it entirely would probably work too.

Other things I did along the way that may have helped:

• Cleared DNS cache: chrome://net-internals/#dns
• Flushed socket pools: chrome://net-internals/#sockets
• Cleared browsing data for all time: chrome://settings/clearBrowserData

@drbyte thanks for your help!