The agent based backends use an agent process to interact with the backend DNS server as opposed to directly talking to them over a management protocol. I wasn't part of the project when the agent based BIND9 backend was added, so I don't have the full context of why there is an agent for BIND9. I will note that all of the agent based backends are in the "untested" or "experimental" category: https://docs.openstack.org/designate/latest/admin/support-matrix.html Since the agent based drivers don't have many contributors now, I would expect to see more of them marked deprecated and removed in a future release. I would highly recommend you use the native backend if possible. Michael On Mon, Jun 6, 2022 at 11:54 PM Christian Rohmann <christian.rohmann@inovex.de> wrote:
On 07/06/2022 02:04, Michael Johnson wrote:
There are two ways zones can be resynced: 1. Using the "designate-manage pool update" command. This will force an update/recreate of all of the zones. 2. When a zone is in ERROR or PENDING for too long, the WorkerPeriodicRecovery task in producer will attempt to repair the zone.
Thanks again for these details! I suppose there is no option for a targeted run of this "pool update" command to just hit one backend server?
If you don't mind me asking yet another question ... what is the difference between running a regular backend or an agent backend? So https://github.com/openstack/designate/blob/master/designate/backend/impl_bi... vs. https://github.com/openstack/designate/blob/master/designate/backend/agent_b...
Regards and thanks again,
Christian