5.2. DNS management

Cobbler can optionally manage DNS configuration. This feature is off by default.

The following options are available for modules.dns.module:

  • "managers.bind"

  • "managers.dnsmasq"

For this setting to take effect manage_dns must be set to True.

All managed files will be updated each time cobbler sync is run, and not until then, so it is important to remember to use cobbler sync when using this feature.

5.2.1. bind DNS

If using BIND, you must define the zones to be managed with. This is done with two options

  • manage_forward_zones: This option is a list of domain names.

  • manage_reverse_zones: This option is a list of IP addresses.

While the built-in templates provide a good starting point for many environment, they may not be suitable for all use-cases. As such, these files must be user edited for the user’s particular networking environment. Read the files and understand how BIND works before proceeding.

Helpful links:

Templates used during generation:

  • named.conf: A template with the tags named_primary and active.

  • secondary.conf: A template with the tags named_secondary and active.

  • Default zone template: A template with the tags named_zone_default and active.

  • Specific zone template: A template with the tags named_zone_specifc and your DNS zone name (e.g. example.org).

5.2.2. dnsmasq DNS

Helpful links:

Templates used during generation:

  • A template with the tags dnsmasq and active qualifies.

5.2.3. ndjbdns DNS

If using ndjbdns, the template is /etc/cobbler/ndjbdns.template. Read the file and understand how ndjbdns works before proceeding.

For this the DNS server tools of D.J. Bernstein need to be installed.

Helpful links:

Templates used during generation:

  • A template with the tags ndjbdns and active qualifies.