Bind9 environment
Environment variables
Bind9 environment variables
| variable name | description |
|---|---|
PATH |
“The sequence of path prefixes that certain functions and utilities apply in searching for an executable file known only by a filename. The prefixes are separated by a colon (:) When a non-zero-length prefix is applied to this filename, a slash is inserted between the prefix and the filename. A zero-length prefix is a legacy feature that indicates the current working directory. It appears as two adjacent colons (::), as an initial colon preceding the rest of the list, or as a trailing colon following the rest of the list. A portable application must use an actual pathname (such as .) to represent the current working directory in PATH. The list is searched from beginning to end, applying the filename to each prefix, until an executable file with the specified name and appropriate execution permissions is found. If the pathname being sought contains a slash, the search through the path prefixes will not be performed. If the pathname begins with a slash, the specified path is resolved (see pathname resolution ). If PATH is unset or is set to null, the path search is implementation-dependent. The path separator on Windows is a semicolon, not a colon, as in the Unix world. Setting the path has the effect of automatically locating, say, dig or nsupdate. However, there is a Windows version of nslookup that will be found first. Using the BIND version of nslookup either requires a full path command, such as C:\Program Files\ISC BIND 9\bin\nslookup.exe (or C:\Program Files (x86)\ISC BIND 9\bin\nslookup.exe for a 32-bit BIND install on a Windows 64 bit platform) when running it from the command line. Alternatively, the preceding path directive can be placed first in the path list, which, in turn, has the disadvantage that it will add an extra check for all other program loading operations that use normal Windows locations.” |
COMSPEC |
“COMSPEC or ComSpec is one of the environment variables used in DOS, OS/2 and Windows, which normally points to the command line interpreter, which is by default COMMAND.COM in DOS or CMD.EXE in OS/2 and Windows NT. The variable name is written in all-uppercase under DOS and OS/2. Under Windows, which also supports lowercase environment variable names, the variable name is COMSPEC inside the DOS emulator NTVDM and for any DOS programs, and ComSpec under CMD.EXE. The variable’s contents can be displayed by typing SET or ECHO %COMSPEC% at the command prompt. The environment variable by default points to the full path of the command line interpreter. It can also be made by a different company or be a different version.” |
IDN_DISABLE |
“If you’d like to turn off the IDN support for some reason, defines the IDN_DISABLE environment variable. The IDN support is disabled if the variable is set when dig runs.” |
ISC_TASK_WORKERS |
Used during unit testing of Bind9. This is not used during production. |
ISC_TASKS_MIN |
Used during unit testing of Bind9. This is not used during production. |
KRB5_KTNAME |
Used to minimize memory leakage associated with KRB5 API calls |
LANG |
“This variable determines the locale category for native language, local customs and coded character set in the absence of the LC_ALL and other LC_* (LC_COLLATE, LC_CTYPE, LC_MESSAGES, LC_MONETARY, LC_NUMERIC, LC_TIME) environment variables. This can be used by applications to determine the language to use for error messages and instructions, collating sequences, date formats, and so forth. Always use a value for LANG that is supported by the UNIX or Linux operating system you are using. To obtain the locale names for your UNIX or Linux system, enter the following command: locale -a. If you specify the LANG environment variable and also modify the regional settings then the LANG environment variable will override the regional setting. As specified by open systems standards, other environment variables override LANG for some or all locale categories. These variables include the following:
If any of the previous variables are set, you must remove their setting for the LANG variable to have full effect. Some values found on Linux platforms (via |
LC_ALL |
“This variable determines the values for all locale categories. The value of the LC_ALL environment variable has precedence over any of the other environment variables starting with LC_ (LC_COLLATE, LC_CTYPE, LC_MESSAGES, LC_MONETARY, LC_NUMERIC, LC_TIME) and the LANG environment variable.” |
LC_CTYPE |
“This variable determines the locale category for character handling functions, such as tolower(), toupper() and isalpha(). This environment variable determines the interpretation of sequences of bytes of text data as characters (for example, single- as opposed to multi-byte characters), the classification of characters (for example, alpha, digit, graph) and the behavior of character classes. Additional semantics of this variable, if any, are implementation-dependent.” |
NET_ORDER |
Set the sorting order of multiple IP addresses being displayed. Valid values are "inet4" or "inet6". |
PKCS11_PROVIDER |
“Declares the PKCS11 provider being used. Valid values are: "undefined", "libsofthsm2", "openssl"” |
TEMP |
A pathname of a directory made available for programs that need a place to create temporary files. |
TERM |
The terminal type for which output is to be prepared. This information is used by utilities and application programs wishing to exploit special capabilities specific to a terminal. The format and allowable values of this environment variable are unspecified. |
TZ |
“Timezone information. The contents of the environment variable named TZ are used by the ctime(), localtime(), strftime() and mktime() functions, and by various utilities, to override the default timezone. The value of TZ has one of the two forms (spaces inserted for clarity):
or:
If
|
ZKT_CONFFILE |
“Specifies the name of the default global configuration files.
|