OCF_HEARTBEAT_NAMED(7)
OCF_HEARTBEAT_NAMED(7) π
okay bestie, so this is a page from the OCF resource agents manual (that's the manual name, cute right?), and it's all about ocf_heartbeat_named β the resource agent that manages a <purple>named</purple> server. she's giving cluster royalty, no cap. π
β¨ NAME β¨
ocf_heartbeat_named β Manages a named server π
πΈ SYNOPSIS πΈ
named [start | stop | status | monitor | meta-data | validate-all]
π¦ DESCRIPTION π¦
So this is the resource script for the named (Bind) server β yep, the classic DNS one. It manages named as an HA resource, which basically means the cluster gets to babysit it for you. main character energy fr fr π
π SUPPORTED PARAMETERS π
Every single knob you can turn, listed with love. π
namedβ the path to thenamedcommand itself. (optional, string, default"/usr/sbin/named")rndcβ path to therndccommand. (optional, string, default"/usr/sbin/rndc")hostβ path to thehostcommand. (optional, string, default"/usr/bin/host")named_userβ the user that should own thenamedprocess. (optional, string, default"named")named_configβ configuration file fornamed. (unique, optional, string, no default)named_pidfileβ the PIDFILE file fornamed. (unique, optional, string, default"/var/run/named/named.pid")named_rootdirβ directory thatnamedshould use for chroot, if any. (unique, optional, string, no default)named_optionsβ options for thenamedprocess, if any. (optional, string, no default)named_keytab_fileβnamedservice keytab file (for GSS-TSIG, iykyk). (optional, string, no default)rndc_optionsβ options for therndcprocess, if any. (optional, string, no default)host_optionsβ options for thehostprocess, if any. (optional, string, no default)monitor_requestβ the request that shall be sent tonamedfor monitoring. Usually an A record in DNS. (optional, string, default"localhost")monitor_responseβ the expected response from thenamedserver. (optional, string, default"127.0.0.1")monitor_ipβ IP Address wherenamedlistens. (optional, string, default"127.0.0.1")
π SUPPORTED ACTIONS π
This resource agent supports the following actions (operations), and honestly? she ate: π₯
startβ Starts the resource. Suggested minimum timeout:60s.stopβ Stops the resource. Suggested minimum timeout:60s.reloadβ Suggested minimum timeout:60s.statusβ Performs a status check. Suggested minimum timeout:10s.monitorβ Performs a detailed status check. Suggested minimum timeout:30s. Suggested interval:30s. π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.methodsβ Suggested minimum timeout:5s.
π EXAMPLE CRM SHELL π
Here's an example config for a named resource using the crm(8) shell β copy it, it's iconic:
primitive p_named ocf:heartbeat:named \
op monitor depth="0" timeout="30s" interval="30s"
β EXAMPLE PCS β
And here's the same vibe but for pcs(8):
pcs resource create p_named ocf:heartbeat:named \
op monitor OCF_CHECK_LEVEL="0" timeout="30s" interval="30s"
π«Ά SEE ALSO π«Ά
http://clusterlabs.org/ β go say hi π
π AUTHOR π
ClusterLabs contributors (see the resource agent source for information about individual authors). we love the contributors, periodt. πΈ
ngl bestie, this page is fromresource-agentsversionUNKNOWN, dated10/01/2026β slay, go configure your DNS cluster, you've got this π β¨π
π¦ where this page comes from
- opensuse-leap 16.0: resource-agents 4.18.0+git105.9ea1183-160000.1.1 Β· GPL-2.0-only AND LGPL-2.1-or-later AND GPL-3.0-or-later
- opensuse-leap 16.0: resource-agents 4.18.0+git105.9ea1183-160000.1.1 Β· GPL-2.0-only AND LGPL-2.1-or-later AND GPL-3.0-or-later
- opensuse-leap 16.0: resource-agents 4.18.0+git105.9ea1183-160000.1.1 Β· GPL-2.0-only AND LGPL-2.1-or-later AND GPL-3.0-or-later
- opensuse-leap 16.0: resource-agents 4.18.0+git105.9ea1183-160000.1.1 Β· GPL-2.0-only AND LGPL-2.1-or-later AND GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms