Hacker News new | past | comments | ask | show | jobs | submit login

all of the DHCP options, for example.

SLAAC just tells the endpoint device to self-assign an address and to roll with it. For example, there’s no way to pass in DNS servers with SLAAC.




The DNS bit it's not true: there's RFC8106 [1] for this and it's widely supported. You can set a list of DNS servers to use (RDNSS) and a domain suffix for resolving unqualified hostnames (DNSSL), exactly as for DHCP.

[1]: https://datatracker.ietf.org/doc/html/rfc8106


Can't you provide DNS servers as part of router advertisement packets ? RFC8106


I stand corrected, but I haven't seen this in practice yet.


This requires client support though, which isn't a given.


I expect basically anything that supports SLAAC would have supported DNS advertisements for at least a few years…


That is most operating systems and devices these days.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: