Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What domain name to use for your home network

ctrl.blog

Post reply on HN
Print view View original

131–140 of 174 posts

Re: What domain name to use for your home network

#131

Post by KaiserPro »

This isn't networking advice, but its what I've done either professionally and for home in some limited cases.

For fee paying networks, the "router" will most likley be in charge of some sort of DNS. If thats the case its made canonical for a subdomain that one owns. If you're lazy, just plain split horizon. However limit it strictly to DHCP. As soon as you start re-writing public services, you're sunk.

Side note, its a really good time to start putting in location data into subdomains. using option 60(might not be this, its been a while) you can work out what switch the request came from and add a different subdomain based on that you can make subdomains like server01.rack3.datacenter.country.company.com. this allows you to make search params to create local services. ie "time" would first check rack3, then datacenter, then country, then company.

Re: What domain name to use for your home network

#132

Post by KaiserPro »

KaiserPro wrote: post #131

This isn't networking advice, but its what I've done either professionally and for home in some limited cases. For fee paying networks, the "router" will most likley be in charge of some sort of DNS. If thats the case its made canonical for a subdomain that one owns. If you're lazy, just plain split horizon. However limit it strictly to DHCP. As soon as you start re-writing public services, you're sunk. Side note, it…

also my home domain name is "phartiphuckballs.com"

Re: What domain name to use for your home network

#133

Post by soraminazuki »

tedk-42 wrote: post #123
charles_f wrote: post #99

Earlier quoted context omitted.

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

'exposing your internal infra' I've worked in gov places where they care about this detail. It's quite a sad 'security by hiding' mentality. Oh no someone knows my current IP is 192.168.0.100

I'm pretty sure some people would be interested if they figured out you have a subdomain named say, name-your-password-manager.example.com. Motivated attackers could then attempt to exploit your password manager through websites you're likely to visit.

Re: What domain name to use for your home network

#134

Post by pwdisswordfish8 »

Symbiote wrote: post #103
nucleardog wrote: post #73

Earlier quoted context omitted.

I'm with ya. I use `.zz`. It's short, easy to type, and in order for that to be assigned out, we'd need an entirely new country to be created (one that decided the other bazillion free CCTLDs are not to their liking). And like you say, I only run into a problem if I decide I want to access things from said country. Would I do this in any professional setting? Absolutely not. For my own stuff at home? The risk is pret…

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

Re: What domain name to use for your home network

#135

Post by maccard »

inetknght wrote: post #31
thundermuffin wrote: post #28

Earlier 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 hope you never forget to renew that registration...

Decent registrars provide auto renewal, and terms of multiple years. They also email you in advance of a card expiration and domain expiration. At a certain point you have to take some responsibility.

Re: What domain name to use for your home network

#136

Post by maccard »

manquer wrote: post #71
thundermuffin wrote: post #34

Earlier quoted context omitted.

I agree! It always boggles my mind how people and companies can forget to renew their domain names when you receive so many email reminders now a days.

It is quite easy, the original owner/ responsible PoC left long ago, or the email goes to an barely read inbox/ group or bounces completely. If a task only recurs less frequently like say every 3-5 years, it is more likely to be forgotten it is the same whether it is individual or companies.

If that person leaves or the notifications are ignored that would happen with any method that involves any interaction whatsoever. At a certain point someone has to take some amount of responsibility for this, and if they don't it's going to fail _eventually_.

Re: What domain name to use for your home network

#137

Post by Spivak »

inetknght wrote: post #31
thundermuffin wrote: post #28

Earlier 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 hope you never forget to renew that registration...

This is a non-issue when you can pick a registrar (i.e. Route53) that will auto-renew for you.

Re: What domain name to use for your home network

#138

Post by Spivak »

willis936 wrote: post #130
minimaul wrote: post #35

Earlier quoted context omitted.

And as an extra point - can you actually guarantee that all your DNS lookups hit your DNS server first? That's harder than it sounds, with more and more apps implementing their own DNS over HTTPS clients - Firefox does it for instance, so does Chrome.

If you run your own router: yes up to a certain point. https://www.myhelpfulguides.com/2018/07/30/redirect-hard-cod... Afaik nobody has a fix for the client hostility that DoH brings to the table.

I think the fact that I can slurp, block, and/or modify all the unencrypted DNS requests of every device on my network to be the hostile thing.

Yes we have all abused unencrypted DNS to take the littlest bit of control back from hostile devices but we’re the minority of a minority who lose out in this situation where everyone else is now shielded from random sketchy Wi-Fi hotspots, and their ISP.

Re: What domain name to use for your home network

#139

Post by wellthisishn »

d2wa wrote: post #55
ASalazarMX wrote: post #53

Earlier quoted context omitted.

Mixing LAN and Internet scopes makes me uneasy. In my LANs the local domain is .local, because .local is one of the reserved top domain names, and it shouldn't be resolvable outside the LAN. https://tools.ietf.org/id/draft-chapin-rfc2606bis-00.html#rf...

Read the article. Don’t use .local (except for mDNS.)

They don't give a reason. I don't believe the author. I think it will not only technically work fine, but it's a good idea and better than using what the author suggests.
Post reply on HN