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

Pak​ 

It would be much easier to add a completely new subdomain then moving existing records into subdomain of the same name.  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?  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 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 zone file to add the DNS records.
7. Manually edit the 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

Good luck,

Matthew