3 ms·

I've started using .internal

• mkl 4mo ago
  That's no use for self-hosting unless all your users are on your private network.
  • warpech 4mo ago
    Tailnet and Magic DNS make it easy to bring other people or devices to your network, including simple authentication mechanisms to know who is who
    • Diti 4mo ago
      A VPN is literally a… (Very) Private Network.
      • furyofantares 4mo ago
        Virtual, not Very
        • Diti 4mo ago
          Woops! This is what sleep deprivation does. Thanks!
    • mkl 4mo ago
      That doesn't contradict anything I said. Private networks can be huge, e.g. in big companies, and they can still use .internal. .internal serves quite a different purpose to that proposed for .self, so the top level comment I replied to doesn't make much sense.
• whartung 4mo ago
  As I understand it, if you want to use domains internally for your home ("home") network, there's some DNS support for "home.arpa"[0]. 0 - https://www.rfc-editor.org/rfc/rfc8375.html https://www.rfc-editor.org/rfc/rfc8375.html
  • mawise 4mo ago
    I've been using .lan, referenced in rfc6762[1] as a good alternative to the multicast .local > We do not recommend use of unregistered top-level domains at all, but should network operators decide to do this, the following top-level domains have been used on private internal networks without the problems caused by trying to reuse ".local." for this purpose: .intranet. .internal. .private. .corp. .home. .lan. [1]: https://datatracker.ietf.org/doc/html/rfc6762 https://datatracker.ietf.org/doc/html/rfc6762