DNS service configuration successful

DNS service configuration is successful-Linux Enterprise Application-Linux server application information. For details, refer to the following section. (Letter/author) since learning "Linux service configuration" in advance from the last semester, the most time I spent was the configuration of the DNS service, it was not until the last day of last month (9.30 II) that I had successfully completed the DNS service test, that is, I knew the basic configurations of the DNS service.

If you have understood some basic concepts, you can successfully configure the DNS service. I think it is wrong. I knew some basic DNS concepts last semester, why does it take a month to succeed?

First of all, the biggest headache for me is the software Bind for implementing DNS services. It adopts a "jail imprisonment" installation mode, it seems that the installation directory is under "/var/named/". In fact, the first root is the virtual root, this "/" is equivalent to "/var/named/chroot/", so the real directory of Bind is under "/var/named/chroot/var/named, if you do not clarify this, the configuration file will be misplaced and cannot serve the DNS service.

Then the main configuration file "/etc/named. conf ", first: This is a symbolic link file linked to"/var/named/chroot/etc/named. conf file. Second, the options in the option command include directory "/var/named ", the Bind automatically identifies it as the actual directory of "/var/named/chroot/var/named". This is also true for other similar options.

In addition, find out a series of configuration files required for DNS service configuration. First, the main configuration file "/etc/named. conf ", which contains the path names, server version information, root region declaration, primary region, and reverse resolution regions of some required files. Second, the root server file, it is helpful to perform step-by-step queries through the root server when the Bind cannot meet client queries in the Cache. Third: the region file, the primary region declaration in the primary configuration file, is detailed in this file, such as the main configuration file to declare "tongxin.com ", the region file "tongxin.com. "zone" will write the DNS service configuration statements (such as SOA resource records and A resource records) required by the region, so that the DNS server can resolve the Domain Name of the region; Fourth: reverse parsing of the region file is similar to that of the region file, which is not described here.

The last point is what I think is worth noting. First, there must be no space at the beginning or left of each line, especially the first letter in the SOA resource record. In my opinion, this is a stumbling block for me to configure the DNS server for so long. I remember it. Second, the host name has a relative name and a complete name, for example, in the "tongxin.com" area, there is a fully-regulated domain name "squid.tongxin.com", which can be expressed by "squid" (relative name) or "squid.tongxin.com. "indicates (full name), but the".. This also made me spend a lot of time implementing the DNS service in Linux4 (minimal installation!

These understandings of the DNS service only implement the most basic DNS service configuration, and more details can make the DNS service more practical, and I cannot introduce them one by one, more time investment is needed. The description here will not at least forget the DNS service configuration process and my accumulated experience.