Bug ID 429127: GTM zone modifications do not sync to members of a GTM sync group

Last Modified: Jul 12, 2023

Affected Product(s):
BIG-IP GTM(all modules)

Known Affected Versions:
11.1.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1

Fixed In:
11.5.0, 11.4.1 HF1, 11.4.0 HF4, 11.3.0 HF8, 11.2.1 HF10

Opened: Aug 28, 2013

Severity: 3-Major

Related Article: K14767


When changes to an existing zone are made via ZoneRunner, the changes are made effective on the local device, but are not loaded into the BIND daemons on the peer GTM group members.


Changes made to an existing zone are not synced to other members of the GTM sync group.


GTM used in a sync group with zone 'Synchronize DNS Zone Files' enabled.


Issue the following command on peer sync group members in order to see zone updates: bigstart restart named Note: This issue might result in zrd process exits, which you can find described in K10066: The zrd process exits upon the 'journal rollforward failed: journal out of sync with zone' error message :: https://support.f5.com/csp/article/K10066.

Fix Information

Changes in the DNS Zone Files are now properly synchronized between peer GTM group members.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips