Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Carlos E. R." Newsgroups: comp.os.linux.misc,comp.os.linux.x Subject: Re: tint2 keeps crashing Date: Wed, 15 Nov 2023 12:43:59 +0100 Lines: 56 Message-ID: References: <87v8a515hg.fsf@usenet.ankman.de> <877cmj250h.fsf@usenet.ankman.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net 7OuhxGserjPytoZacNhAjwBdOhW0pIuSFfMHBwHSCM5YpPGQdg Cancel-Lock: sha1:hb1RvNUomb8GX5vkzA8k0TSaGbo= sha256:lB3FqYyXI6li0hDvEYOTaOULbW12XW59KI8ITTNLwGk= User-Agent: Mozilla Thunderbird Content-Language: en-CA, es-ANY In-Reply-To: Xref: csiph.com comp.os.linux.misc:43894 comp.os.linux.x:327 On 2023-11-15 12:30, The Natural Philosopher wrote: > On 15/11/2023 01:13, Andreas Kohlbach wrote: > >> Nice! >> >> I didn't even cared to check his email address for validity. >> >> ~$ host lenovo.lan >> Host lenovo.lan not found: 3(NXDOMAIN) >> >> What a c**t! (Yeah, that's a flame) > > Well, amazingly idiotic, for sure. https://www.rfc-editor.org/rfc/rfc6762#appendix-G Appendix G. Private DNS Namespaces The special treatment of names ending in ".local." has been implemented in Macintosh computers since the days of Mac OS 9, and continues today in Mac OS X and iOS. There are also implementations for Microsoft Windows [B4W], Linux, and other platforms. Some network operators setting up private internal networks ("intranets") have used unregistered top-level domains, and some may have used the ".local" top-level domain. Using ".local" as a private top-level domain conflicts with Multicast DNS and may cause problems for users. Clients can be configured to send both Multicast and Unicast DNS queries in parallel for these names, and this does allow names to be looked up both ways, but this results in additional network traffic and additional delays in name resolution, as well as potentially creating user confusion when it is not clear whether any given result was received via link-local multicast from a peer on the same link, or from the configured unicast name server. Because of this, we recommend against using ".local" as a private Unicast DNS top-level domain. We do not recommend use of unregistered top-level domains at all, but should network operators decide to do this, the following top-level domains have been used on private internal networks without the problems caused by trying to reuse ".local." for this purpose: .intranet. .internal. .private. .corp. .home. .lan. :-) -- Cheers, Carlos E.R.