Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- # This file should be included in your main BIND configuration file
- #
- # For example with
- # include "/opt/samba4/private/named.conf";
- zone "example.org." IN {
- type master;
- file "/opt/samba4/private/dns/example.org.zone";
- /*
- * the list of principals and what they can change is created
- * dynamically by Samba, based on the membership of the domain controllers
- * group. The provision just creates this file as an empty file.
- */
- include "/opt/samba4/private/named.conf.update";
- /* we need to use check-names ignore so _msdcs A records can be created */
- check-names ignore;
- };
- # The reverse zone configuration is optional. The following example assumes a
- # subnet of 192.168.123.0/24:
- /*
- zone "56.168.192.in-addr.arpa" in {
- type master;
- file "56.168.192.in-addr.arpa.zone";
- update-policy {
- grant *.ORG wildcard *.56.168.192.in-addr.arpa. PTR;
- };
- };
- */
- # Note that the reverse zone file is not created during the provision process.
- # The most recent BIND versions (9.5.0a5 or later) support secure GSS-TSIG
- # updates. If you are running an earlier version of BIND, or if you do not wish
- # to use secure GSS-TSIG updates, you may remove the update-policy sections in
- # both examples above.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement