What domain name to use for your home network • Hacker News Board

Re: What domain name to use for your home network

#171

Post by flemhans » Fri, Aug 20, 2021, 1:27 PM UTC

geofft wrote: post #14

flemhans wrote: post #9

What 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.)

But homes could do that too.

I bet many homes have more money for domain names than some shops/offices.

Just wondering why they didn't call it 'localnet' or some other unused synonym for local.

Re: What domain name to use for your home network

#172

Post by livinginfear » Sat, Aug 21, 2021, 8:34 AM UTC

jannes wrote: post #125

livinginfear wrote: post #78

What method are people using to configure this oin their own network? The router supplied by my ISP doesn't support using a custom DNS server like a pihole, unfortunately. I don't consider using /etc/hosts a longterm worthwhile solution. I'd love to find another useful way of setting this up.

Does your router support disabling DHCP? You can just run your own DHCP server in that case.

It does. I might go with this option. It seems like it'll be easier than running the router in bridged mode, and adding another physical router.

Re: What domain name to use for your home network

#173

Post by pwdisswordfish8 » Sat, Aug 21, 2021, 10:24 PM UTC

tremon wrote: post #156

pwdisswordfish8 wrote: post #134

Earlier quoted context omitted.

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

The RFC may expire, but it quotes the ISO3166 guidelines as to why .zz is safe for personal use. Those guidelines will not change because of this draft: [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…

> The RFC may expire, but it quotes the ISO3166

This is not the argument you think that it is.

> zz is safe for personal use. Those guidelines will not change

Right. Safe for personal use within the range of uses for ISO 3166—guaranteed not to collide with any future two-letter country code. It's not a commitment from ICANN, which remains free to say, "ISO 3166 guarantees no collisions for AA. We choose, therefore, to open up bidding to auction off aa, which is expected to fetch a pretty penny as the first of a limited set of possible TLDs that are < 3 characters long."

Re: What domain name to use for your home network

#174

Post by pwdisswordfish8 » Sat, Aug 21, 2021, 10:26 PM UTC

labawi wrote: post #153

pwdisswordfish8 wrote: post #96

Earlier quoted context omitted.

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.

Delegating .dev was not fine. Does everything need to be for rent? 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?

> I suppose .onion was not fine either, till cca 2015 when it got special-use status?

You are correct.