Struct Bind9Manager 

pub struct Bind9Manager { /* private fields */ }

Manager for BIND9 servers via HTTP API sidecar.

The Bind9Manager provides methods for managing BIND9 servers running in Kubernetes pods via an HTTP API sidecar. The API sidecar executes rndc commands locally and manages zone files. Authentication uses Kubernetes ServiceAccount tokens.

Examples

use bindy::bind9::Bind9Manager;

let manager = Bind9Manager::new();

Implementations

impl Bind9Manager

pub fn new() -> Self

Create a new Bind9Manager.

Reads the ServiceAccount token from the default location and creates an HTTP client for API requests.

pub fn build_api_url(server: &str) -> String

Build the API base URL from a server address

Converts “service-name.namespace.svc.cluster.local:8080” or “service-name:8080” to <http://service-name.namespace.svc.cluster.local:8080> or <http://service-name:8080>

This is a public method for testing purposes.

pub async fn reload_zone(&self, zone_name: &str, server: &str) -> Result<()>

Reload a specific zone via HTTP API.

This operation is idempotent - if the zone doesn’t exist, it returns an error with a clear message indicating the zone was not found.

Arguments

• zone_name - Name of the zone to reload
• server - API server address (e.g., “bind9-primary-api:8080”)

Errors

Returns an error if the HTTP request fails or the zone cannot be reloaded.

pub async fn reload_all_zones(&self, server: &str) -> Result<()>

Reload all zones via HTTP API.

Errors

Returns an error if the HTTP request fails.

pub async fn retransfer_zone(&self, zone_name: &str, server: &str) -> Result<()>

Trigger zone transfer via HTTP API.

Errors

Returns an error if the HTTP request fails or the zone transfer cannot be initiated.

pub async fn freeze_zone(&self, zone_name: &str, server: &str) -> Result<()>

Freeze a zone to prevent dynamic updates via HTTP API.

Errors

Returns an error if the HTTP request fails or the zone cannot be frozen.

pub async fn thaw_zone(&self, zone_name: &str, server: &str) -> Result<()>

Thaw a frozen zone to allow dynamic updates via HTTP API.

Errors

Returns an error if the HTTP request fails or the zone cannot be thawed.

pub async fn zone_status(&self, zone_name: &str, server: &str) -> Result<String>

Get zone status via HTTP API.

Errors

Returns an error if the HTTP request fails or the zone status cannot be retrieved.

pub async fn zone_exists(&self, zone_name: &str, server: &str) -> bool

Check if a zone exists by trying to get its status.

Returns true if the zone exists and can be queried, false otherwise.

pub async fn server_status(&self, server: &str) -> Result<String>

Get server status via HTTP API.

Errors

Returns an error if the HTTP request fails or the server status cannot be retrieved.

pub async fn add_zones( &self, zone_name: &str, zone_type: &str, server: &str, key_data: &RndcKeyData, soa_record: Option<&SOARecord>, name_server_ips: Option<&HashMap<String, String>>, secondary_ips: Option<&[String]>, primary_ips: Option<&[String]>, ) -> Result<bool>

Add a zone via HTTP API (primary or secondary).

This is the centralized zone addition method that dispatches to either add_primary_zone or add_secondary_zone based on the zone type.

This operation is idempotent - if the zone already exists, it returns success without attempting to re-add it.

Arguments

• zone_name - Name of the zone (e.g., “example.com”)
• zone_type - Zone type (use ZONE_TYPE_PRIMARY or ZONE_TYPE_SECONDARY constants)
• server - API endpoint (e.g., “bind9-primary-api:8080” or “bind9-secondary-api:8080”)
• key_data - RNDC key data
• soa_record - Optional SOA record data (required for primary zones, ignored for secondary)
• name_server_ips - Optional map of nameserver hostnames to IP addresses (for primary zones)
• secondary_ips - Optional list of secondary server IPs for also-notify and allow-transfer (for primary zones)
• primary_ips - Optional list of primary server IPs to transfer from (for secondary zones)

Returns

Returns Ok(true) if the zone was added, Ok(false) if it already existed.

Errors

Returns an error if the HTTP request fails or the zone cannot be added.

pub async fn add_primary_zone( &self, zone_name: &str, server: &str, key_data: &RndcKeyData, soa_record: &SOARecord, name_server_ips: Option<&HashMap<String, String>>, secondary_ips: Option<&[String]>, ) -> Result<bool>

Add a new primary zone via HTTP API.

This operation is idempotent - if the zone already exists, it returns success without attempting to re-add it.

The zone is created with allow-update enabled for the TSIG key used by the operator. This allows dynamic DNS updates (RFC 2136) to add/update/delete records in the zone.

Note: This method creates a zone without initial content. For creating zones with initial SOA/NS records, use create_zone_http() instead.

Arguments

• zone_name - Name of the zone (e.g., “example.com”)
• server - API endpoint (e.g., “bind9-primary-api:8080”)
• key_data - RNDC key data (used for allow-update configuration)
• soa_record - SOA record data
• name_server_ips - Optional map of nameserver hostnames to IP addresses for glue records
• secondary_ips - Optional list of secondary server IPs for also-notify and allow-transfer

Returns

Returns Ok(true) if the zone was added, Ok(false) if it already existed.

Errors

Returns an error if the HTTP request fails or the zone cannot be added.

pub async fn add_secondary_zone( &self, zone_name: &str, server: &str, key_data: &RndcKeyData, primary_ips: &[String], ) -> Result<bool>

Add a secondary zone via HTTP API.

Creates a secondary zone that will transfer from the specified primary servers. This is a convenience method specifically for secondary zones.

Arguments

