4 ms·

Having trouble not attributing to malice that which is adequately explained by stupidity here... For Home Assistant for instance, the only reasonable option is

by racked 2y ago

Having trouble not attributing to malice that which is adequately explained by stupidity here... For Home Assistant for instance, the only reasonable option is .internal - its default .local is not the right TLD to use. [1] [1]: https://serverfault.com/a/937808 https://serverfault.com/a/937808

bmacho 2y ago
Hanlon's razor is malicious. Assuming malice is the trivial right choice. Assuming stupidity just bc it rhymes, or bc you can feel smart about yourself is stupid.
- deleted 2y ago
  [deleted]
deleted 2y ago
[deleted]
wkat4242 2y ago
Isn't .local specific to 'rendezvous' tech anyway? I forget the generic name but it was Apple that put it on the map under this name. But I mean that serverless broadcast protocol. What I do is I just bought a domain and use that together with DNS-based SSL. It's a bit hard to set up with every different SSL server but it's doable.
- aspenmayer 2y ago
  There’s mDNS, zeroconf, and Bonjour. https://en.wikipedia.org/wiki/.local https://en.wikipedia.org/wiki/.local
- lathiat 2y ago
  Rendezvous = Bonjour = Multicast DNS Service Discovery
- ethersteeds 2y ago
  The non Apple name is multicast DNS or mDNS. mDNS is exclusive to .local, but not necessarily the other way around. From its Wikipedia entry: "By default, mDNS exclusively resolves hostnames ending with the .local top-level domain. This can cause problems if .local includes hosts that do not implement mDNS but that can be found via a conventional unicast DNS server. Resolving such conflicts requires network-configuration changes that mDNS was designed to avoid."
  - aragilar 2y ago
    Per https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml https://www.iana.org/assignments/special-use-domain-names/sp... and https://www.rfc-editor.org/rfc/rfc6761.html https://www.rfc-editor.org/rfc/rfc6761.html .local. is only for mDNS, but as with any other name you can always misuse it (see .corp. .dev. etc.). I notice .alt. now exists.
notpushkin 2y ago
> its default .local is not the right TLD to use What if you advertise it on mDNS?

by racked 2y ago

bmacho 2y ago

Hanlon's razor is malicious. Assuming malice is the trivial right choice. Assuming stupidity just bc it rhymes, or bc you can feel smart about yourself is stupid.

deleted 2y ago
[deleted]

deleted 2y ago

[deleted]

wkat4242 2y ago

Isn't .local specific to 'rendezvous' tech anyway? I forget the generic name but it was Apple that put it on the map under this name. But I mean that serverless broadcast protocol. What I do is I just bought a domain and use that together with DNS-based SSL. It's a bit hard to set up with every different SSL server but it's doable.

aspenmayer 2y ago
There’s mDNS, zeroconf, and Bonjour. https://en.wikipedia.org/wiki/.local https://en.wikipedia.org/wiki/.local
lathiat 2y ago
Rendezvous = Bonjour = Multicast DNS Service Discovery
ethersteeds 2y ago
The non Apple name is multicast DNS or mDNS. mDNS is exclusive to .local, but not necessarily the other way around. From its Wikipedia entry: "By default, mDNS exclusively resolves hostnames ending with the .local top-level domain. This can cause problems if .local includes hosts that do not implement mDNS but that can be found via a conventional unicast DNS server. Resolving such conflicts requires network-configuration changes that mDNS was designed to avoid."
- aragilar 2y ago
  Per https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml https://www.iana.org/assignments/special-use-domain-names/sp... and https://www.rfc-editor.org/rfc/rfc6761.html https://www.rfc-editor.org/rfc/rfc6761.html .local. is only for mDNS, but as with any other name you can always misuse it (see .corp. .dev. etc.). I notice .alt. now exists.

notpushkin 2y ago

> its default .local is not the right TLD to use What if you advertise it on mDNS?