Bug ID 602300: Zone Runner entries cannot be modified when sys DNS starts with IPv6 address

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP GTM(all modules)

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,

Fixed In:

Opened: Jun 30, 2016
Severity: 3-Major


Zone Runner entries cannot be modified if an IPv6 DNS name server is listed first. This can happen when a user runs the tmsh command tmsh modify sys dns name-servers add { <IPv6> } as the first dns name-server. This will show in the /etc/resolv.conf file (an example) nameserver 2001::1 nameserver


ZoneRunner records cannot be modified.


When an IPv6 nameserver is the first server defined.


Do not use DNS server with IPv6 address or add IPv4 server at top of the list.

Fix Information

The IP address type was not set properly while communicating with BIND. This does not matter if the first nameserver listed is an IPv4 address or if there are no nameservers listed at all. If the first nameserver listed is an IPv6 and the IP address type is not set to IPv4 (AF_INET), BIND libraries will attempt to use the IPv6 library from /etc/resolv.conf. We not properly set the AF_INET type to IPv4.

Behavior Change