logoalt Hacker News

yjftsjthsd-h • today at 3:32 AM • 2 replies • view on HN

> addressing hosts via IPv6 is the wrong way to go about it. On your lan, you really want to be doing ".local" / ".lan" / ".home".

.local is fine as long as all the daemons work correctly, but AFAIK there's no way to have SLAAC and put hosts in "normal" internal DNS, so .lan/.home/.internal are probably out.

Replies

alwillis • today at 3:54 AM

> On your lan, you really want to be doing ".local" / ".lan" / ".home".

The "official" is home.arpa according to RFC 8375 [1]:

    Users and devices within a home network (hereafter referred to as
    "homenet") require devices and services to be identified by names
    that are unique within the boundaries of the homenet [RFC7368].  The
    naming mechanism needs to function without configuration from the
    user.  While it may be possible for a name to be delegated by an ISP,
    homenets must also function in the absence of such a delegation.
    This document reserves the name 'home.arpa.' to serve as the default
    name for this purpose, with a scope limited to each individual
    homenet.
[1]: https://datatracker.ietf.org/doc/html/rfc8375
➕ show 2 replies
somat • today at 4:18 AM

I do it by abusing the static slaac address. I have a set of wierd vms where they are cloned from a reference image, so no fixed config allowed. I should have probably just have used dhcp6 but I started by trying slaac and the static address were stable enough for my purposes so it stuck.

➕ show 1 reply