16
18.7 Legacy Series / Re: WAN Interface not obtaining IPv6 prefix.
« on: January 17, 2019, 09:22:15 pm »
I tried siwtching it between none and track. It worked at the time.
Also didn't know that THAT is what the prefix ID is for, and why when I changed it I got a different prefix that still started with 2601. The last 4 of the prefix were different, which means comcast is probably giving me at least a /48 prefix, right?
And yes, 2601 was the LAN ip, which seems to be correct in that that's whats being dished out by the ISP, and I can access the router using both its LAN ip (2601) and WAN IP (2001)
And if SLAAC can't do DNS at all, what would the best method be for syncing them to DNS records? Currently my v4 network tracks all DHCP clients (including static leases) as {hostname}.lan.example.com, and I want all ipv6 clients to be mapped in {hostname}.lan6.example.com. (I use unbound DNS for this). When I used DHCPv6, my servers weren't grabbing an IP address at all (seemed like dhclient wasn't running on the servers, all ubuntu 18.04).
Also didn't know that THAT is what the prefix ID is for, and why when I changed it I got a different prefix that still started with 2601. The last 4 of the prefix were different, which means comcast is probably giving me at least a /48 prefix, right?
And yes, 2601 was the LAN ip, which seems to be correct in that that's whats being dished out by the ISP, and I can access the router using both its LAN ip (2601) and WAN IP (2001)
And if SLAAC can't do DNS at all, what would the best method be for syncing them to DNS records? Currently my v4 network tracks all DHCP clients (including static leases) as {hostname}.lan.example.com, and I want all ipv6 clients to be mapped in {hostname}.lan6.example.com. (I use unbound DNS for this). When I used DHCPv6, my servers weren't grabbing an IP address at all (seemed like dhclient wasn't running on the servers, all ubuntu 18.04).