I use cozy.systems
What domain name to use for your home network
11–20 of 174 posts
Re: What domain name to use for your home network
#12> 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...
> My DNS server, my rules, no? That's the same line taken by network admins who think they know better than using RFC1918 IP ranges for their LAN.
Worked at a company which did this (dating back to when they probably figured they’d never need to connect to the net).
As a satellite office and an acquisition, we played all kinds of games to try to figure out whether we should send a given IP address out to the Internet or to corporate. Apple’s IP range was entirely overlapping and of course the corporate networking group just threw up their hands and said “send it to us; the internet is not a business critical function.”
This was in the early 2000s, not the early 90s.
Re: What domain name to use for your home network
#13> 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...
Does every single network client on your network use your DNS server for name resolution? No DNS-over-HTTPS? No widgets configured to talk to public DNS servers?
Also, does your DNS server correctly filter "out"-of-bailiwick responses for .lan etc. zones that are actually perfectly well in-bailiwick because they're from the actual delegated-by-the-real-root-servers nameservers, they're just not from your private server that you've configured? If not, I can execute a cache-poisoning attack against you.
Re: What domain name to use for your home network
#14What if it's an office building?
Buy a real domain name and use that. It is probably cheaper than a single square foot of office space.
(This can either be your normal domain name that you already have, using split DNS to make more things resolve on the internal network, or an entirely separate domain name, whichever is operationally easier for you.)
Re: What domain name to use for your home network
#15> 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.
Re: What domain name to use for your home network
#16> 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...
> My DNS server, my rules, no? That's the same line taken by network admins who think they know better than using RFC1918 IP ranges for their LAN.
I'm not suggesting this would be intelligent for anything larger than your own home network!
Re: What domain name to use for your home network
#17What about .localhost? Asking for a friend.
Re: What domain name to use for your home network
#18> 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...
The issue here being: what happens when you have your proxy configured as "proxy.lan" but you make a typo when entering it in local DNS or in your browser settings? That DNS request for "proxy.lan" will now go all the way out to the root servers for every page load, multiple times. Not so important for you with your 200 tabs open, but quite important to the people maintaining the root servers who see a significant pe…
> (...) but quite important to the people maintaining the root servers who see a significant percentage of all queries being for bogus domains that don't exist.
I get the boys out rule sentiment, but isn't resolving domain names, even those that don't exist, the whole purpose of root servers?
I mean, your suggestion reads like asking not to type URLs wrong because a significant percentage of requests are 404s.
Re: What domain name to use for your home network
#19IMO the best approach is to register somedomain.com and use its subdomains. It’s guaranteed not to interfere with anything, you can get LE certificate, you can make it available from the Internet if necessary.
That's what I do, local.domain.com.
I also have a wildcard le cert for *.local.domain.com.
Re: What domain name to use for your home network
#20"pennygetyourownwifi" works for me.