# ZoneRunner – Zero-downtime migration of records from zone to zone

**URL:** <https://community.f5.com/t/zonerunner-zero-downtime-migration-of-records-from-zone-to-zone/77328>\
**Category:** Technical Forums\
**Tags:** gslb, dns, zone-runner\
**Created:** [August 12, 2026, 8:12am UTC](https://community.f5.com/t/zonerunner-zero-downtime-migration-of-records-from-zone-to-zone/77328 "2026-08-12T08:12:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pak](https://avatars.discourse-cdn.com/v4/letter/p/4bbf92/32.png) [@Pak](https://community.f5.com/u/Pak)\
**Post date:** [August 12, 2026, 8:12am UTC](https://community.f5.com/t/zonerunner-zero-downtime-migration-of-records-from-zone-to-zone/77328/1 "2026-08-12T08:12:14Z")

</div>

We are running BIG-IP DNS version 17.5.1.5 and use ZoneRunner for authoritative DNS.

Current state:

We have a master zone [my.com](http://my.com) on BIG-IP.

In this zone there are multiple records for services under [f5.my.com](http://f5.my.com), e.g. [r1.f5.my.com](http://r1.f5.my.com), [s1.f5.my.com](http://s1.f5.my.com), etc.

These are used for WideIP (A/AAAA) and RR responses.

We want to introduce a separate authoritative zone [f5.my.com](http://f5.my.com) (with proper SOA/NS), and then delegate [f5.my.com](http://f5.my.com) from [my.com](http://my.com).

Issue/concern:

As soon as we create the empty zone [f5.my.com](http://f5.my.com) on the same BIG-IP, queries for names like [r1.f5.my.com](http://r1.f5.my.com) stop being answered from the parent zone [my.com](http://my.com) (ANSWER becomes empty/NODATA), because BIG-IP starts matching the most specific zone.

Therefore, creating the new zone first causes an immediate service impact unless all RRsets are already present in [f5.my.com](http://f5.my.com) at the moment the zone is created.

Request:

Could you please provide the recommended, supported procedure to migrate RRsets/WideIP-related records from [my.com](http://my.com) to a new authoritative subzone [f5.my.com](http://f5.my.com) on BIG-IP DNS without downtime?

---

<div class="post-metadata">

**Author:** ![mwolf](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/mwolf/32/33723_2.png) [@mwolf](https://community.f5.com/u/mwolf)\
**Post date:** [August 18, 2026, 12:03am UTC](https://community.f5.com/t/zonerunner-zero-downtime-migration-of-records-from-zone-to-zone/77328/2 "2026-08-18T00:03:45Z")

</div>

@Pak

It would be much easier to add a completely new subdomain then moving existing records into subdomain of the same name.&nbsp; This is not only an BIG-IP DNS issue. It’s an issue for any implementation of BIND.

Do you have multiple BIG-IP DNS devices in a DNS sync group?&nbsp; You have to be careful to not get devices out of sync.

ZoneRunner uses DNS dynamic updates to update the zone files. You can freeze the zones and manually update the zone files,

KB K7032.

F5 does not support manually editing the named.conf file, KB K7176. All named.conf changes have to be done via ZoneRunner.

You may want to open a F5 support case. They may have a better process then what I would do.

What I would do minimize the downtime. A high level process.

1. Add zone [f5.my.com](http://f5.my.com) via ZoneRunner.
2. Wait for DNS sync group update.
3. make a backup copy of all zone files.
4. Freeze all zones. See KB K7032
5. rndc sync -clean
6. Manually edit the [f5.my.com](http://f5.my.com) zone file to add the DNS records.
7. Manually edit the [my.com](http://my.com) zone file to remove the DNS records.
8. named-checkzone on all edited zones.
9. Thaw all zones
10. bigstart start zrd - Restart ZoneRunner
11. touch /var/named/config/named.conf to force a sync DNS group update.

[K7032: Freezing zone files to allow manual update to ZoneRunner-managed zone files](https://my.f5.com/manage/s/article/K7032)

Good luck,

Matthew
