Back to Changelog
Panel Backend
v1.0.573
A mirrored DNS zone no longer waits an hour for its first transfer
Improvements
2- Existing servers in that state repair themselves: on the first check after the update, every mirrored zone without a zone file is fetched.
- Includes everything in 1.0.572.
Bug Fix
1- On a secondary DNS server, a mirrored zone whose very first transfer was refused stayed empty for up to an hour. Creating the mirror only reloaded BIND, and BIND does not retry a refused transfer until the zone's retry timer expires; only a zone edited on the primary came over, because the change notification triggers an immediate transfer. This happens whenever the primary is told about the secondary after the mirrors were created. The panel now asks BIND explicitly to fetch any mirrored zone that has no zone file yet, so the first sync no longer depends on that timer. Mirrors that already work are left alone, and each zone is asked for at most once per server start.