4 ms·
I have recently come to the conclusion that a major problem is that there is no "local" internet. You either have websites somewhere out of local network or som
by LeanderK 3y ago
I have recently come to the conclusion that a major problem is that there is no "local" internet. You either have websites somewhere out of local network or some app-based solution, but there's no "dishwasher.local". And you can't burden consumers with IP addresses.
- candiddevmike 3y agohttps://en.wikipedia.org/wiki/Multicast_DNS https://en.wikipedia.org/wiki/Multicast_DNS should work fine here
- LeanderK 3y agoah I never knew that the protocols behind the zeroconf services (Bonjour etc.) can also resolve hostnames. Very interesting. Although I have to say that in my experience these things are not robust enough yet. Setting up the printer at work was a pain because it was not automatically found (okay, this is a complex network) and at home I have a few devices that should talk with each other (some running behind switches) but only if I start them in the right order. I wonder why there's no way to let the router handle the DNS with some sort of registering/de-registering functionality? I would think this to be more robust compared to the broadcasting.
- oefrha 3y agoThere is “local” Internet, it’s called LAN. There’s “dishwater.local” if someone (manufacturer included, though I’m pretty firmly against IoS devices) bothers to set it up. Local nodes can do multicast/broadcast DNS and discover each other. You’ve probably seen it if you ever used a WiFi-connected printer on LAN.