SCO openserver 5.0.5 DNS and DHCP configuration

SCO OpenServer 5.0.5 Not only has a user-friendly graphical interface, but also increases the functionality of DHCP relative to the 5.0.4 version. Now the 5.0.5 Edition already has the Web service, the FTP service, the e-mail service, the DNS, the fictitious domain name, the DHCP and so on many functions, based on it is very convenient to build an intranet platform, the following describes its DNS and DHCP configuration.

One, DNS configuration files

SCO openserver 5.0.5 DNS configuration in several cases, more commonly used is configured as a primary name server.

Configuring the primary name server requires a complete set of files, including/etc/named.boot,/etc/named.d/named.rev,/etc/named.d/named.hosts,/etc/named.d/named.local,/ Etc/named.d/named.soa,/etc/named.d/root.cache, etc. 6 documents.

After daemon named is activated, named locates and reads the/etc/named.boot file,/etc/named.boot the file named point to the DNS information source. There is a "directory" record in the/etc/named.boot file that tells named the file--root.cache referenced by named, Which directory the Named.rev,named.hosts,named.local,named.soa is located in. In SCO OpenServer 5.0.5, the directory is usually/etc/named.d, and in the/etc/named.d directory, the 5 files already exist, and users can modify them using a text editor based on the actual situation.

SCO OpenServer 5.0.5 The following steps to configure the primary name server:

1. Log into the system as root

2. Create/etc/named.boot files

This file is not present in the/ETC directory and needs to be created by the user using a text editor, which is a boot file for DNS.

3. Configure an existing/etc/named.d/named.soa file

This file is primarily configured with some SOA records, NS Records, SOA records that define the beginning of a zone's data, define parameters that affect the entire zone, and NS records flag a domain's name server.

4. Configure an existing/etc/named.d/named.hosts file

The file contains most of the domain information, which converts the hostname to an IP address, which contains a record, and may include some mx,cname and other records. In the Named.hosts file, each host in this domain should have a record of a, and there should also be a record of a localhost for this machine.

5. Configure an existing/etc/named.d/named.rev file

This file is used to find the host name by IP address. In the Named.rev file, you simply create a host part with an IP address and a record that matches the name. Typically, a PTR record is the only record in a Named.rev file.

6. Configure an existing/etc/named.d/named.local file

The named.local file is used to convert the loopback address 127.0.0.1 to the cost host name localhost, which is the file used by the reverse domain 0.0.127.in-addr.arpa. Because all systems use 127.0.0.1 as the loopback address, the Named.local file is actually the same for each system, and the file is not modified in general.

7. Configure an existing/etc/named.d/root.cache file

The cache statement in the Named.boot file points to a cache initialization file (Root.cache). Each server with a cache has one such file that contains the information needed to start constructing a domain data cache when the name server starts.

If the system is not connected to the Internet, the cache can be initialized using the primary name server information from the local network. In an intranet environment, the file is generally not changed.

8. Reboot the system

9. Check the contents of the/usr/adm/syslog file to find the configuration error.

Second, the configuration of virtual domain name

A virtual domain name is a single system (a network card) corresponding to multiple IP addresses and system names.

On the desktop, open "Internet Configuration", enter the user ID (such as: admin) and the super user password into the configuration interface, click the "Enable Virtual Domains" button, after several confirmation prompts, finally select the "Add" button, In the dialog box that opens then, enter the virtual domain name in the name bar, such as www1.jsjzx.edu, and enter the virtual IP address in the IP address bar, such as: 210.43.50.5, the system will be based on this IP address in the directory/usr/internet/ns_ HTTPd adds a subdirectory httpd-80.210.43.50.5 (this is the root directory of the Web service for that address) and creates a/usr/internet/ip/for the virtual domain name under the/USR/INTERNET/IP directory 210.43.50.5 subdirectory (which has the root directory of the FTP service for that address), enter the administrator name in the administrative user field, such as admin, and enter the administrator password in the admin User password field; re-enter Password The administrator password again, and then click the Create New Virtual Domain button.

You can then click the "Add" button again to continue adding new virtual domain names and IP addresses, such as: Www2.jsjzx2.edu and 210.43.50.6.

Now we have created two virtual domain name www1.jsjzx.edu (corresponding IP address is 210.43.50.5) and www2.jsjzx2.edu (corresponding IP address is 210.43.50.6).