path: root/prog/6/6d.conf

the example configuration file for 6d
this is where you define your zones/networks and static entries
syntax description:
- all lines that are unparsable are considered comments and ignored
- zones/networks are defined with a space separated list of the following items on the same line
	1) an ipv6 network address (see `man inet_pton`) and a netmask with a '/' in between
	2) the admin email address of the dns administrator
	3) a space-separated list of FQDNs of nameservers for this zone, the first entry being the master
- static PTRs for hosts are defined by an IPv6 address and FQDN, separated by a single space on a single line
- NS delegations for subnetworks are defined by an IPv6 subnetwork (address+mask) and nameserver FQDNs, with everything separated by a single space
- the order of configuration lines does not matter

the following defines a dns zone. there can be many such lines for different networks.
those are authoritative zones for which on-the-fly generation will occur.
all nameservers, provided here, must be 6d nameservers or at least 6d nameservers behind a DNS proxy, such as bind.
there can be as many nameservers (but at least one) after the admin email
2001:db8::/32 dns@t-2.net.example dns1.t-2.net.example dns2.t-2.net.example

the following line defines a static PTR FQDN for a single host
2001:db8:0:d::b90a tranzistor.sijanec.eu.example

the following line defines static NS records for a subnetwork.
this subnetwork must be a subnetwork of a zone that 6d will generate records for.
when 6d will be asked for an address that is part of this subnetwork, it will state that some other server is authoritative for this subnetwork and direct the client to the server provided.
there can be as many nameservers (but at least one) after the network name
2001:db8:e77:5500::/56 ns1.sijanec.org.example ns2.sijanec.org.example

you can run `6d dry <config file>` to parse the configuration file, output it and exit without starting the daemon