←back to thread

.localhost Domains

(inclouds.space)
301 points todsacerdoti | 1 comments | 10 Apr 25 14:19 UTC | HN request time: 0.199s | source
Show context
mohsen1 ◴[10 Apr 25 14:49 UTC] No.43644362[source]▶
Avoid using `.local`. In my experience Chrome does not like it with HTTPS. It takes much much longer to resolve. I found a Chrome bug relating to this but do not have it handy to share. `.localhost` makes more sense for local development anyways.
replies(8): >>43644412 #>>43644418 #>>43644420 #>>43644480 #>>43644481 #>>43644511 #>>43644548 #>>43646934 #
1. jeroenhd ◴[10 Apr 25 14:53 UTC] No.43644420[source]▶
I use .local all the time and it works just fine. For TLS I use my existing personal CA, but HTTP links don't cause issues for me.

That said, I do use mDNS/Bonjour to resolve .local addresses (which is probably what breaks .local if you're using it as a placeholder for a real domain). Using .local as a imaginary LAN domain is a terrible idea. These days, .internal is reserved for that.