Last Modified: Aug 26, 2020
See more info
BIG-IP DNS, GTM
Known Affected Versions:
14.1.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 14.1.2, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 15.1.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52
Opened: Aug 13, 2020
Bind does not match IPv6 addresses configured for a zone view, and returns REFUSED responses, rather than the expected answers. After enabling debug logging in bind (see K14680), the apparent source address of the IPv6 DNS requests shows as being in the fe80::/96 range, rather than the IPv6 source address that sent the request. For example: debug 1: client @0x579bf188 fe80::201:23ff:fe45:6701%10#4299: no matching view in class 'IN'
You cannot use DNS views in bind (zonerunner) based on IPv6 addresses.
- BIG-IP DNS is provsioned - One or more ZoneRunner views is defined using IPv6 addresses. - A DNS query is sent from an IPv6 source address
If possible, use only IPv4 addresses to define views for DNS queries