3 ms·
What? No. You connect a device, and SLAAC (and optionally DHCPv6, on enterprise networks) configures everything. It just works. SLAAC is more than capable of s
by tjohns 4y ago
What? No. You connect a device, and SLAAC (and optionally DHCPv6, on enterprise networks) configures everything. It just works.
SLAAC is more than capable of sending DNS settings to devices. There's no manual configuration involved.
- tjoff 4y agoMy post said to use DHCPv6 and RDNSS. Follow up claimed to use SLAAC instead. SLAAC does not do DNS. Clear as day?
- tjohns 4y agoSLAAC does DNS, with the RDNSS extension enabled. (RDNSS is a feature that was added to SLAAC.) Some older devices [1] do not support RDNSS. I haven't run into them, but if you're at all worried about it, you can run DHCPv6 in parallel just to hand out DNS settings. Personally, I just use SLAAC (with RDNSS) and it just works. [1]: https://en.wikipedia.org/wiki/Comparison_of_IPv6_support_in_operating_systems https://en.wikipedia.org/wiki/Comparison_of_IPv6_support_in_...
- ipython 4y agoI run dual stack at home and every device I have connected to my home network runs ipv6 with no manual configuration whatsoever. It’s easier than ipv4 when you consider providing inbound access to resources (no nat configuration)