What domain name to use for your home network
1–10 of 174 posts
Re: What domain name to use for your home network
#2> 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...
Re: What domain name to use for your home network
#3Interesting, but I don't understand how to set this up. If I go into my router's admin pages (it's a Ubiquiti EdgeRouterX), then Services, then DNS... the only options are:
DNS Forwarding
Cache size
Interface (currently set to Switch0)
(Add DDNS interface)
Re: What domain name to use for your home network
#4In similar news, do not use "dev.host", because someone owns it[0] and can and will do increasingly hilarious things to your traffic.
[0] me
Re: What domain name to use for your home network
#5> 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 percentage of all queries being for bogus domains that don't exist.
Re: What domain name to use for your home network
#6The 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 of such high-risk strings would be deferred indefinitely." [1]
[1]https://features.icann.org/addressing-new-gtld-program-appli...
Re: What domain name to use for your home network
#7> 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.
Re: What domain name to use for your home network
#8IMO 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.
Re: What domain name to use for your home network
#9What if it's an office building?
Re: What domain name to use for your home network
#10> 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…
Does this happen often? How do they mitigate this?