On Sun, 4 Aug 2024 12:59:55 +0000
Andy Smith <a...@strugglers.net> wrote:
> Hi,
>
> On Sat, Aug 03, 2024 at 10:08:55PM +0000, Andrew M.A. Cater wrote:
> > > On 8/3/24 09:00, Andy Smith wrote:
> > > > If you use .local for other things it can interfere with mDNS
> > > > but picking almost anything else has very few repercussions
> > > > (unless you are very silly about it), so I don't understand why
> > > > this topic always generates so much debate on this list.
> >
> > Part of the reason it generates more heat than light, Andy, is
> > because off-topicness creaps in.
>
> I've been thinking about it and I also wonder if it's because
> home.arpa is relatively new and weird-sounding so anyone who's been
> around for a while probably does not use it themselves. When certain
> such people read a post that says that home.arpa is the standard
> they somehow feel personally called out ("they're saying I'm
> NON-COMPLIANT!?") and compelled to either question it, argue it or
> simply state a personal anecdote about what they use on their
> network and why it is okay / has always been okay.
>
> So I want to emphasise again that while standards are useful so
> we're all on the same page, in this particular case it's not a big
> deal, likely nothing terribly bad is going to happen to you even if
> you do squat on some already-allocated TLD let alone a possible
> future one. We should just accept what the standard is and consider
> it next time we set things up.
>
>
Exactly. I've run a DHCP server since about 2010, and used one of my
own domain names in my network since 2006. I know what to do about
external resources on the same domain, not that I have any at the
moment. I've never had any kind of networking trouble that is
associated with using that internal domain name.
--
Joe
