Browse Source

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@
OPENBSD_5_1
sobrado 13 years ago
parent
commit
ad486a01df
1 changed files with 4 additions and 4 deletions
  1. +4
    -4
      src/etc/nsd.conf

+ 4
- 4
src/etc/nsd.conf View File

@ -1,11 +1,11 @@
# $OpenBSD: nsd.conf,v 1.4 2010/08/26 19:05:14 jakob Exp $
# $OpenBSD: nsd.conf,v 1.5 2011/12/15 14:51:46 sobrado Exp $
server:
hide-version: yes
## tsig key example
#key:
# name: "key1.example.com"
# name: "tsig1.example.com."
# algorithm: hmac-sha256
# secret: "bWVrbWl0YXNkaWdvYXQ="
@ -20,5 +20,5 @@ server:
#zone:
# name: "example.net"
# zonefile: "example.net"
# allow-notify: 192.0.2.2 key1
# request-xfr: 192.0.2.2 key1
# allow-notify: 192.0.2.2 tsig1.example.com.
# request-xfr: 192.0.2.2 tsig1.example.com.

Loading…
Cancel
Save