Re:What domain name to use for your home network
by d2wa on Sunday August 15, 2021 @10:13PM
(#28194325)
Read the article. Don’t use .local (except for mDNS.)
Re:What domain name to use for your home network
by ASalazarMX on Sunday August 15, 2021 @10:31PM
(#28194429)
Now it's evident I answered reflexively without reading the article. I like the concept of <server>.<location>.local/localdomain so host names never collided when you connected through VPN from one to another. That can still be done with <server>.<location>.home.arpa, but it feels ugly. I guess I'll get used to it.
Re:What domain name to use for your home network
by mattowen_uk on Monday August 16, 2021 @05:53AM
(#28196442)
> 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.
Re:What domain name to use for your home network
by d2wa on Monday August 16, 2021 @10:43AM
(#28198712)
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.
Re:What domain name to use for your home network
by k12sosse on Monday August 16, 2021 @12:58PM
(#28200260)
SBS (Small Business Server) pushed .local for YEARS.
Re:What domain name to use for your home network
by willis936 on Monday August 16, 2021 @07:42AM
(#28196979)
If your L2 DNS (hostnames, typically auto-generated) doesn't match your L3 DNS (handpicked) you're going to eventually have a Bad Time.
Re:What domain name to use for your home network
by wellthisishn on Monday August 16, 2021 @09:28AM
(#28197794)
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.
Re:What domain name to use for your home network
by WorldMaker on Monday August 16, 2021 @03:56PM
(#28202143)
They do give a reason: mDNS is a standard that was assigned .local. mDNS is useful for a number of reasons. (One of its original codenames was "Bonjour" if that helps connect the dots on how old mDNS is at this point.)
It's not worth the effort to break mDNS because lots of apps can use mDNS, it's a useful standard. In fact, in many LANs today (on modern operating systems inc. relatively recent versions of Windows 10 as Microsoft was one of the last to adopt mDNS) mDNS does almost everything people would want DNS to do in LAN scope anyway and you could get away with not assigning any local DNS and just using mDNS services.
https://tools.ietf.org/id/draft-chapin-rfc2606bis-00.html#rf...