I just use a real domain name, so I can easily obtain LE certs. Only the internal DNS server will actually return internal addresses.
This is a no brainer for any serious setup. We use our main domain to add subdomains which point to local services.
What domain name to use for your home network
91–100 of 174 posts
Re: What domain name to use for your home network
#92I just use a real domain name, so I can easily obtain LE certs. Only the internal DNS server will actually return internal addresses.
A real domain name is the way to go. The convenience of using LE wildcard certificates is huge. However, running split-horizon DNS is not straightforward, at least in a home setting. I don't see a huge problem with putting a couple of internal addresses in external DNS servers. lexicon cloudflare --auth-token $(gopass cloudflare) create my-real-domain.xyz A --name my-rpi --content 192.168.1.201
Split horizon:
I run DNSMasq on port 53, to serve DHCP and local DNS queries. DNSMasq forwards queries it can't answer (queries for "real" domains) to Unbound on port 1053.
It's not split horizon, because Unbound only serves the LAN - I don't serve DNS to the world - and because Unbound isn't an authoritative nameserver. But it's not that hard to make DNSMasq serve zones, and it's not hard to make DNSMasq serve those zones only to queries from the intarwebs, and serve the DHCP 'zone' to local queries.
And anyway, I guess you could use something ugly like BIND instead of Unbound, if you need an industrial-grade authoritative DNS server facing the internet.
Re: What domain name to use for your home network
#93Earlier quoted context omitted.
> (...) 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.
>... even those that don't exist, the whole purpose of root servers? The root servers shouldn't be a dumping ground for unnecessary traffic when proper DNS configuration is not that difficult.
I'm not sure you're getting it. You're complaining about a scenario where there's a misconfiguration error that's totally unintentional. No one is intentionally driving traffic to domains that don't exist. In fact, of said traffic hits the root servers, odds are that the system is effectively down and not receiving the traffic it's expected to receive, and a few developers are trying to figure out what's broken.
Re: What domain name to use for your home network
#94Honestly, 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…
> Honestly, just spend the five bucks a year and reserve a real domain name with auto renew.
It really doesn't make much sense to propose as a solution to a potential configuration problem subscribing to a service with the goal of never using it.
It wouldn't be far-fetched to suggest reserving a subdomain of a domain you already own and use for that specific purpose, but paying for a subscription just to configure your internal DNS doesn't sound reasonable at all.
Re: What domain name to use for your home network
#95I think it’s safe to assume that the one gtld ICANN will never sign off on - even if they sell .home, .lan, and everything else - is .icann
So if they won’t give us a tld to use, just use that :)
Re: What domain name to use for your home network
#96I 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 t…
Delegating .dev was fine. Sick of hearing about this. As the meme goes, "well, well, well, if it isn't the consequences of my own actions." Everyone who got burned by .dev got what they deserve and needs to grow up already, take responsibility for themselves, and get over it.
Re: What domain name to use for your home network
#97Earlier quoted context omitted.
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
Are you arguing that the person should have used example.com in their comment as an example domain or are you suggesting people use a subdomain of example.com for their home network?
You're acting smug but nobody can tell why right now
Re: What domain name to use for your home network
#98I think it’s safe to assume that the one gtld ICANN will never sign off on - even if they sell .home, .lan, and everything else - is .icann So if they won’t give us a tld to use, just use that :)
What if they start using it?
Re: What domain name to use for your home network
#99Honestly, 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…
This would still forward your unresolved to public DNS, exposing your internal infra, which as I understand it is one of the things this article is looking at preventing
Re: What domain name to use for your home network
#100Earlier quoted context omitted.
I'm not saying your wrong, but frankly, it's 2021, and it should be a lot easier than this to set up hosts internally for home use. We've largely had the internet broadly for the last 25 years, and the average person should not have to be an expert on wildcard certs/DNS/zeroconf if they want to just have a server running locally. In fact, that's part of the reason things have gone to the cloud, because what should be…
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?