.local TLD Conflicts

Cluster debates the use of .local top-level domain for private/local hostnames and networks, warning of conflicts with mDNS/Bonjour/Zeroconf which reserves it per RFC 6762, and suggesting alternatives like .localhost or .localdomain.

➡️ Stable 0.8x DevOps & Infrastructure
2,682
Comments
19
Years Active
5
Top Authors
#3056
Topic ID

Activity Over Time

2008
3
2009
17
2010
42
2011
46
2012
72
2013
62
2014
121
2015
133
2016
192
2017
195
2018
187
2019
213
2020
234
2021
212
2022
186
2023
172
2024
327
2025
242
2026
28

Keywords

US WebSo SRV SSH DNS snap.com NSS en.m ourdomainname.com spa.snap 127 local dns tld localhost reserved domains resolve addresses com

Sample Comments

chrisweekly May 8, 2019 View on HN

I use "foo.local" as a drop-in replacement, haven't had problems...

Pxtl Sep 28, 2016 View on HN

I thought .local was a de-facto standard for this?

LoSboccacc Sep 28, 2016 View on HN

isn't that the role of .localdomain tho?

LeoPanthera Aug 10, 2024 View on HN

Using .local causes big problems with mDNS/Bonjour/Rendezvous, which also uses that TLD.

jt2190 Jun 28, 2020 View on HN

There’s always the .local TLD, which is reserved for this use case:https://en.m.wikipedia.org/wiki/.local

nitrogen Jun 28, 2020 View on HN

Why not just use mDNS too and stick with .local?

ivlad Jan 6, 2019 View on HN

Using .local in DNS is a violation of RFC6762. You really ought not to do this.

theteapot Aug 16, 2021 View on HN

What's wrong with .localdomain? Or is that for something else??

rcarmo Jul 21, 2024 View on HN

Won't this break Bonjour/Zeroconf .local announcements from hosts? Should you be using .local at all?

fanf2 Jul 5, 2019 View on HN

.local is reserved for multicast DNS so it is a really bad idea to use it for private DNS