@@ -446,13 +446,13 @@ remote-control:
446
446
#allow-notify: 2001:db8::0/64 my_tsig_key_name
447
447
# By default, a secondary will request a zone transfer with IXFR/TCP.
448
448
# If you want to make use of IXFR/UDP use: UDP addr tsigkey
449
- # for a master that only speaks AXFR (like NSD) use AXFR addr tsigkey
449
+ # for a primary that only speaks AXFR use AXFR addr tsigkey
450
450
# If you want to require use of XFR-over-TLS use: addr tsigkey tlsauthname
451
451
#request-xfr: 192.0.2.2 the_tsig_key_name
452
452
#request-xfr: 192.0.2.2 the_tsig_key_name the_tls_auth_name
453
453
# Attention: You cannot use UDP and AXFR together. AXFR is always over
454
454
# TCP. If you use UDP, we highly recommend you to deploy TSIG.
455
- # Allow AXFR fallback if the master does not support IXFR. Default
455
+ # Allow AXFR fallback if the primary does not support IXFR. Default
456
456
# is yes.
457
457
#allow-axfr-fallback: yes
458
458
# set local interface for sending zone transfer requests.
@@ -484,8 +484,8 @@ remote-control:
484
484
# from that pattern are inserted into this one (as if it were a
485
485
# macro). The statement can be given in between other statements,
486
486
# because the order of access control elements can make a difference
487
- # (which master to request from first, which secondary to notify first).
488
- #include-pattern: "common-masters "
487
+ # (which primary to request from first, which secondary to notify first).
488
+ #include-pattern: "common-primaries "
489
489
490
490
# Verify zone before publishing.
491
491
# Default is value of verify-zones in verify.
@@ -530,7 +530,7 @@ remote-control:
530
530
# name: "example.com"
531
531
# you can give a pattern here, all the settings from that pattern
532
532
# are then inserted at this point
533
- # include-pattern: "master "
533
+ # include-pattern: "primary "
534
534
# You can also specify (additional) options directly for this zone.
535
535
# zonefile: "example.com.zone"
536
536
# request-xfr: 192.0.2.1 example.com.key
0 commit comments