• zone_name - Name of the zone (e.g., “example.com”)
• server - API endpoint of the secondary server (e.g., “bind9-secondary-api:8080”)
• key_data - RNDC key data
• primary_ips - List of primary server IP addresses to transfer from

Returns

Returns Ok(true) if the zone was added, Ok(false) if it already existed.

Errors

Returns an error if the HTTP request fails or the zone cannot be added.

pub async fn create_zone_http( &self, zone_name: &str, zone_type: &str, zone_config: ZoneConfig, server: &str, key_data: &RndcKeyData, ) -> Result<()>

Create a zone via HTTP API with structured configuration.

This method sends a POST request to the API sidecar to create a zone using structured zone configuration from the bindcar library.

Arguments

• zone_name - Name of the zone (e.g., “example.com”)
• zone_type - Zone type (use ZONE_TYPE_PRIMARY or ZONE_TYPE_SECONDARY constants)
• zone_config - Structured zone configuration (converted to zone file by bindcar)
• server - API endpoint (e.g., “bind9-primary-api:8080”)
• key_data - RNDC authentication key (used as updateKeyName)

Errors

Returns an error if the HTTP request fails or the zone cannot be created.

pub async fn delete_zone(&self, zone_name: &str, server: &str) -> Result<()>

Delete a zone via HTTP API.

Errors

Returns an error if the HTTP request fails or the zone cannot be deleted.

pub async fn notify_zone(&self, zone_name: &str, server: &str) -> Result<()>

Notify secondaries about zone changes via HTTP API.

Errors

Returns an error if the HTTP request fails or the notification cannot be sent.

pub async fn add_a_record( &self, zone_name: &str, name: &str, ipv4: &str, ttl: Option<i32>, server: &str, key_data: &RndcKeyData, ) -> Result<()>

Add an A record using dynamic DNS update (RFC 2136).

Arguments

• zone_name - DNS zone name (e.g., “example.com”)
• name - Record name (e.g., “www” for www.example.com, or “@” for apex)
• ipv4 - IPv4 address
• ttl - Time to live in seconds (None = use zone default)
• server - DNS server address with port (e.g., “10.0.0.1:53”)
• key_data - TSIG key for authentication

Errors

Returns an error if the DNS update fails or the server rejects it.

pub async fn add_aaaa_record( &self, zone_name: &str, name: &str, ipv6: &str, ttl: Option<i32>, server: &str, key_data: &RndcKeyData, ) -> Result<()>

Add an AAAA record using dynamic DNS update (RFC 2136).

Errors

Returns an error if the DNS update fails or the server rejects it.

pub async fn add_cname_record( &self, zone_name: &str, name: &str, target: &str, ttl: Option<i32>, server: &str, key_data: &RndcKeyData, ) -> Result<()>

Add a CNAME record using dynamic DNS update (RFC 2136).

Errors

Returns an error if the DNS update fails or the server rejects it.

pub async fn add_txt_record( &self, zone_name: &str, name: &str, texts: &[String], ttl: Option<i32>, server: &str, key_data: &RndcKeyData, ) -> Result<()>

Add a TXT record using dynamic DNS update (RFC 2136).

Errors

Returns an error if the DNS update fails or the server rejects it.

pub async fn add_mx_record( &self, zone_name: &str, name: &str, priority: i32, mail_server: &str, ttl: Option<i32>, server: &str, key_data: &RndcKeyData, ) -> Result<()>

Add an MX record using dynamic DNS update (RFC 2136).

Errors

Returns an error if the DNS update fails or the server rejects it.

pub async fn add_ns_record( &self, zone_name: &str, name: &str, nameserver: &str, ttl: Option<i32>, server: &str, key_data: &RndcKeyData, ) -> Result<()>

Add an NS record using dynamic DNS update (RFC 2136).

Errors

Returns an error if the DNS update fails or the server rejects it.

pub async fn add_srv_record( &self, zone_name: &str, name: &str, srv_data: &SRVRecordData, server: &str, key_data: &RndcKeyData, ) -> Result<()>

Add an SRV record using dynamic DNS update (RFC 2136).

Errors

Returns an error if:

• DNS server connection fails
• TSIG signer creation fails
• DNS update is rejected by the server
• Invalid domain name or target

pub async fn add_caa_record( &self, zone_name: &str, name: &str, flags: i32, tag: &str, value: &str, ttl: Option<i32>, server: &str, key_data: &RndcKeyData, ) -> Result<()>

Add a CAA record using dynamic DNS update (RFC 2136).

Errors

Returns an error if:

• DNS server connection fails
• TSIG signer creation fails
• DNS update is rejected by the server
• Invalid domain name, flags, tag, or value

pub fn generate_rndc_key() -> RndcKeyData

Generate a new RNDC key with HMAC-SHA256.

Returns a base64-encoded 256-bit (32-byte) key suitable for rndc authentication.

pub fn create_rndc_secret_data( key_data: &RndcKeyData, ) -> BTreeMap<String, String>

Create a Kubernetes Secret manifest for an RNDC key.

Returns a BTreeMap suitable for use as Secret data.

pub fn parse_rndc_secret_data( data: &BTreeMap<String, Vec<u8>>, ) -> Result<RndcKeyData>

Parse RNDC key data from a Kubernetes Secret.

Supports two Secret formats:

1. Operator-generated (all 4 fields): key-name, algorithm, secret, rndc.key
2. External/user-managed (minimal): rndc.key only - parses the BIND9 key file

Errors

Returns an error if:

• Neither the metadata fields nor rndc.key are present
• The rndc.key file cannot be parsed
• Values are not valid UTF-8 strings

Trait Implementations

impl Clone for Bind9Manager

fn clone(&self) -> Bind9Manager

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for Bind9Manager

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for Bind9Manager

fn default() -> Self

Returns the “default value” for a type.