Cannot delete zone from designate if zone's SOA is actually hosted by a forwarder/external dns
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
New
|
Undecided
|
Unassigned | ||
OpenStack Designate Charm |
Triaged
|
Undecided
|
Unassigned |
Bug Description
This is an upstream Designate bug based on packages installed by our bionic/queens cloud charm configs.
If you add a zone to designate that is actually a zone owned by an upstream DNS server serviced by the forwarders defined for bind, you cannot delete the zone from designate.
You will see the logs looping with:
https:/
The flag "RA" denotes that this is a referred answer, not an authoritative answer.
In the code, the check is whether the response from Designate is authoritative.
With the DNS backend network included in allowed_
Workaround, remove the forwarders from your charm config, let the zone deletion succeed, then re-add your forwarders.
Another workaround is to configure your dns-backend network into allowed_nets instead of allowed_
tags: | added: cpe-onsite |
Changed in charm-designate: | |
status: | New → Triaged |
experiend while working around https:/ /bugs.launchpad .net/charm- designate- bind/+bug/ 1806485