Switch nsd control socket from localhost to a unix domain socket.
OK sthen

Put commented minimal-reponses and refuse-any defaults into nsd.conf
so that the changed default will be pointed out to the admin by
sysmerge.

Idea & OK sthen

Switch example NSD config to splitting master and slave zones into different
subdirectories (/var/nsd/zones/{master,slave}) and create these in mtree.
Nearly everybody that uses NSD for slave zones that I talked to already has
this layout. Bikesh^Wdiscussed with ajacoutot florian millert and others.

ok ajacoutot@ florian@ phessler@ claudio@ jung@

Set verbosity to 1 (the default is 0) so we log incoming notifies
and zone xfers. OK florian@ deraadt@

Disable db file. It is believed to be a saner default for the common
use case.
sthen@ noticed a problem with missing records on shutdown.

OK sthen@

nsd.conf is not ready to be an example

Move more files into the examples directory...

new sample config entries for NSD 4.0.0

use a FQDN (i.e. one ending with a period) as tsig key example's name;
rename key1 to tsig1 to clearly identify this name as a transaction
signature digest; consistently use tsig key name on slave zone.

ok jakob@

better TSIG key example

add template nsd.conf (with examples)

remove unintentionally added file

add _nsd

Put commented minimal-reponses and refuse-any defaults into nsd.conf
so that the changed default will be pointed out to the admin by
sysmerge.

Idea & OK sthen

Switch example NSD config to splitting master and slave zones into different
subdirectories (/var/nsd/zones/{master,slave}) and create these in mtree.
Nearly everybody that uses NSD for slave zones that I talked to already has
this layout. Bikesh^Wdiscussed with ajacoutot florian millert and others.

ok ajacoutot@ florian@ phessler@ claudio@ jung@

Set verbosity to 1 (the default is 0) so we log incoming notifies
and zone xfers. OK florian@ deraadt@

Disable db file. It is believed to be a saner default for the common
use case.
sthen@ noticed a problem with missing records on shutdown.

OK sthen@

nsd.conf is not ready to be an example

Move more files into the examples directory...

new sample config entries for NSD 4.0.0

use a FQDN (i.e. one ending with a period) as tsig key example's name;
rename key1 to tsig1 to clearly identify this name as a transaction
signature digest; consistently use tsig key name on slave zone.

ok jakob@

better TSIG key example

add template nsd.conf (with examples)

remove unintentionally added file

add _nsd

Switch example NSD config to splitting master and slave zones into different
subdirectories (/var/nsd/zones/{master,slave}) and create these in mtree.
Nearly everybody that uses NSD for slave zones that I talked to already has
this layout. Bikesh^Wdiscussed with ajacoutot florian millert and others.

ok ajacoutot@ florian@ phessler@ claudio@ jung@

Set verbosity to 1 (the default is 0) so we log incoming notifies
and zone xfers. OK florian@ deraadt@

Disable db file. It is believed to be a saner default for the common
use case.
sthen@ noticed a problem with missing records on shutdown.

OK sthen@

nsd.conf is not ready to be an example

Move more files into the examples directory...

new sample config entries for NSD 4.0.0

use a FQDN (i.e. one ending with a period) as tsig key example's name;
rename key1 to tsig1 to clearly identify this name as a transaction
signature digest; consistently use tsig key name on slave zone.

ok jakob@

better TSIG key example

add template nsd.conf (with examples)

remove unintentionally added file

add _nsd