Bug ID 920817: Wide IP operations performed in quick succession result in missing resource records and out of sync journals.

Last Modified: Jan 20, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP DNS, GTM, TMOS(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.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3

Opened: Jun 24, 2020
Severity: 3-Major

Symptoms

Two issues occur with Wide IP operations performed in quick succession: 1. DNS Zone syncing is missing resource records. 2. In some cases it throws named/zrd error: journal rollforward failed: journal out of sync with zone.

Impact

DNS resource records can be missing from the BIND DNS database. The impact of this issue is that if GSLB Load Balancing falls back to BIND, the DNS resource records may not be present. Manually remove the .jnl files in order to restore named/zrd on all GTMs.

Conditions

This issue can occur when a large number of configuration changes, including Wide IP changes, are made simultaneously on multiple GTM/DNS devices in a sync group.

Workaround

Restrict configuration (Wide IP) changes to one GTM/DNS device in a device group. Note: It is also possible to turn off zone syncing. GTM/DNS configuration is still synced, but you lose the ability to sync non-Wide IP changes to the BIND DB. If you do not use ZoneRunner to add additional non-Wide IP records, this is only a problem when GSLB resorts fallback to BIND. This can be mitigated with DNSX and DNS (off device) for non Wide IP Resource Records. Manually remove the .jnl files in order to restore named/zrd on all GTMs.

Fix Information

None

Behavior Change