Bug #7384

DHCPv6 doesn't merge IPv6 prefix with the input submitted in DNS servers field when using Track Interface IPv6 configuration parameter for the LAN interface.

Added by Hannu Tirkkonen about 4 years ago. Updated 6 months ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
Affected Architecture:
Release Notes:


When using Track Interface as a IPv6 Configuration Type in the LAN interface, the DHCPv6 server doesn't merge the IA_PD-prefix obtained via the DHCP6 client (WAN interface) and the DNS Servers input (i.e. ::a and ::b) in the DHCPv6 configuration page.

If user fills ::a and ::b as DNS servers in the DNS Servers field, the configuration file will be written without the prefix obtained via Track Interface
(::a and ::b instead of expected results 2001:14ab:11f1:9200::a and 2001:14ab:11f1:9200::b in case 2001:14ab:11f1:9200::/56 being delegated and Track Interface with WAN/0 used as IPv6 configuration parameters for the LAN interface).

The merge works ok with the DHCPv6 Range and static mappings fields and provides ability to assign semi static IPv6 addresses for the internal DNS servers, but it doesn't work in the DNS Servers field and as such manual reconfiguration is required each time the ISP delegates a new IPv6 network.


subnet6 2001:14ab:11f1:9200::/64 {
range6 2001:14ab:11f1:9200::fe90:0 2001:14ab:11f1:9200::fe90:ffff;
do-forward-updates false;
option ::a,::b;

host s_lan_0 {
host-identifier option dhcp6.client-id 00:01:00:01:1b:de:af:2b:20:c9:d0:54:c6:d3;
fixed-address6 2001:14ab:11f1:9200::a;
option host-name DNS1;

This is problematic when the ISP doesn't obey the request for delegating previously assigned network for the customer and causes the DNS name resolution to fail after the new IPv6 network will be delegated for the customer.

Associated revisions

Revision 7339f154 (diff)
Added by Viktor Gurov 7 months ago

DHCPv6 merge IPv6 prefix for DNS servers. Fixes #7384


#1 Updated by Jim Pingle almost 4 years ago

  • Target version changed from 2.3.4 to 2.4.1

#2 Updated by Jim Pingle over 3 years ago

  • Target version changed from 2.4.1 to 2.4.2

#3 Updated by Jim Pingle over 3 years ago

  • Target version changed from 2.4.2 to 2.4.3

#4 Updated by Steve Beaver about 3 years ago

  • Assignee set to Luiz Souza
  • Priority changed from High to Normal
  • Target version changed from 2.4.3 to 2.4.4

#5 Updated by Steve Beaver over 2 years ago

  • Target version changed from 2.4.4 to 48

#6 Updated by Chris Collins over 2 years ago

this has been pushed back a lot, it would be nice if it got implemented, as a work around I have been using fe80::1:1 as a DNS server configured in DHCPv6, allowing the configuration to remain valid if the IA_PD changes.

#7 Updated by Jim Pingle about 2 years ago

  • Target version changed from 48 to 2.5.0

#8 Updated by Jim Pingle over 1 year ago

  • Category changed from DHCP (IPv4) to DHCP (IPv6)

#10 Updated by Jim Pingle 7 months ago

  • Status changed from New to Pull Request Review

#11 Updated by Renato Botelho 7 months ago

  • Status changed from Pull Request Review to Feedback
  • % Done changed from 0 to 100

PR has been merged. Thanks!

#12 Updated by Steve Beaver 6 months ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF