Say you have a domain on 184.108.40.206, and you have 220.127.116.11 linked to it for dns, DA will duplicate all A/AAAA records accordingly. So you'd have: www A 18.104.22.168 www A 22.214.171.124 however, some people might manually change the ns1/ns2 records to look like this: ns1 A 126.96.36.199 ns2 A 188.8.131.52 while the other records are doubled up. When DA creates the backup, it will remove the linkeds IPs from the zone, leaving just: www A 184.108.40.206 ns1 A 220.127.116.11 where this would actually cause the write to fail the zone write check, since if this was present: domain.com. NS ns2 the ns2 A record is now missing. This change is to check how many total A+AAAA records there are for that given name, and if there is only 1, then the value is not removed. This can span AAAA records too, eg: ns1 A 18.104.22.168 ns2 AAAA :::1:2:3:5 and DA will ensure if there is only 1 of either A or AAAA, that last value is not removed, even if it's only on the linked IP. This will allow it to pass the zone check. Backups will now also include the domains/domain.com.ip_list, so that DA can eventually be coded to know that the 22.214.171.124 value is an additional value, and should be swapped if the new server is using a different IP. As this change currently sits, when you restore the zone, if you were to set the User/Domain to use 126.96.36.199, it would end up like: www A 188.8.131.52 ns1 A 184.108.40.206 ns2 A 220.127.116.11 Since 18.104.22.168 is considered a "custom" IP at this point, since DA does not yet check that it's a linked IP (as the backup system only currently supports a single IP to restore to) If you're restoring to the same IPs, then it should be fine, it just gets a bit messy if you're restore to a different IP, then 22.214.171.124 would need to be swapped accordingly after the restore.