Changing the dns zone name of a cluster does not remove the old zone.
Bug #1438977 reported by
Andres Rodriguez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
If I change the zone name of a cluster, from say 'zone1.com' to 'zone11.com', the old 'zone1.com' does not get removed and files still remain in /etc/bind/maas/.
Also, when renaming, the zone declarations name does not change:
roaksoax@
named.conf.
named.conf.maas: file "/etc/bind/
Related branches
Changed in maas: | |
milestone: | none → 1.8.0 |
importance: | Undecided → High |
status: | New → Triaged |
description: | updated |
summary: |
- Changing the zone name of a cluster does not remove the old zone. + Changing the dns zone name of a cluster does not remove the old zone. |
Changed in maas: | |
milestone: | 1.8.0 → 1.9.0 |
Changed in maas: | |
status: | Triaged → Won't Fix |
To post a comment you must log in.
I'm not sure I understand this bug: maas/named. conf.maas, it doesn't matter so much. Granted, it's probably better to remove the zone files when they are not used anymore but this is just a cleanup. maas/named. conf.maas… ?
- You're right that old zone files are not being deleted when a zone changes. But since they are not referenced from /etc/bind/
- Now the part that I don't understand is "zone declarations name does not change". I've tested renaming a zone and I see the reference to the new zone being added to /etc/bind/