Re: Assigning IPv6 DNS servers to clients via DHCPv6?

Changed to dhcpv6-stateless. Here's radvd.conf:

# cat /etc/radvd.conf
interface eth0.102 {
#   This section was automatically generated by the Vyatta
#   configuration sub-system.  Do not edit it.
#
#   service type [dhcpv6-stateless]
#
    IgnoreIfMissing on;
    AdvSendAdvert on;
    AdvManagedFlag off;
    AdvOtherConfigFlag on;
    prefix ::/64 {
          AdvOnLink on;
          AdvAutonomous on;
    };
};
interface eth2 {
#   This section was automatically generated by the Vyatta
#   configuration sub-system.  Do not edit it.
#
#   service type [dhcpv6-stateless]
#
    IgnoreIfMissing on;
    AdvSendAdvert on;
    AdvManagedFlag off;
    AdvOtherConfigFlag on;
    prefix ::/64 {
          AdvOnLink on;
          AdvAutonomous on;
    };
};

Ther was no IPv6 on the client, tho... which confused me.

It didn't over-write the DHCPv6 pool:

# cat /opt/vyatta/etc/dhcpdv6.conf
# This file is auto-generated by the Vyatta configuration sub-system.
# Do not edit it by hand.
# Auto-generated by: root
# Auto-generated on: Fri Aug 19 19:00:10 MDT 2016
#
shared-network IPv6pool {
    option dhcp6.name-servers 2001:4860:4860::8888, 2001:4860:4860::8844;
    subnet6 fe80::xxxx:xxxx:xxxx:9459/128 {
    }
}

I couldn't see why IPv6 routing shouldn't work... so I rebooted the router.... and the OSX client got an IPv6 address! Still scored "18" on http://ipv6-test.com/, but SLAAC was now green and marked as "NO."

Tested on all client platforms. IPv6 DNS servers still don't show up on the clients TCP/IP properties interfaces, though IPv6 name resolution is working fine on OSX, Linux, and Windows clients, though probably though IPv4 DNS.

So far, this config is the best. But I'll experiment with dnsmasq next!