Directory layout of the OS/2 port

You will have less troubles if you use the directory layout given below! However, you can fit the OS/2 bind directory layout to your needs by setting the environment variables gives in brackets.

/tcpip/bin/
named.exe (or somewhere in your PATH)
named-xfer.exe (NAMED_XFER)
nslookup.exe (or somewhere in your PATH)
dig.exe (or somewhere in your PATH)
dnsquery.exe (or somewhere in your PATH)
host.exe (or somewhere in your PATH)

/tcpip/help/
nslookup.help (NAMED_HELP)

/tcpip/etc/ (ETC)
named.pid

/tcpip/etc/namedb/ (ETC)
named.boot (NAMED_BOOT)
(and your configuration files) (use 'directory' keyword in your named.boot)

/tmp/ (TMP or (TEMP)
named.run
named_dump.db
named.stats
xfer.trace
xfer.ddt.XXXXXX

Example:

• You are using MPTS (not LAPS, TCP/IP 2.0), so your ETC environment variable will likely point to x:/mptn/etc – your named.boot file should be located in x:/mptn/etc/namedb.
• Using MPTS want to have your bind executables in x:/mptn/bin – set NAMED_XFER to x:/mptn/bin, set NSLOOKUP_HELP to x:/mptn/help (and copy nslookup.help to x:/mptn/help of course).
• You absolutely want the named configuration files on c:/named – so set NAMED_BOOT to c:/named.

Warning: The OS/2 bind port has not been excessively tested in a multiple-drive configuration (say ETC = g:/mptn/etc, TMP = d:/tmp, NAMED_BOOT = c:/namedb, ...).