On 12/13/19 8:55 PM, David Wright wrote:
On Fri 13 Dec 2019 at 19:33:51 (-0500), Jape Person wrote:
Hi folks. Did I miss something?
Perhaps a couple of references:
https://features.icann.org/addressing-new-gtld-program-applications-corp-home-and-mail
which points out that any of .home, .mail and .corp are ideal for the
domain name of a home LAN, and RFC 6762 on Multicast DNS which
explains why .local is not a good choice.
Thank you very much, David. I'll dig into the documentation.
I could be quite wrong, but I thought that "local" was actually suggested as a domain name at one
time by the installer. (And I could be remembering a different distro, though I've been using Debian
for a long time -- at least 10 years, I think.) I suppose I just continued to use it over the years
out of habit.
I've had 3 Sid/testing systems running on the same LAN behind the same
router for just shy of 3 years. Their static IP addresses have always
been issued by the DHCP server on the router. Everything has been
copacetic among the systems, with local and outside name resolution
working with no issue.
A little over a week ago the systems stopped being able to access each
other by name. No changes were made in the settings or firmware of the
router or of the local network settings on the systems.
I discovered that all of the hostnames had changed from xxxxxx.local
to xxxxxx. I've tried to determine the cause of this alteration in the
hostnames on the LAN.
Everything is working fine now that I've stopped trying to call the
systems by the old xxxxxx.local names.
Could this change be due to recent upgrades in software? (I upgrade
every day.) I've reviewed the recent upgrades listed in
/var/log/apt/history.log. I would have thought any deliberate change
of this behavior would have been flagged by listchanges, but I can't
find it.
I'm just a home user / hobbyist, but this change occurring without any
deliberate administrative action on my part makes the hairs stand up
on my neck -- just a little bit.
Advice or consolation would be welcomed.
I tried .local quite a long while ago but it didn't work too well.
I don't know where the problem lay, and I got along with no domain
name for a longish period, but changed to .corp after I read the
first reference above. It stopped exim4 complaining too.
I have noticed that the speed of interactions (like logging on to ssh session, pinging, etc.) have
improved since .local went away.
But is it possible you've started using avahi/bonjour when previously
you didn't? Or has the router upgraded itself and now knows not to
issue names like that?
I'll check to see if avahi/bonjour are being used, but I haven't done anything deliberately to start
using them. I'm wondering if recent changes to CUPS may be implicated in some way. My Brother
printer defaults to using bonjour, but I turned it off because I deemed it to be not particularly
useful to me. It's connected by wire to the router. I live in a condo where I can see at least three
dozen (no kidding) printers advertising their services. I'm getting ready to switch everything to
wired connections.
The router is a Luxul. Its firmware must be upgraded manually. It has been at the latest firmware
version for almost a year.
Perhaps others have more/better ideas.
Cheers,
David.
Well, your ideas are certainly appreciated. I'm going to get a little education, I think, while I'm
following up on your message.
Best regards,
JP
