MAAS currently reloads the named configuration after every DNS change. When a large number of changes occur, this has negative side-effects for bind9. (For context, see bug #1710278.)
MAAS should:
- Throttle consecutive updates. (For example, when the first DNS change occurs, schedule a task for a few seconds in the future which will update DNS, and don't ever schedule more additional updates while that task is pending.)
- Wait for confirmation that the reload is complete before starting another update.
MAAS currently reloads the named configuration after every DNS change. When a large number of changes occur, this has negative side-effects for bind9. (For context, see bug #1710278.)
MAAS should:
- Throttle consecutive updates. (For example, when the first DNS change occurs, schedule a task for a few seconds in the future which will update DNS, and don't ever schedule more additional updates while that task is pending.)
- Wait for confirmation that the reload is complete before starting another update.