| ▲ | axus 4 hours ago |
| I've started using .internal |
|
| ▲ | whartung 4 hours ago | parent | next [-] |
| 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 |
| |
| ▲ | mawise 2 hours ago | parent [-] | | 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 |
|
|
| ▲ | mkl 4 hours ago | parent | prev [-] |
| That's no use for self-hosting unless all your users are on your private network. |
| |
| ▲ | warpech 4 hours ago | parent [-] | | 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 | | |
|
