[2.2] MAAS should avoid updating DNS if nothing changed

Bug #1712205 reported by Mike Pontillo on 2017-08-21
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

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.)

By checking the zone serial (per bug #1710308), MAAS now implicitly throttles reloads. But what it does NOT do is ensure that a DNS update is *necessary* (results in a change to the current DNS zone).

For example, MAAS may receive notification of an updated StaticIPAddress due to the DHCP server committing a new lease. Right now, this may trigger a DNS update, when nothing has actually changed.

Tags: sts Edit Tag help
description: updated
summary: - [2.2] MAAS should batch multiple DNS changes into a single reload
- request
+ [2.2] MAAS should avoid updating DNS if nothing changed
description: updated
Felipe Reyes (freyes) on 2017-08-22
tags: added: sts
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers