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 the named command itself. (optional, string, default "/usr/sbin/named")
  • rndc β€” path to the rndc command. (optional, string, default "/usr/sbin/rndc")
  • host β€” path to the host command. (optional, string, default "/usr/bin/host")
  • named_user β€” the user that should own the named process. (optional, string, default "named")
  • named_config β€” configuration file for named. (unique, optional, string, no default)
  • named_pidfile β€” the PIDFILE file for named. (unique, optional, string, default "/var/run/named/named.pid")
  • named_rootdir β€” directory that named should use for chroot, if any. (unique, optional, string, no default)
  • named_options β€” options for the named process, if any. (optional, string, no default)
  • named_keytab_file β€” named service keytab file (for GSS-TSIG, iykyk). (optional, string, no default)
  • rndc_options β€” options for the rndc process, if any. (optional, string, no default)
  • host_options β€” options for the host process, if any. (optional, string, no default)
  • monitor_request β€” the request that shall be sent to named for monitoring. Usually an A record in DNS. (optional, string, default "localhost")
  • monitor_response β€” the expected response from the named server. (optional, string, default "127.0.0.1")
  • monitor_ip β€” IP Address where named listens. (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 from resource-agents version UNKNOWN, dated 10/01/2026 β€” slay, go configure your DNS cluster, you've got this πŸ’…βœ¨πŸ“
πŸ“¦ where this page comes from