151–160 of 174 posts
For us laymen, why would you need/want a domain name for a home network?
So you don't need to memorize and hard-code IP addresses for your network services. * router.home.arpa * nas.home.arpa * printer.home.arpa * htpc.home.arpa
Earlier quoted context omitted.
> Don’t use .local (except for mDNS.) Going forward, I agree. However for many years, the recommendation from large providers (including Microsoft) WAS to use .local I've got .local as my internal network. For some people, it's not a trivial job to re-domain everything.
Microsoft had .corp as a placeholder for years, intending admins to input their own domains. (Which many promptly never did.) However, I'm not aware of them ever recommending or using .local for anything.
I 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.
The name system is a unique non-renewable resource. And it's not like ICANN gave people a lot of choice for unregistered domains.
By your logic, I suppose .onion was not fine either, till cca 2015 when it got special-use status? And all the name system alternatives should be abolished, because we need to rent their TLDs to some uninterested party?
Earlier quoted context omitted.
.lan should be OK, it has no it’s own RFC, but it is a reserved domain nevertheless: https://datatracker.ietf.org/doc/html/rfc6762#appendix-G
> We do not recommend use of unregistered top-level > domains at all, but should network operators decide to do this, the > following top-level domains have been used on private internal > networks without the problems caused by trying to reuse ".local." for > this purpose: This is hardly ‘reserved’. It just describes existing practice without in any way designating it as safe, recommended or future-proof.
Honestly, 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…
Earlier quoted context omitted.
You can use ZZ freely, as it's an ISO 3166 code reserved for private use. AA, QM to QZ and XA to XZ are also reserved.
Not exactly. The RFC that would make it safe is draft status, and the draft is set to expire in https://tools.ietf.org/id/draft-ietf-dnsop-private-use-tld-0... > are thought to be plausible choices for the implementation of private namespaces
[ISO3166 clause 8.1.3] "User assigned code element":
"If users need code elements to represent country names not included in this part of ISO 3166, the series of letters AA, QM to QZ, XA to XZ, and ZZ, and the series AAA to AAZ, QMA to QZZ, XAA to XZZ, and ZZA to ZZZ respectively and the series of numbers 900 to 999 are available."
Earlier 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?
Earlier quoted context omitted.
So you don't need to memorize and hard-code IP addresses for your network services. * router.home.arpa * nas.home.arpa * printer.home.arpa * htpc.home.arpa
Yes, but that can be achieved by using a hostname alone (router, nas, printer, htpc...). What does the domain bring?
With all new gTLDs it’s easy to have a collision when someone buys the “router” TLD.
I 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 :)
This 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...