On Sat 03 Aug 2024 at 11:26:38 (+0200), to...@tuxteam.de wrote: > On Sat, Aug 03, 2024 at 06:56:42PM +1000, George at Clug wrote: > > What is the purpose of mDNS ? > > > > It seems to be for multicast? > > It is not /for/ multicast IP, it /uses/ multicast for name resolution. > In a nutshell [1], it sends a "DNS" request to the local network asking > "who is called Fritz here?", and Fritz answers with its IP. So sys-non- > admins don't have to set up a name server. > > It is part of Microsoft's promise that anyone can be sysadmin because > no one is. And then you end up in The Cloud(TM), which doesn't work either.
Isn't that what modern networking is striving to attain? “It is not practical to expect home users to configure their networks. Thus, the assumption of this document is that the homenet is as far as possible self-organising and self-configuring, i.e., it should function without proactive management by the residential user.” (RFC 7368) “Users and devices within a home network (hereafter referred to as "homenet") require devices and services to be identified by names that are unique within the boundaries of the homenet [RFC7368]. The naming mechanism needs to function without configuration from the user. While it may be possible for a name to be delegated by an ISP, homenets must also function in the absence of such a delegation. This document reserves the name 'home.arpa.' to serve as the default name for this purpose, with a scope limited to each individual homenet.” (RFC 8375) Cheers, David.
