The state of a primary DNS server.

server s is the server of the primary.

data s is the data store of s.

with_data s now ts trie replaces the current data with trie in s. The returned notifications should be send out.

with_keys s now ts keys replaces the current keys with keys in s, and generates notifications.

trie_cache s is the trie cache of the server.

create ~trie_cache_entries ~keys ~unauthenticated_zone_transfer ~tsig_verify ~tsig_sign ~rng data creates a primary server. If unauthenticated_zone_transfer is provided and true (defaults to false), anyone can transfer the zones. trie_cache_entries is the backlog to keep in memory for incremental zone transfers (IXFR, default is 5). This affects memory usage.

handle_packet ~packet_callback s now ts src src_port proto key packet handles the given packet, returning new state, an answer, and potentially notify packets to secondary name servers. If packet_callback is specified, it is called for each incoming query. If it returns Some reply, this reply is used instead of the usual lookup in the zone data. It can be used for custom query processing, such as for load balancing or transporting data.

handle_buf ~packet_callback s now ts proto src src_port buffer decodes the buffer, processes the DNS frame using handle_packet, and encodes the reply. The result is a new state, potentially a list of answers to the requestor, a list of notifications to send out, information whether a notify (or signed notify) was received, and the hmac key used for authentication. If packet_callback is specified, it is called for each incoming query. If it returns Some reply, this reply is used instead of the usual lookup in the zone data. This can be used for custom query processing, such as for load balancing or transporting data.

closed s ip marks the connection to ip closed.

timer s now ts may encode some notifications to secondary name servers if previous ones were not acknowledged.

to_be_notified s zone returns a list of pairs of IP address and optional tsig key name of the servers to be notified for a zone change. This list is based on (a) NS entries for the zone, (b) registered TSIG transfer keys, and (c) active connection (which transmitted a signed SOA).