Return to nsd.conf CVS log | Up to [local] / src / etc |
File: [local] / src / etc / nsd.conf (download)
Revision 1.11, Sun Apr 12 11:49:39 2015 UTC (9 years, 1 month ago) by 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@ |
# $OpenBSD: nsd.conf,v 1.11 2015/04/12 11:49:39 sthen Exp $ server: hide-version: yes verbosity: 1 database: "" # disable database ## bind to a specific address/port # ip-address: 192.0.2.53 # ip-address: 192.0.2.53@5678 # ip-address: 2001:db8::53 remote-control: control-enable: yes ## tsig key example #key: # name: "tsig1.example.com." # algorithm: hmac-sha256 # secret: "bWVrbWl0YXNkaWdvYXQ=" ## master zone example #zone: # name: "example.com" # zonefile: "master/example.com" # notify: 192.0.2.1 NOKEY # provide-xfr: 192.0.2.1 NOKEY ## slave zone example #zone: # name: "example.net" # zonefile: "slave/example.net" # allow-notify: 192.0.2.2 tsig1.example.com. # request-xfr: 192.0.2.2 tsig1.example.com. ## dynamically configured zones, used with "nsd-control addzone/delzone". ## filenames are constructed using the pattern: %s - zone name. ## %1 - first character of zone name, %2 second, ## %3 third. ## %z - topleveldomain label of zone, %y, %x next labels in name. #pattern: # name: "master" # zonefile: "master/%s.zone" # notify: 192.0.2.1 NOKEY # provide-xfr: 192.0.2.1 NOKEY