Configuration of multi-level domain names in sco unix environment (1)

SCO multi-level domain name configuration in UNIX environment (1) So far, UNIX technology is not comparable to any operating system, especially in the Internet Server field, UNIX will coexist with other operating systems for a long time; this document uses SCO Open Server 5.0.7 as an example to describe how to bind multiple IP addresses and configure multiple domain names to one network card in the same system.

Take a university campus network as an example. Assume that the server name is www, the domain name is www.gyxx.edu, And the IP address of the network adapter net0 is 201.168.0.1, And the mask is 255.255.255.0, the information department and the administration department of their respective departments use two virtual domain names: xxx.gyxx.edu (corresponding IP Address: 201.168.0.2) and jgx.gyxx.edu (corresponding IP Address: 201. 168.0.3 ).

How to bind multiple IP addresses to a network card of SCO Open Server 5.0.7

In SCO Unix, you can configure multiple NICs to obtain multiple IP addresses. If you want to bind multiple IP addresses to one Nic, its configuration is implemented through the alias address of the network interface.

The procedure is as follows:

1. Edit the/etc/tcp file. For example, vi/etc/tcp

2. Find the ifconfig command line that contains the NIC device file name net0.

3. Add the ifconfig command line after the command line to set another IP address (the second IP address and the third IP address…) for the NIC ......). If you set the 2nd IP addresses of the network adapter to 201.168.0.2 and the mask to 255.255.255.0, you can add the following line: ifconfig net0 alias 201.168.0.2 netmask 255.255.255.0 broadcast 201.168.0.255 perf 24576 24576 1; if you set 3rd IP addresses of the network adapter to 201.168.0.3 and mask to 255.255.255.0, you can add the following line: ifconfig net0 alias 201.168.0.3 netmask 255.255.255.0 broadcast 201.168.0.255 perf 24576 24576 1, and so on

4. Run the reboot command to restart the machine.

5. Run the ping command to test network connectivity.

2. DNS configuration file

The most common software for DNS is BIND (Berkeley Internet Name Domain). It provides the parser and Domain Name Server software. The parser performs the actual query and the Domain Name Server provides the response. The configuration file of BIND 4 is named. the Bind8 configuration file is named. conf (the configuration file for versions earlier than sco5.04 is named. boot, while sco5.05 and later configuration files are named. conf); BIND divides the Domain Name Server into three main types: The Primary Domain Name Server, the secondary Domain Name Server, and the cache server. The primary Domain Name Server is the most authoritative for the data it contains, it can create subdomains in sequence and assign permissions. The primary Domain Name Server is the authoritative information source for all information of one or more specific domains; the Primary Domain Name Server obtains local information from the data files related to Domain Name Information built by the system administrator. The primary Domain Name Server reads/etc/named. the conf file obtains the files in which domain name information is stored. A secondary Domain Name Server is a backup server that contains basically the same information on the Primary Domain Name Server. At a configurable interval, it updates data from the master server. The secondary Domain Name Server can choose whether to retain the original records on the local disk, which can be in the named. conf. The cache server does not store data on a local disk. All data is stored in the system cache. In a multi-user system, the cache server can accelerate domain name query. The cache server provides an informal backup method. Compared with the secondary Domain Name Server that stores data locally, the biggest advantage of this method is that when a new subdomain is added to a primary domain name server, it does not need to update data in the local DNS database.

It is commonly used to configure the master Domain Name Server. The configuration of the Primary Domain Name Server requires a complete set of files, including/etc/named. conf,/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 and other 6 files.