#
# Optional path to config directory (default: /etc/dns-manager).
#

#etc_dir: /etc/dns-manager

#
# Optional paths to named_checkconf and rndc binaries.
# If unset, both are looked up on PATH.
#

#named_checkconf: /usr/bin/named-checkconf
#rndc: /usr/bin/rndc

#
# Optional path to named.conf.
#

#named_conf: /etc/bind/named.conf

#
# Optional IP address of the DNS server (default: 127.0.0.1).
#

#dns_ip: 127.0.0.1

#
# Optional path to the hooks base directory (default: <etc_dir>/hooks).
# Executable files placed in this tree are run around zone and record mutations. The tree narrows
# progressively; every level is optional and a hook fires for every event along its path:
#
#   hooks/                          -> every action and phase (zone+record, add+delete, pre+post)
#   hooks/<kind>/                   -> all actions/phases of <kind> (zone|record)
#   hooks/<kind>/<action>/          -> both phases of <action> (add|delete)
#   hooks/<kind>/<action>/<phase>/  -> single phase only (pre|post)
#
# All matching hooks across all levels are collected and run sorted by filename (run-parts style);
# only executable files are run. Each hook inherits the terminal: stdout/stderr appear live and it
# may be interactive (prompt and read stdin). In batch mode (-b) stdin is /dev/null, so reads get EOF.
# A pre-hook exiting non-zero aborts the operation (exit code 190); a post-hook failure prints an ERROR and continues.
# Hooks receive context via env vars (DNSMGR_KIND/ACTION/PHASE/ZONE/VIEW and, for records,
# DNSMGR_RECORD_NAME/TTL/TYPE/VALUE).
# DNSMGR_ZONE_FILE (zone file path) is set only for managed zones and and not for zone add pre-hooks nor for zone delete post-hooks.
#

#hooks_dir: /etc/dns-manager/hooks

#
# Dictionary of paths to key files (TSIG) per view used for zone transfers and DDNS updates.
# This option is mandatory when using views other than the default (_default) or if the usage of a key
# is mandatory to transfer and/or update zones. The keys of this dictionary are either the name of a view
# or a specific zone in a view (zone@view).
# Keep in mind that the first key found in the key files is used and all other keys are ignored.
#

#dns_keyfiles:
#  _default: /etc/bind/rndc.key
#  example.tld@_default: /etc/bind/another.key

#
# Optional path to key file passed to rndc (-k option), otherwise rndc uses its default key file.
# This key is used to reconfigure Bind when adding or deleting zones.
#

#control_key: /etc/bind/rndc.key

#
# Dictionary of configuration options per view.
#

zones_config:
  _default:
    #
    # Optional path to directory where config files per zone are stored.
    # Default: <etc_dir>/<view>.zones
    #

    #config_dir: /etc/dns-manager/_default.zones

    #
    # Path to config file that has to be included in named.conf.
    # All configs stored in <config_dir> will be concatenated and written to it. The detour via this file is necessary
    # because Bind does not support wildcards when including config files.
    #

    config_file: /etc/bind/default_zones.conf

    #
    # Path to the directory where the Bind zone files of this view are stored.
    # This is typically "/etc/bind/dyn" in an single view environment.
    #

    zone_dir: /etc/bind/dyn

    #
    # Optional Bind catalog zone that will be managed automatically when adding or deleting zones.
    # The view may also be specified if necessary (zone@view). 
    #
    # IMPORTANT: It is recommended to manually add catalog zones to Bind to prevent accidental deletion.
    #

    #catalog_zone: catalog.example.tld

    #
    # Paths to config and zone default templates used when adding zones.
    # Required to add a zone unless overridden per-invocation via dns-zone-add -t/-z.
    #

    #templates:
    #  config: /etc/dns-manager/templates/zone.config.template
    #  zone: /etc/dns-manager/templates/zone.template