2008-07-22 05:06:47 +04:00
# This file should be included in your main BIND configuration file
2007-08-24 05:57:54 +04:00
#
2008-07-22 05:06:47 +04:00
# For example with
2010-02-11 05:17:09 +03:00
# include "${NAMED_CONF}";
2007-08-24 05:57:54 +04:00
zone "${DNSDOMAIN}." IN {
2008-05-18 08:24:48 +04:00
type master;
2010-02-11 05:17:09 +03:00
file "${ZONE_FILE}";
2008-07-22 05:06:47 +04:00
/*
2010-02-11 07:25:13 +03:00
* 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.
2008-07-22 05:06:47 +04:00
*/
2010-02-11 07:25:13 +03:00
include "${NAMED_CONF_UPDATE}";
2010-01-16 05:19:50 +03:00
/* we need to use check-names ignore so _msdcs A records can be created */
check-names ignore;
2007-08-24 05:57:54 +04:00
};
2008-05-18 08:24:48 +04:00
# The reverse zone configuration is optional. The following example assumes a
# subnet of 192.168.123.0/24:
2008-07-22 05:06:47 +04:00
/*
2008-05-18 08:24:48 +04:00
zone "123.168.192.in-addr.arpa" in {
type master;
file "123.168.192.in-addr.arpa.zone";
update-policy {
grant ${REALM_WC} wildcard *.123.168.192.in-addr.arpa. PTR;
};
};
2008-07-22 05:06:47 +04:00
*/
2008-05-18 08:24:48 +04:00
# Note that the reverse zone file is not created during the provision process.
2012-07-02 02:06:53 +04:00
# The most recent BIND versions (9.8 or later) support secure GSS-TSIG
2008-05-18 08:24:48 +04:00
# 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.