←back to thread

.localhost Domains

(inclouds.space)
301 points todsacerdoti | 6 comments | | HN request time: 0.001s | source | bottom
Show context
hardaker ◴[] No.43644486[source]
You might check out .internal instead which was recently approved [1] for local use.

[1]: https://en.wikipedia.org/wiki/.internal

replies(7): >>43644727 #>>43644836 #>>43645467 #>>43645484 #>>43645535 #>>43648046 #>>43656960 #
1. alexvitkov ◴[] No.43645535[source]
Too much typing, and Chromium-based browsers don't understand it yet and try to search for mything.internal instead, which is annoying - you have to type out the whole http://mything.internal.

This can be addressed by hijacking an existing TLD for private use, e.g. mything.bb :^)

replies(3): >>43645793 #>>43646358 #>>43653062 #
2. tepmoc ◴[] No.43645793[source]
eh, you can just add search domain via dhcp or static configuration and just type out http://mything/ no need to enter whole domain unless you need todo ssl
replies(1): >>43649588 #
3. nsteel ◴[] No.43646358[source]
Isn't just typing the slash at the end enough to avoid it searching? e.g. mything/
replies(1): >>43652354 #
4. ◴[] No.43649588[source]
5. jeroenhd ◴[] No.43652354[source]
mything/ will make the OS resolve various hosts: mything., mything.local (mDNS), mything.whateverdomainyourhomenetworkuses. (which may be what you wanted).

If you want to be sure, use mything./ : the . at the end makes sure no further domains are appended during DNS lookup, and the / makes the browser try to access to resource without Googling it.

6. thaumasiotes ◴[] No.43653062[source]
> Chromium-based browsers don't understand it yet and try to search for mything.internal instead, which is annoying

That's hardly the only example of annoying MONOBAR behavior.

This problem could have been avoided if we had different widgets for doing different things. Someone should have thought of that.