Hi Jadon, It sounds like a weird issue to me, when I messed up my Designate environment, usually the zones transitioned to ERROR, even if it took some time, but never stuck on PENDING. I suspect either Worker didn't move the state of those zones to ACTIVE for some reason, but even if it didn't, I think WorkerPeriodicRecovery should have moved it. Can you reproduce this issue on devstack? Can you share your environment's pools.yaml file? On Mon, Sep 22, 2025 at 5:16 PM Jadon Naas <jadon.naas@gmail.com> wrote:

Hello!

I am using Designate on 2023.2 with a PowerDNS backend. I have a recordset with three A records created through Designate. The A records are stuck in "PENDING" state with action "CREATE" or "UPDATE". The records were successfully created in PowerDNS, and changes are pushed to PowerDNS. However, the record status never finishes updating.

Deleting and recreating the recordset results in the same situation. I do not see any notable errors in the logs for Designate or for PowerDNS. I have checked that the Desigate configuration for the nameservers and for the targets match the correct IP addresses for my PowerDNS server and for my Designate service hosts.

Would folks have any suggestions for what I could do to determine what is preventing Designate from updating these records or to manually update the status of the records?

Thank you!

Jadon Naas