designate should create servers when related to designate-bind or other dns-backend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Designate Charm |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
When setting up a new designate service with designate-bind dns-backend, the designate-bind servers are not registered with the designate API.
It appears that one must manually run "designate server-create <designate-
Is this perhaps a bug given that my environment does not have pre-existing PTR and A records for my designate-bind servers?
For reference, using MAAS provider, designate and designate-bind are both deployed in lxds without static addressing. The designate and designate-bind units are able to find juju-XXXX-
If the IPs provide PTR records, the dns-backend relation should auto-populate servers in the API, even if they're not externally accessible at those particular NS records.
This sounds like more of a feature request than a bug. Marked it as wishlist for now, but feel free to push back if you think that the behavior as written is truly unexpected.