Bug ID 743987: DNSX can no longer receive DNS NOTIFY messages on self ips

Last Modified: Sep 06, 2019

Bug Tracker

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 14.1.2

Opened: Sep 13, 2018
Severity: 4-Minor

Symptoms

DNSX can no longer receive DNS NOTIFY messages on self ips.

Impact

DNSX acting as slave/secondary can no longer receive or process DNS NOTIFY messages via self ips.

Conditions

User has configured DNSX as a DNS slave/secondary server that listens for DNS NOTIFY messages from a master DNS server.

Workaround

If your infrastructure relies on DNS NOTIFY messages being sent to DNSX slave/seconadry servers via self ips, you will need to modify the configuration on their Master DNS server(s) and also on the BIG-IP with DNSX acting as a slave secondary. The Master needs to be configured to send DNS NOTIFY messages to either to a BIG-IP Virtual (UDP & TCP) with DNSX enabled on the associated DNS profile or configured to send to the management ip of the BIG-IP, or both. Note if using the management ip to recieve DNS NOTIFY for DNSX, you must enable this behavior by setting the dnsexpress.notifyport db variable to a port number besides zero.

Fix Information

None

Behavior Change