Advertisement
Guest User

DNS SMB4-3

a guest
May 19th, 2010
88
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.22 KB | None | 0 0
  1. # This file should be included in your main BIND configuration file
  2. #
  3. # For example with
  4. # include "/opt/samba4/private/named.conf";
  5.  
  6. zone "example.org." IN {
  7. type master;
  8. file "/opt/samba4/private/dns/example.org.zone";
  9. /*
  10. * the list of principals and what they can change is created
  11. * dynamically by Samba, based on the membership of the domain controllers
  12. * group. The provision just creates this file as an empty file.
  13. */
  14. include "/opt/samba4/private/named.conf.update";
  15.  
  16. /* we need to use check-names ignore so _msdcs A records can be created */
  17. check-names ignore;
  18. };
  19.  
  20. # The reverse zone configuration is optional. The following example assumes a
  21. # subnet of 192.168.123.0/24:
  22.  
  23. /*
  24. zone "56.168.192.in-addr.arpa" in {
  25. type master;
  26. file "56.168.192.in-addr.arpa.zone";
  27. update-policy {
  28. grant *.ORG wildcard *.56.168.192.in-addr.arpa. PTR;
  29. };
  30. };
  31. */
  32.  
  33. # Note that the reverse zone file is not created during the provision process.
  34.  
  35. # The most recent BIND versions (9.5.0a5 or later) support secure GSS-TSIG
  36. # updates. If you are running an earlier version of BIND, or if you do not wish
  37. # to use secure GSS-TSIG updates, you may remove the update-policy sections in
  38. # both examples above.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement