5 ms·

Hostname discovery (mdns), etc solves it on local networks. If DNS is down or broken, it would be difficult for me to "use the internet", and I'd have to copy

Hostname discovery (mdns), etc solves it on local networks. If DNS is down or broken, it would be difficult for me to "use the internet", and I'd have to copy and paste a lot anyways.

api 11y ago
mDNS is slow and unreliable and on large networks it doesn't scale. I personally don't find it very useful since half the time it barely works even on wired LANs let alone big WiFi or distributed networks. It's also prone to naming conflicts (is this linux-1, linux-2, or linux-3?) and other OS configuration issues and is not secure.
- jauer 11y ago
  On a network like that, wouldn't DDNS solve the problem? I mean DDNS where the DHCP server tells the DNS server which IP has what hostname, not e.g. dyndns.
  - emmelaich 11y ago
    I don't think people trust DDNS enough in corporate networks and any security sensitive network.
akira2501 11y ago
So, run yet another service with a poorly thought out RFC and add another code base to my vulnerability monitoring?
- tekklloneer 11y ago
  At home/small business scale, yes. At enterprise scale, you shouldn't be relying on IP addresses for clients for anything important.