Bug ID 737726: If named is restarted and zrd is not restarted, ZoneRunner can lose contact with the DNS server daemon

Last Modified: Jan 29, 2019

Bug Tracker

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4

Fixed In:
14.1.0

Opened: Jul 20, 2018
Severity: 2-Critical

Symptoms

ZoneRunner displays the following error message when attempting to list resource records: No route to host.

Impact

ZoneRunner cannot communicate with named, and thus cannot display resource records. There are temporary addresses created on the loopback address to facilitate communication between the zrd and named processes. When named is restarted, these temporary address are inadvertently removed.

Conditions

-- named is restarted outside of the normal start up procedure. -- zrd is not restarted.

Workaround

Restart the zrd process using the following command: bigstart restart zrd

Fix Information

The system no longer removes loopback addresses when named is restarted, so this issue no longer occurs.

Behavior Change