What about .localhost? Asking for a friend.
Works great for things you run on the same machine, less-so for LAN.
[deleted]
What domain name to use for your home network
61–70 of 174 posts
Re: What domain name to use for your home network
#62Re: What domain name to use for your home network
#63Earlier quoted context omitted.
Mixing LAN and Internet scopes makes me uneasy. In my LANs the local domain is .local, because .local is one of the reserved top domain names, and it shouldn't be resolvable outside the LAN. https://tools.ietf.org/id/draft-chapin-rfc2606bis-00.html#rf...
Read the article. Don’t use .local (except for mDNS.)
Now it's evident I answered reflexively without reading the article. I like the concept of ..local/localdomain so host names never collided when you connected through VPN from one to another. That can still be done with ..home.arpa, but it feels ugly. I guess I'll get used to it.
Re: What domain name to use for your home network
#64The blog post misses the (controversial if you're one of the ex-applicants) decision by ICANN to ban .corp, .home and .mail from ever appearing on the internet. So you've got those options too. Or in ICANN management-speak: "Whereas, the Board considered that the applicants were not aware before the application window that the strings .CORP, .HOME, and .MAIL would be identified as high-risk, and that the delegations…
It actually mentioned .home as something not to use (along with .lan and.homenetwork)
Re: What domain name to use for your home network
#65Weird, my Linksys WRT1900AC applies `.home` to its local DNS, but this article says not to?
Don’t use the .home domain. It was mistakenly recommended in RFC 7788. But that RFC was updated by RFC 8375 recommending the home.arpa domain. (RFCs are published by the IETF who manages the .arpa TLD. That’s one of the few TLDs not managed by ICANN for historical reasons. The .home TLD falls under ICANN’s root domain, so the RFC shouldn’t have assigned it.)
Ah, thanks. Oddly, it is the default and the current firmware won't let me change it.
Re: What domain name to use for your home network
#66Earlier quoted context omitted.
somedomain.com is not guaranteed not to interfere! example.com is guaranteed not to interfere (and example.org) http://www.iana.org/domains/reserved
I believe you took their post too literally; they mean to go register some domain you would like to have (such as ilovemycoolhouse.com or bearinabigblue.house) and use it, because the only way it will ever interfere with something is if you cause it to.
> I believe you took their post too literally; they mean to go register some domain you would like to have
yes, and that's EXACTLY what example.com is for, this precise circumstance
smh
Re: What domain name to use for your home network
#67The blog post misses the (controversial if you're one of the ex-applicants) decision by ICANN to ban .corp, .home and .mail from ever appearing on the internet. So you've got those options too. Or in ICANN management-speak: "Whereas, the Board considered that the applicants were not aware before the application window that the strings .CORP, .HOME, and .MAIL would be identified as high-risk, and that the delegations…
For non-TLDs, example.com is also good.
Re: What domain name to use for your home network
#68I truly do not understand why this problem has gone on for so long. It's clear that many people think `.home.arpa` is ugly. It boggles my mind that the IETF and ICANN can't come up with some agreement to get `.home` or something similar codified like RFC 7788 tried to do. This just seems like a fight between giant bureaucracies while meanwhile the users suffer and bad decisions like assigning `.dev` are made. I get that there are rules around this sort of critical infrastructure and its management, but come ON. /rant
With the rant ended: can anyone explain to me why all the relevant organizations can't get together and assign a TLD for this purpose that doesn't end in `.arpa`?
Re: What domain name to use for your home network
#69> Do not use undelegated domain names like .lan, .home, .homenet, .network, nor should you make up your own domain name. ...why? My DNS server, my rules, no? Why should I feel obligated to follow ICANN? Obviously, I'll need to make changes if someone ever registers the domain with ICANN (and I want to access the ICANN version), but other than that...
On your network, sure. But you seem to be on our network with all of us and so here you need to obey our rules or things won't go so well for you.
Oh yeah? What are you going to do? Complain that you can’t run the root nameservers and try to blackhole my traffic but fail since I am DHCP configured by my ISP?
Sounds like a toothless threat.
Re: What domain name to use for your home network
#70No mention of .internal
https://datatracker.ietf.org/doc/html/draft-wkumari-dnsop-in...
(Though maybe it's not a great name for this particular application, it seems to make a lot of sense for enterprise level infrastructure)