Hacker News Reader

Comment by nhance | Hacker News Reader

If this doesn't happen or takes too long, there's always lacolhost.com and *.lacolhost.com. I own this domain, have registered it out until 2026 and vow that the domain and all subdomains will always redirect to localhost.

It's easy to type and easy to remember and should always do a good job of expressing intent of usage.

View on HN

I don't think that quite fits into the security model of many of the purposes for which people use localhost, as they often want to avoid all external dependencies (including Internet access!) and all external trust.

If they do use your domain name then they have to trust that nobody has subsequently seized the name in court, nobody has hacked or DDOSed your nameservers, there's not an interruption of network connectivity between them and your servers, and that the ISPs forwarding the DNS queries didn't substitute a different response for the one you intended to return (since currently your leaf records aren't DNSSEC-signed).

The issue they are trying to solve is that the DNS request might be sent somewhere at all (and thus manipulated). So your solution doesn't address that (as it guarantees a request is sent)

Could it be you were hanging on #css on irc on a network I can't remember more than 10 years ago ? (there usually were only 5 of us there). I seem to remember someone owning a domain like that.

i'm not really sure why i'm saying this, but you should put an AAAA record there too, so people can benefit from ipv6 loopback, haha

It would make more sense for someone to setup localhost.mydomain.com than to trust a third party.

I wonder if lacolhost.com is just an A record pointing to 127.0.0.1, what would be the use-case to use that instead of just using 127.0.0.1? Is it that some systems require a domain to be used/tested?

lacolhost.com should also resolve to the ipv6 record for localhost.

Being able to test locally while using the full internet name resolution system is a valuable thing as well. Though if this is your use case I wouldn't trust lacolhost: register your own domain.

It doesn't though. Unless I'm missing something obvious, it only has an A record, not a AAAA.

The problem with things like this is that they won't resolve without an internet connection.

You're amazing. I hope you're given more power than you already have.

If people use this in production services, he will have much more power over their services.

I don't think (?) I've ever made this typo. How many hits do you get?

(I feel like "ocalhost", "locahost", or "localhos" would be more common typos.)

I have no clue, it's all handled by the registrar's DNS. I know when it last expired I was getting a good number of emails from people begging for it to come back asap.

The other commentators here are right, it won't solve a good number of the issues in this proposal, but works well if you need something for developing against subdomains.

localhost would be a good name for a bar in SF.

I keep trying to go to this hip new bar called localhost, but somehow directions just lead me to drinking at home.

I lol'd

The anagram alcolhost would be a nice one too

"St Alcohol" and "Alcohol St" are also good anagrams

Did you think of that on your own? God I feel dumb. (I like being made to feel dumb) I googled it and didn't get that answer. I guess remembering ST can be a street or saint is a good rule.

There's the Network Operation Center Network Operation Center.

https://www.yelp.com/biz/noc-noc-san-francisco

Right next to a Foo Bar

It's a tech community center in Philadelphia: http://localhostphilly.com/

this is an actually good idea - it's still a good name if you have no idea where it comes from or what it means

Reply on news.ycombinator.com