Use SLAAC. It just works.
[0] <https://datatracker.ietf.org/doc/html/rfc4861#section-4.6.2>
[1] <https://datatracker.ietf.org/doc/html/rfc4861#section-4.2>
Odd.
option dhcp6.name-servers <ADDR>;
option dhcp6.sntp-servers <ADDR>;
work to get my Linux systems an IPv6 DNS and NTP server (respectively) when I'm using ISC DHCPd and 'dhcpcd'. Perhaps your DHCPd and/or your DHCPc were either misconfigured or badly broken?It is a little weird to be using the 'sntp' option, but on the systems I have access to, the address passed back to the client is treated exactly the same as the DHCPv4 NTP information. ~Thirteen years ago, one of the ISC DHCP bigwigs seemed to be of the opinion that the DHCPv6 NTP Server Option was "badly broken" [0]. Perhaps that's why the 'sntp' option is used instead.
[0] <https://lists.isc.org/pipermail/dhcp-users/2013-June/016882....>
interface enp2s0f1 {
AdvSendAdvert on;
AdvManagedFlag off;
AdvOtherConfigFlag off;
IgnoreIfMissing on;
prefix ::/64 {
AdvOnLink on;
AdvAutonomous on;
};
RDNSS fddd:deca:fbad:1::10 {
AdvRDNSSLifetime infinity;
};
DNSSL internal.domain {
AdvDNSSLLifetime infinity;
};
};
I haven't yet found a way to specify a local NTP server though, which is a drag. So everything not manually configured (like the voip phone) talks to the local NTP over ipv4.Mine is all static. I run a bind9 forwarder for DNS, and KEA for dhcp4. I have a little list of machines/macs/addresses as the source of truth, and a pair of python scripts that generates kea-dhcp4.conf and a bind9 zone file from that table.
When I enabled IPv6, I just put all the SLACC addresses in that table, and made the python script generate AAAA records too. But this is honestly really stupid, I need to actually use mdns...
I thought about writing a little systemd oneshot that used rfc2136 dyndns updates for home. But it feels like reinventing the wheel a bit...
> When I enabled IPv6, I just put all the SLACC addresses in that table, and made the python script generate AAAA records too.
Er, isn't that just manual static assignment, then? Not SLAAC? Don't get me wrong, static addresses do make DNS easy...
Haha no, much dumber than that: I boot the machine, get the permanent SLAAC address it comes up with, put that in the static table, and re-run the script to generate the zone files. The downside is the address changes if you reinstall the OS, but I do that so rarely it honestly hasn't been a problem (and you can force the older MAC-based address generation if you want it to be stable). I wouldn't recommend this setup though...
I do also have some static addresses, like that DNS server address.
P.S. thanks for the funniest HN comment I've read in a while