Hacker News Reader

Comment by greggsy | Hacker News Reader

I’m holding out for a draft RFC to deprecate .local for mDNS, and allow it to be used for local domains. It’s practically infeasible, but one can wish.

View on HN

That will never happen, but RFC 6762 suggests some other options for private networks: .intranet, .internal, .private, .corp, .lan.

https://datatracker.ietf.org/doc/html/rfc6762#appendix-G

ICANN seems to be in the process of finalizing a proposal to officially reserve .internal for this purpose.

https://www.icann.org/en/announcements/details/icann-seeks-f...

Just use mDNS then. But as others have said, there are other options that are almost as good.

Same here. We set up our company's intranet using a `.local` address long before mDNS was a thing. Needless to say it causes a lot of pain on a daily basis.

On almost every linux installation we have to tweak `/etc/nsswitch.com` for it to work.

I doubt it'll ever happen but hey, one can wish :)

Your company is over twenty years old? Well done.

didn't realize that was something to point out ...

Given the fact that Kubernetes uses cluster.local. by default (and probably in the 99% of clusters), you can be sure that any useful software will be OK with that.

Kubernetes is normally used on hosted servers and mDNS is normally used for home appliances like printers. I wouldn’t expect Kubernetes to be able to show that using .local is safe with mDNS.

Kebernetes ought to change that default, as it's contrary to the standard.

e.g. systemd by default won't query DNS for a .local domain, and it's sometimes useful to connect to K8s resources from outside the cluster.

Reply on news.ycombinator.com