ScratchMonkey
Occasional Visitor
Router: RT-AC66U
Firmware: 380.58_0
IPv6 Connection Type: Native
DHCP-PD: Enable
Issue 1: If I just edit the IPv6 DNS server 1 setting and save, the router forgets its IPv6 lease, and only remembers the new DNS setting. I have to reboot the router to both preserve the lease and change the DNS server setting.
Issue 2: I'd like the DNS server setting to be able to use a macro representing the prefix, so I can (for example) request a DNS server of "%PREFIX%::128" representing the static address of an internal Linux server. Does anything like that exist?
I have an internal CentOS 5 server serving DNS using BIND. I want to set it as IPv6 DNS Server 1 in the IPv6 page.
I'm currently configuring the CentOS server with a static IPv6 address using the prefix from the router's IPv6 page. This allows my Windows clients to use the internal server to locate LAN services on the box (served by IPv4). (I have to figure out how to configure it to use the advertised prefix instead of having it hard-coded in ifcfg-eth0. But that's a CentOS 5 issue. And I'm hoping to replace it soon with a CentOS 7 box.)
Firmware: 380.58_0
IPv6 Connection Type: Native
DHCP-PD: Enable
Issue 1: If I just edit the IPv6 DNS server 1 setting and save, the router forgets its IPv6 lease, and only remembers the new DNS setting. I have to reboot the router to both preserve the lease and change the DNS server setting.
Issue 2: I'd like the DNS server setting to be able to use a macro representing the prefix, so I can (for example) request a DNS server of "%PREFIX%::128" representing the static address of an internal Linux server. Does anything like that exist?
I have an internal CentOS 5 server serving DNS using BIND. I want to set it as IPv6 DNS Server 1 in the IPv6 page.
I'm currently configuring the CentOS server with a static IPv6 address using the prefix from the router's IPv6 page. This allows my Windows clients to use the internal server to locate LAN services on the box (served by IPv4). (I have to figure out how to configure it to use the advertised prefix instead of having it hard-coded in ifcfg-eth0. But that's a CentOS 5 issue. And I'm hoping to replace it soon with a CentOS 7 box.)
