I have successfully tested this package on Warp 4 with TCP/IP 4.0 and 4.1 myself. Note that TCP/IP 4.1 requires EMX 0.9c fix 4 or later.
named.exe named-xfer.exe emxkill.exe ndc.cmdOptionally, you may also want to put these tools in the same directory:
nslookup.exe dig.exe dnsquery.exe host.exe addr.exe nsupdate.exe nssig.cmdMove this file from y:\xxx\bind\etc to your ETC directory
nslookup.help
cd %ETC% copy y:\xxx\bind\etc\samples\named.conf
md namedb
cd namedb
copy y:\xxx\bind\etc\samples\127.0.0.zone copy y:\xxx\bind\etc\samples\root.hint copy y:\xxx\bind\etc\samples\localhost.zone copy y:\xxx\bind\etc\samples\bogus.zone
epm named.conf
ndc start
But after thinking more about it, I decided not to since
You can find a lot of documentation, recommended reading, and examples in the DNS resources directory. Note that most examples will use the old BIND 4.x boot file format which is not compatible with BIND 8.1.1. See the BIND Configuration File Guide for documentation and examples of a BIND 8 config file.
The zone data file format has not changed, and examples of such files can therefore be copied directly.
If you just make sure that you haven't done any of the common errors listed in RFC 1912, then you have done very well. Better than for example aol.com (and if you can find the error in the aol.com zone, then maybe you can get a job as DNS technician there :-)
I assume you have a working setup, and are somewhat familiar with DNS zone data files. You need to know what a zone is to make a configuration file, but there is no need to edit the zone files (unless BIND detects errors in them).
The named.boot file (or NAMED.BT in IBM's DDNS) has been replaced by the much more configurable named.conf in BIND 8.x. You should study the BIND Configuration File Guide carefully to learn about the new syntax. There is a perl script (bin\named-bootconf.pl) which will upgrade your old named.boot to the new format. You will of course need access to a system with perl to run this script. I tested it with the OS/2 port of perl5, and it seemed to work just fine.
Using this script is strongly recommended if you run a server with more than a couple of zones.
perl5 y:\xxx\bind\bin\named-bootconf.pl < %ETC%\namedb\named.boot > %ETC%\named.confto create a configuration file from your old named.boot file.
If you don't have perl, you will have to write a named.conf file by hand:
cd %ETC% copy y:\xxx\bind\etc\samples\named.conf
zone "bind.org" IN {
type master;
file "db.bind.org";
};
zone "168.192.in-addr.arpa" IN {
type master;
file "db.192.168";
};
zone "bog.com" IN {
type slave;
file "db.bog.com";
masters {
10.10.2.224;
};
};
ndc start
The Changi Manual has excellent instructions on how to set up syslogd. And while you're there, check out Changi! This is the NNTP server for OS/2. You say don't need an NNTP server? How about an offline news solution for Netscape or NR/2?
Well, back to subject: BIND will write somthing like this to the syslog when it starts:
[localhost] May 12 23:06:51 named[91]: starting. named 8.1.2 Tue May 12 22:28:04 CED 1998 bjorn@ballingway.mork.no:D:/bind-812/src/bin/named [localhost] May 12 23:06:51 named[91]: directory . is world-writable [localhost] May 12 23:06:51 named[91]: cannot set resource limits on this system [localhost] May 12 23:06:51 named[91]: directory d:\mptn\etc\namedb is world-writable [localhost] May 12 23:06:51 named[91]: cannot set resource limits on this system [localhost] May 12 23:06:51 named[91]: master zone "localhost" (IN) loaded (serial 1) [localhost] May 12 23:06:51 named[91]: master zone "127.in-addr.arpa" (IN) loaded (serial 1) [localhost] May 12 23:06:51 named[91]: master zone "0.in-addr.arpa" (IN) loaded (serial 1) [localhost] May 12 23:06:51 named[91]: master zone "255.in-addr.arpa" (IN) loaded (serial 1) [localhost] May 12 23:06:51 named[91]: cache zone "" (IN) loaded (serial 0) [localhost] May 12 23:06:51 named[91]: listening on [127.0.0.1].53 (lo) [localhost] May 12 23:06:51 named[91]: listening on [192.168.3.7].53 (lan0) [localhost] May 12 23:06:51 named[91]: Forwarding source address is [0.0.0.0].52253 [localhost] May 12 23:06:51 named[92]: Ready to answer queries.You should watch these messages carefully whenever you update your data files. Watch out for messages like zone rejected due to errors, since this will cause your server to answer non-authoratively for those zones.
The four warning messages cannot set.. and directory is... are normal on an OS/2 system. I did not remove these for two reasons:
Debugging information is written to named.run in the database directory (except for startup messages, which are saved in the startup directory).
If you want to keep named.conf in %ETC% (recommended), use either
cd %ETC% namedor
named -c %ETC%\named.confor
ndc startNOTE: Unless you edit it, ndc.cmd will always look for named.pid and named.conf in %ETC%, regardless of any named startup parameters or config options.
| File name | Default location | How to move |
|---|---|---|
| named.exe | %PATH% | Must be in %PATH% if you want to use ndc |
| named-xfer.exe | %PATH% | named.conf options |
| ndc.cmd | %PATH% | |
| nslookup.exe | ||
| dig.exe | ||
| dnsquery.exe | ||
| host.exe | ||
| addr.exe | ||
| nsupdate.exe | ||
| emxkill.exe | %PATH% | Must be in %PATH% (required by ndc) |
| named.conf | startup directory [1] | named -c my.conf [2] |
| named.run | run direcory [3] | |
| namedb/ directory | named.conf options | |
| named.pid | %ETC% | named.conf options [2] |
| nslookup.help | %ETC% [4] | |
| resolv2 | %ETC% | |
| .nslookuprc | %HOME% | |
| named_dump.db | %TEMP% | named.conf options |
| named.stats | %TEMP% | named.conf options |
| xfer.trace | %TEMP% | |
| xfer.ddt.XXXXXX | run directory |
If you need to set a non-default root server or port number for nslookup, put SET HOME=x:\somewhere in CONFIG.SYS and create x:\somewhere\.nslookuprc with the options you want as defaults. See nslookup.help for a list of options.
If you only want to change the local domain, you can do this with the domain/search directives in %ETC%\resolv2, or by setting the environment variable LOCALDOMAIN. If none of these are found, nslookup will get the local domain from your hostname.
I can fix the second problem by faking the protection, telling BIND that the files are protected even though they are not. But I have a feeling that this would be The Wrong Thing™ to do. The warnings are legitimate. Therefore I decided to keep them. But I am open for input on this one.
The third problem is worse. I cannot fix this without editing the code or placing named.run in a fixed place. But that would have to be C:\, and after all, not even that location is guaranteed to be available.
A temporary fix would be to always start named from the database directory when you are using the debug option (-d x).
The dig ping option uses a shell command (ping -s server_name 56 3 | tail -3) to do the job. This will fail in OS/2 since ping does not have a -s option, and since most OS/2 users do not have tail installed.
I have never felt the need for the ping option, and I won't fix it unless someone asks me to. I would prefer that it was either removed or fixed by the BIND maintainers.
Please report other bugs to bjorn@mork.no
comp.protocols.tcp-ip.domains Frequently Asked Questions
[2] ndc.cmd will always look for this file in the %ETC% directory, so that's where you should put it. Unless you edit ndc.cmd to reflect your choice, of course.
[3] This will be both the startup directory during initialisation and the DB directory afterwards. I.e. if you start named with the debug flag, you will get a named.run file in two different locations. Sorry about that, but this was one of the directories that had to be fixed. And I wouldn't want to assume that a fixed location was available. After all, there are systems where you cannot write to C:\
[4] This differs from the BIND 4.9.5 port, which expected this file to be in x:\tcpip\help. I made this change because there is no simple way to detect the location of x:\tcpip. It's much simpler to use %ETC% since it will always be defined.
[5] I used a utility called PolyglotMan to do this. PolyglotMan
was a very pleasant surprise: it compiled directly on my OS/2 system, without any
changes. If you are interested, the latest version is available via anonymous
ftp from
ftp.cs.berkeley.edu
If you need a precompiled OS/2 version, ask me to
send you a copy.
Last updated
Tue May 12 1998
by Bjørn Mork