OCF_HEARTBEAT_DNSUPD(7)

💖 NAME 💖

okay bestie, welcome to the OCF_HEARTBEAT_DNSUPD(7) page from OCF resource agents — this is the ocf_heartbeat_dnsupdate resource agent, and it's literally about IP take-over via dynamic DNS update. no cap. 💅

🦋 SYNOPSIS 🦋

dnsupdate [start | stop | status | monitor | meta-data | validate-all]

🌸 DESCRIPTION 🌸

This resource agent manages IP take-over via dynamic DNS updates. that's the whole main-character job, fr fr. ✨

🎀 SUPPORTED PARAMETERS 🎀

okay so here are the parameters, with the receipts so you don't miss a single one:

• hostname — Either the hostname whose IP address will need to be updated (in case of type=A) or alias whose hostname will need to be updated (in case of type=CNAME). metadata: unique, required, string, no default. 👑
• type — The type of DNS record that need to be updated (A or CNAME). metadata: optional, string, default "A".
• ip — IP address to set. metadata: optional, string, no default.
• cname — The CNAME whose hostname address will need to be updated. metadata: optional, string, no default.
• ttl — Time to live, in seconds, for the DNS record. This affects how soon DNS updates propagate. It should be a reasonable compromise between update speed and DNS server load. If using booth, the ticket timeout is a good start. metadata: optional, integer, default 300.
• keyfile — The file containing the shared secret needed to update the DNS record. Please see the nsupdate man page for the exact syntax. metadata: optional, string, no default.
• server — Which DNS server to send these updates for. When no server is provided, this defaults to the promoted server for the correct zone. metadata: optional, string, no default.
• serverport — Port number on the DNS server. ⚠️ Note: due to a limitation in the nsupdate command, this option will only take effect if you also specify the DNS server! metadata: optional, integer, default 53.
• nsupdate_opts — Additional options to be passed to nsupdate. metadata: optional, string, no default.
• unregister_on_stop — Whether or not to actively remove records on stop. This is not needed for normal operation, since the site taking over the IP address will delete all previous records. metadata: optional, boolean, default false.

🔥 SUPPORTED ACTIONS 🔥

This resource agent supports the following actions (operations):

• start — Starts the resource. Suggested minimum timeout: 30s.
• stop — Stops the resource. Suggested minimum timeout: 30s.
• status — Performs a status check. Suggested minimum timeout: 30s. Suggested interval: 10s.
• monitor — Performs a detailed status check. Suggested minimum timeout: 30s. Suggested interval: 10s.
• meta-data — Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5s.
• validate-all — Performs a validation of the resource configuration. Suggested minimum timeout: 5s.

🧚 EXAMPLE CRM SHELL 🧚

The following is an example configuration for a dnsupdate resource using the crm(8) shell:

           primitive p_dnsupdate ocf:heartbeat:dnsupdate \
             params \
               hostname=string \
             op monitor depth="0" timeout="30s" interval="10s"

🦄 EXAMPLE PCS 🦄

The following is an example configuration for a dnsupdate resource using pcs(8):

           pcs resource create p_dnsupdate ocf:heartbeat:dnsupdate \
             hostname=string \
             op monitor OCF_CHECK_LEVEL="0" timeout="30s" interval="10s"

🌈 SEE ALSO 🌈

http://clusterlabs.org/ — go check it out, bestie. 🫶

💜 AUTHOR 💜

ClusterLabs contributors (see the resource agent source for information about individual authors). they ate, no crumbs. 👑

---

k bye bestie — this page is from resource-agents UNKNOWN, dated 10/01/2026. stay iconic, and may your DNS updates always propagate. 💖✨