The most difficult part of setting up a working SOCKS network server, is configuring the domain nameserver that the SOCKS server requires be on the same machine. For OS/2, there are two options: one commercial (IBM DNS Kit fir TCP/IP for OS/2) and one freeware (BIND 4.9.4 for OS/2 EMX port.)
Both DNS Kit and BIND can use the same configuration files, which makes my job much easier. The servers require three configuration files: NAMED.BOOT (for BIND) or NAMED.BT (for DNS Kit), NAMED.CA and NAMED.DOM. These files must be placed in a "NAMEDB" directory created off the ETC directory on the SOCKS server machine. For example, my files (see sample configuration) are:
D:\MPTN\ETC\NAMEDB\NAMED.*To create your own configuration, obtain the sample configuration files, and edit them following the instructions below. Once done, start either BIND of DNS Kit (the command is "named" in either case), and edit your ETC\RESOLV and ETC\RESOLV2 files to point to the local machine. In my case, I set up the local interface in my STARTUP.CMD file with the command:
ifconfig lo 127.0.0.1 upand then point my RESOLV file to that IP number (see RESOLV.LO in the sample configuration):
domain clt.net nameserver 127.0.0.1Once that's done, you should be able to test resolving local hostnames and, if you're connected to the internet, "real" names as well. For example:
[h:\]host deimos deimos.clt.net has address 10.10.10.120 [h:\]host www.spaz.com www.spaz.com has address 207.6.28.33 [h:\]host www.internet.ibm.com www.internet.ibm.com has address 204.146.47.106The only parts of the three files that need changing, are those that are linked. Just click on the link, and follow the instructions given. You can change other parts, but do this only if you know you need to.
The BIND documentation comes with a file that links some online DNS setup guides. In fact, that information was what I used to first setup my own DNS; I am not well versed in domain nameserver administration, so this is just a basic "here's what worked for me" guide. Corrections are welcome.
Note: Make sure that trailing periods are left in place. If they appear in the sample configuration file, leave them there!
Domain name server BOOT definition file:
==== NAMED.BOOT (BIND) or NAMED.BT (DNS Kit) ==== ; ; NAMED.BOOT/NAMED.BT file for name server configuration. ; cache . d:\\mptn\\etc\\namedb\\named.ca ; primary clt.net d:\\mptn\\etc\\namedb\\named.dom primary 0.0.127.in-addr.arpa d:\\mptn\\etc\\namedb\\named.dom ; ====Domain name server cache definition file:
==== NAMED.CA (both BIND and DNS Kit) ==== ; ; define parent(root) domain nameserver (Note trailing dot) ; clt.net. 99999999 IN NS ns01.ny.us.ibm.net. in-addr.arpa. 99999999 IN NS ns01.ny.us.ibm.net. . 99999999 IN NS ns01.ny.us.ibm.net. ; ; address of domain nameservers ; ns01.ny.us.ibm.net. 99999999 IN A 165.87.201.244 ; ====Domain name server domain definition file:
==== NAMED.DOM (Both BIND and DNS Kit) ====
;
;********************************
;* Start of Authority Records *
;********************************
;
@ IN SOA hobb.clt.net. hobb.clt.net. (
961108001 ; Serial number for this data (yymmdd##)
86400 ; Refresh value for secondary name servers
300 ; Retry value for secondary name servers
864000 ; Expire value for secondary name servers
3600 ) ; Minimum TTL value
NS hobb.clt.net.
1 PTR localhost.
;
;
; Domain Address Information
;
localhost 86400 IN A 127.0.0.1
IN HINFO loopback
;
hobb 86400 IN A 10.10.10.100
IN HINFO WarpV4
;
slug 86400 IN A 10.10.10.110
IN HINFO Linux
;
deimos 86400 IN A 10.10.10.120
IN HINFO Linux
;
max 86400 IN A 10.10.10.130
IN HINFO WinNT4
;
; more machine definitions would go here, following the format...
;
====
This is the directory where the nameserver configuration files are stored, except, "\\" is substituted for "\". This should be the NAMEDB directory created off your ETC directory. For example
D:\MPTN\ETC\NAMEDB is d:\\mptn\\etc\\namedb C:\TCPIP\ETC\NAMEDB is c:\\tcpip\\etc\\namedb
Enter the domain name of the private network.
Put in the internet name of the "real" domain name server on your ISP.
Put in the IP number of the "real" domain name server on your ISP.
Enter the private host name of the machine running the SOCKS and domain name server.
For each machine on the private network, you need to enter a three line segment. Make sure, at least, you have the server name and number defined:
machine_name 86400 IN A machine_number
IN HINFO machine_description
;
Enter the machine name here.
For each machine on the private network, you need to enter a three line segment. Make sure, at least, you have the server name and number defined:
machine_name 86400 IN A machine_number
IN HINFO machine_description
;
Enter the machine IP number associated with name "machine_name", here.
For each machine on the private network, you need to enter a three line segment. Make sure, at least, you have the server name and number defined:
machine_name 86400 IN A machine_number
IN HINFO machine_description
;
Enter a short one word description of the machine for name "machine_name", here. This is not critical, but you should put something there.
Copyright © 1996 - Falcon Networking