8 ms·

I didn't see a specific RFC that reserved .lan however from the proposed standard RFC 8375 home.arpa is suggested. https://datatracker.ietf.org/doc/html/rfc837

• n4bz0r 1y ago
  > home.arpa is suggested Thanks, didn't even know it existed. > I didn't see a specific RFC that reserved .lan There is no RFC AFAIK, but it has certainly seen some adoption over the past decade. Mikrotik devices use `router.lan` as a default domain name for their routers, for instance. Home labbers on YouTube seem to like to use `.lan`, too. Would it be fair to think there is a chance `.lan` might get an RFC of its' own given the popularity? Or that's completely irrelevant in case with RFCs? Hard to tell what's the reasoning there - `.home.arpa` seems excessivly long and inconvenient. Would be a real shame and a bummer if `.lan` ends up becoming public :')
  • ZeroSolstice 1y ago
    I agree it would be great to get some of the vendor pushed / common domains put into an accepted standard. In my interaction with IETF standards they are created / implemented in two ways: 1. They set the forward direction for a new technology before it is wide spread. 2. They wait for a technology to become popular / accepted and start to set standards from that baseline. Both are reasonable paths of implementation given how the pace of changes in technology. I doubt .lan, .local, .home, etc will either become public or a standard just based on existing devices that default to these domains and documentation or books that might reference them as example domains.
    • aragilar 1y ago
      .local is defined for mDNS
      • ZeroSolstice 1y ago
        Correct, which is why .local wouldn't become a TLD or part of a standard for home network reserved domains.