Yeah, thanks for the insight, "bros."
What domain name to use for your home network
111–120 of 174 posts
Re: What domain name to use for your home network
#112> Your time is better spent ensuring all your devices support mDNS resolution Heh. I starred this Android feature request and kind of regret it because it's been a continuous stream of "+1" emails (but I want to stay subscribed in case some meaningful conversation happens at last): https://issuetracker.google.com/issues/140786115 (A login is required; any Google account will do)
Starred (not +1'd).
Re: What domain name to use for your home network
#113> 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...
Try using something under .local and see how much fun you have. That's what a former employer had set up for their internal environments. Worked great until mDNS came along and Apple devices insisted that .local had to go through mDNS rather than our DNS servers. The Mac users had a constant stream of complaints because of it: "I can't connect to the printer", "Shared drives don't work", "I can't access the CI enviro…
Place I worked at set up the network using .local around 2010 when mDNS was already common. Turns out the admin had seen/heard of .local and thought that's what it was for. A little knowledge is a dangerous thing...
Re: What domain name to use for your home network
#114> Your time is better spent ensuring all your devices support mDNS resolution Heh. I starred this Android feature request and kind of regret it because it's been a continuous stream of "+1" emails (but I want to stay subscribed in case some meaningful conversation happens at last): https://issuetracker.google.com/issues/140786115 (A login is required; any Google account will do)
I wonder which Android will support first, MDNS or DHCPv6?
Re: What domain name to use for your home network
#115IMO 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.
I’ve been doing that since the beginning of my career, I don’t know what’s so hard about this.
Re: What domain name to use for your home network
#116No 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)
I tried to get my company's IT department to put my latest project on a .internal domain. They wouldn't go for it, even though it can and will only be used by people internally. They bound it to a sub domain of the company's main web site claiming that Microsoft (maybe something with Active Directory? Or Azure?) doesn't support any domains that you don't actually own. I wouldn't be surprised if this is false because…
While it is certainly possible that a Microsoft-managed network places additional restrictions on what addresses are used, there are several good reasons to not to create unique "snowflake" situations for individual applications.
There might be silent assumptions everywhere what domain addresses answer to, in log collection, in monitoring, in address management tools. Simple things like domain search strings becomes harder. Any non trivial enterprise is going to have a ton of these (semi-)automated tools that your address will end up in.
It also carries the risk of complicating future work. The company might merge with another company. Or imagine a mandate where all communication will need to switch to TLS, only to discover there are addresses used under other domains internally.
Re: What domain name to use for your home network
#117Earlier quoted context omitted.
Give your local box a static IP from a LAN range, give it a name in .local or .lan domain, and you're likely fine. The more interesting stuff begins when you want several boxes, and also your laptops, phones, tablets, etc to form a reasonable LAN, while accessing the internet. Bonus points for remote access to your LAN from outside it using your laptop or phone. Etc, etc.
Why is a local domain useful? I mean, what's wrong with your local machines having only a hostname with no domain at all?
I haven't seen many real world software supports lookup remote with a hostname, probably windows itself is the only one that I have seen? Meanwhile, url is almost the universal way for lookup remote machine (besides, of course, IP).
Re: What domain name to use for your home network
#118My solution was to use a single domain for everything, with different locations broken out under their own subdomains. My colocated rack is "fmt2". VPSs are under normal IATA 3-letter codes. Homes, not just mine, are under " ". Internal services available for all homes are under "int". And so on. There are a bunch of reserved names under each to provide consistent access to per-location devices and services... "netwo…
I had set up some minecraft servers in my k8s homelab behind a proxy that routes clients to the right server depending on the domain name they're connecting to.
Everything inside the k8s homelab uses subdomains of k.myvanitydomain.com. The minecraft proxy is at mc.k.myvanitydomain.com. So, to connect to the "valinor" minecraft server, it's just valinor.mc.k.myvanitydomain.com. Dead simple (to me).
I tried explaining that to my kids and suddenly I knew what it was like for whoever explained to me the whole /ls//borg//bns/// setup from google prod
Re: What domain name to use for your home network
#119Honestly, just spend the five bucks a year and reserve a real domain name with auto renew. You don't need to make it publicly resolvable, but you'll be 100% sure all of your internal service names won't ever conflict with anything used in the real world. If you pick the right registrar, you can easily get your hands on a wildcard DNS cert as well through Let's Encrypt, so you can protect your internal services with H…
Lots of DNS servers won’t let you resolve to local IPs. Google’s public DNS does. So I do that but I have to set all my machines to use those DNS.
Re: What domain name to use for your home network
#120This still won't fix the bat-shit-stupid idea of browser developers to just forward anything they think is not resolvable (and often even if it IS a valid local FQDN) to the next best search engine...
IIRC all browsers try to perform name resolution if you append "/" at the end of your input in the address bar. After that fails they redirect to a search engine, but not before.