Redhat Enterprise Linux 6.1 (RHEL) Build ArcGIS 10.1 for server cluster (I) DNS Server SETUP

0 Preface

Starting from this article, the author will introduce how to build an ArcGIS 10.1 for server cluster in a Linux environment. Because the cluster involves Server Load balancer processing and requests need to be distributed among different machines, domain name resolution is required. In addition, machines in the cluster need to share the site configuration file and service configuration information, therefore, files must be shared between machines. This series takes into account that most gisers are not familiar with complex operations in Linux, so we will start from the initial DNS server setup and then explain how to set up the NFS file system, then the system environment check, software installation, site configuration, cluster configuration, and so on.

Thank you for your comments and comments. For more information, see the source.

1. Environment Description

The test environment includes two virtual machines, both of which are installed with Redhat Enterprise Linux 6.1.

Serial number	Machine name	IP	Domain Name	Role
1	AGS-03	192.168.1.163	GIS. esricd	Common Client
2	AGS-04	192.168.1.164	GIS. esricd	DNS Server

2 bind component Installation

In RHEL 6.1, to build a DNS server, you need to install the BIND component. First, check whether the system has installed bind by default:

The above results show that the BIND component has not been installed (for the current version and system architecture, there should be a bind-9.7.3-2.el6.x86_64 after installation ). Therefore, you must first install the BIND component. In the RHEL 6.1 ISO disc (under the packages folder), you can find bind related components, such:

Copy the above files to the specified directory (such as/usr/tmp) in the VM:

View the file information through the command line:

It is found that the execution permission has not been specified for the file. Therefore, first grant the file the permission, and grant the 777 permission directly for saving the trouble.

Then start to install the BIND component, such:

After the installation is complete, check the BIND component installation status again. The complete component is installed, as shown in (note that the first line is added after installation ):

3. modify configuration parameters 3.1 main configuration file

After the domain name resolution component is installed, the named series files will be copied to the/etc directory and the named service will be created. Related Files are shown in:

The main configuration file is the named. conf file. Open it as follows:

Here, you need to modify the query machine source and change localhost to any (or other limited IP segments) so that other client machines can use the domain name resolution service, such as (note the changes before and after the red rectangle box ):

Note that the specified information is stored in the "/etc/named. rfc1912.zones" file at the end of the file. Open the file and find that the configuration information of forward and reverse resolution is stored. Add forward and reverse resolution blocks to the end of the file as needed, for example:

The named. GIS. esricd file is specified for forward resolution, while 1.168.192.in-ADDR. Arpa is used for reverse resolution. Both files are stored in the/var/named directory, that is, the directory specified in the named. conf file.

3.2 forward parsing configuration file

Create or open the/var/named. GIS. esricd file and enter the following content:

It should be noted that you should pay attention to punctuation marks and do not enter errors. The last four lines of the file are the content to be parsed. There are only two machines here. If more machines in your environment need to be parsed, add more lines, the format is consistent with that in this document.

3.3 reverse parsing configuration file

Create or open the/var/named/named.1.168.192 file and enter the following content:

The last two lines of the file are the reverse parsing configuration. In the first example, you only need to enter the last segment of the IP address, because the prefix 192.168.1 has been specified by the configuration file.

If there are more machines that require reverse resolution, add more lines later. The format must be consistent with that in this article.

4. Client Configuration

Here the AGS-04 acts as the DNS domain name server, and also as a client machine, the AGS-03 is another client machine.

The configurations of the two client machines are basically the same. First, modify the network configuration file, which is stored in the/etc/sysconfig/network-scripts directory. For example, if the current network name is auto_eth1, then the corresponding configuration file path is:/etc/sysconfig/network-scripts/ifcfg-Auto_eth1, open the file, such:

Another configuration file/etc/resolv. conf records the DNS server and search domain, and generally does not need to be edited manually, for example (not specified yet ):

Now modify the network profile ifcfg-Auto_eth1 and add the DNS server and domain name at the end of the file, as shown below:

Here, the preferred DNS server is 192.168.1.164, and the domain name is GIS. esricd. Save the file. Now let's look at the resolv. conf file and find that its content has changed automatically:

After both client machines are configured according to the preceding steps, the client configuration is complete.

5 Resolution Test

First, start the domain name resolution service on the AGS-04 machine, such:

Then perform the forward and reverse resolution tests on the AGS-04 and AGS-03 machines, respectively. The results are as follows:

As you can see, on the AGS-03 machine, whether the machine name or the complete qualified name containing the domain name, can forward resolution successful, and enter the IP address, you can also find the corresponding complete qualified name, this indicates that reverse resolution is completely correct.

As shown above, it indicates that the DNS server is successfully built and the customer configuration is successful, and the domain name resolution service can be used normally. This article introduces how to build an NFS file sharing system.