Activity log for bug #1807464

Date Who What changed Old value New value Message
2018-12-07 21:55:45 Drew Freiberger bug added bug
2018-12-07 21:57:06 Dmitrii Shcherbakov bug added subscriber Dmitrii Shcherbakov
2018-12-07 21:57:15 Dmitrii Shcherbakov tags canonical-bootstack canonical-bootstack cpe-onsite
2018-12-07 21:58:57 Drew Freiberger 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://pastebin.ubuntu.com/p/vgpzCQVRbb/ 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_recursion_nets, the recursive lookup northward within designate-bind will return an accurate, external SOA record where designate code expects none. Workaround, remove the forwarders from your charm config, let the zone deletion succeed, then re-add your forwarders. Anoterh workaround is to configure your dns-backend network into allowed_nets instead of allowed_recursion_nets in the charm config to prefect designate's mdns updates from querying upstream DNS accidentally. 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://pastebin.ubuntu.com/p/vgpzCQVRbb/ 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_recursion_nets, the recursive lookup northward within designate-bind will return an accurate, external SOA record where designate code expects none. 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_recursion_nets in the charm config to prefect designate's mdns updates from querying upstream DNS accidentally.
2019-05-14 11:36:34 Chris MacNaughton charm-designate: status New Triaged
2019-08-21 14:44:13 Tori Hegarty bug added subscriber Tori Hegarty
2019-08-21 16:15:11 Drew Freiberger bug task added designate
2020-07-21 07:32:15 James Page marked as duplicate 1802227