2022-03-17 20:46:28 +01:00
|
|
|
# User to run named as:
|
|
|
|
|
NAMED_USER=named
|
|
|
|
|
|
2023-12-20 22:10:47 +01:00
|
|
|
# Group to use for named related files and directories.
|
2022-03-17 20:46:28 +01:00
|
|
|
# By default, named will also run as the primary group of $NAMED_USER,
|
|
|
|
|
# which will usually be the same as what's listed below, but not
|
|
|
|
|
# necessarily if something other than the default of "named" is used.
|
|
|
|
|
NAMED_GROUP=named
|
|
|
|
|
|
|
|
|
|
# Options to run named with. At least -u $NAMED_USER is required, but
|
|
|
|
|
# additional options may be added if needed.
|
|
|
|
|
NAMED_OPTIONS="-u $NAMED_USER"
|
2023-12-20 22:10:47 +01:00
|
|
|
|
|
|
|
|
# If this is set to YES, then before starting named the startup script
|
|
|
|
|
# will make sure that /etc/rndc.key (if it exists) and the enitre contents
|
|
|
|
|
# of /var/named are chowned to $NAMED_USER:$NAMED_GROUP. If some of these
|
|
|
|
|
# files are improperly owned, named will refuse to start or may not work
|
|
|
|
|
# properly. This is also a useful setting when upgrading from an older BIND
|
|
|
|
|
# package that would run as root.
|
|
|
|
|
#
|
|
|
|
|
# If NAMED_CHOWN is set to anything other than YES (or is unset), then these
|
|
|
|
|
# files will not be chowned automatically and the admin will handle any
|
|
|
|
|
# required file ownerships.
|
|
|
|
|
NAMED_CHOWN=NO
|
