From fa194c33b2963c84b406beb1008b8de565b531b6 Mon Sep 17 00:00:00 2001 From: Matthieu Patou Date: Thu, 9 Jun 2011 01:01:25 +0400 Subject: tests: Add alpha13 dumped provision --- .../selftest/provisions/alpha13/private/named.conf | 38 ++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 source4/selftest/provisions/alpha13/private/named.conf (limited to 'source4/selftest/provisions/alpha13/private/named.conf') diff --git a/source4/selftest/provisions/alpha13/private/named.conf b/source4/selftest/provisions/alpha13/private/named.conf new file mode 100644 index 0000000000..4d41024397 --- /dev/null +++ b/source4/selftest/provisions/alpha13/private/named.conf @@ -0,0 +1,38 @@ +# This file should be included in your main BIND configuration file +# +# For example with +# include "/home/mat/workspace/samba/alpha13/private/named.conf"; + +zone "alpha13.samba.corp." IN { + type master; + file "/home/mat/workspace/samba/alpha13/private/dns/alpha13.samba.corp.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 "/home/mat/workspace/samba/alpha13/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 "123.168.192.in-addr.arpa" in { + type master; + file "123.168.192.in-addr.arpa.zone"; + update-policy { + grant *.SAMBA.CORP wildcard *.123.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. -- cgit