A zone is considered broken when it is not receiving updates anymore. Its status can be “ERROR” if Designate detected the error condition or it can be stuck in “PENDING” for a long time.
Review the logs from the API, Central, Producer, Worker and MiniDNS. Identify the transaction ID of the last successful change and the first failing change. Using the ID, you can filter logs from the Designate components that are related to the same transaction. Look for log messages with ERROR level before and after the first failing update.
Failures in updating a zone are usually related to problems in Producer, Worker, MiniDNS or the database.
Ensure the services are running and network connectivity is not impaired.
Transient network issues can be the cause of a broken zone. Producer and Worker are stateful services and perform attempts at restoring failing zones over time. Restarting the services will trigger new attempts.
Deleted zones are flagged with “status” set to “DELETED” and “task” set to “NONE” once the deletion process terminates successfully.
Port numbers are configurable: review your designate.conf
The default values are:
|Component (header rows optional)||Protocol||Port numbers|
HTTP[S] by the API, RabbitMQ and the MySQL protocol by most components, DNS (resolution and XFR), ZooKeeper, Memcached.
The API, Central, Producer, Worker, MiniDNS
Pool and Producer
API and Worker
Designate can be monitored by various monitoring systems listed here
OpenStack recommends Monasca