CentOS6.2 _ 64DNSBind-9.8.2

CentOS6.2 _ 64DNSBind-9.8.2 background: JustForTest environment: Virtual Machine: VirtualBoxPC1 system: centos6.2 role DHCPHOSTNAME: dhcp. test. comIP: 192.168.1.2PC2 system: centos6.2 role: DNSHOSTNAME: dns. te... centOS 6.2 _ 64 DNS Bind-9.8.2
Background: Just For Test environment: Virtual Machine: VirtualBoxPC 1 system: centos6.2 role dhcp hostname: dhcp.test.com IP: 192.168.1.2PC 2 system: centos6.2 role dns hostname: dns.test.com IP: 192.168.1.31 install required software packages
Www.2cto.com bind-9.8.2 // bind the main file bind-libs-9.8.2 // bind the required class library bind-chroot-9.8.2 // bind the security module bind-utils-9.8.2 // bind the command package such as dig, host, nslookup, nsupdate. the easiest way to install with yum
Www.2cto.com # yum install bind-* and then view the installation result: (here I select the installation status on my machine) modify the main configuration file/etc/namd. conf is mainly used to modify the IP address range of the listener. In addition, IPV6 is included in it, and you can delete it. I will display the modified ones here. the undisplayed parts can be kept by default. Modify, named. rfc1912.zones file. here, I have deleted all the extra files. I only keep the used parts and add the region files. we can see from the main configuration file that, the directory specified by direcetory is/var/named. then we will create a region file under this directory: # vi test.com. zone result # vi 1.168.192.zone check the correctness of the configuration file # named-checkconf/etc/named. conf # named-checkzone test.com/var/named/test.com. zone # named-checkzone 1.168.192.in-addr. arpa/var/namd/1.168.192.zone enable DNS service # service named start test domain name server running status: about the configuration file location: many blogs need to put the configuration file in/var/named/chroot/var. /Named directory, but I have been tested and found that it cannot. However, it is not difficult to find that there are indeed files in this directory. well, now I am presenting images to you, and I know a strange thing: you have found a problem, when the DNS server is shut down, the/var/named/chroot/var/named directory is empty. However, once the server is running, more information is displayed in this directory, it is equivalent to completely copying all the/var/named files. However, once the service is closed, all the files are gone. isn't that strange! This is the DNS security mechanism. let's look at the bind manual the next day to find out what the problem is.