Migrate the DNS server to CentOS5

Migrate the DNS server to CentOS5-Linux Enterprise Application-Linux server application information. For more information, see. In fact, this is the second migration. The last migration may be too smooth and no logs are left. At the same time, I always wanted to back up the new server, but it was delayed. Unfortunately, the DNS server fails and cannot be started. Unfortunately, the server on which data is automatically backed up by the previous DNS also fails, so that data cannot be recovered from the backup. Fortunately, the old server has not been formatted, so you can perform another migration task. The changes made after the last migration will be lost, but at least ensure that most services can run normally. Try again tomorrow to see if the data in the new DNS server can be restored.

Because the internal DNS server does not require a lot of resources, we need to use XEN to install another virtual machine, use CentOS 5 i386, Select Server installation, and remove unnecessary services, such as file service and DHCP.

After the installation is complete, copy named. conf to the/var/named/chroot/etc directory and copy all other files to the/var/named/chroot/var/named directory. Starting named should be able to run properly theoretically. This migration method may not be clean, because the data is still in a directory in disorder, with the advantage of fast recovery and easy backup.

After the migration is completed, the following problems are encountered:

1) manually delete the named. pid file in the/var/named/chroot/var/named/directory.

2) the permissions of some files and directories need to be modified. Change the owner to named.

3) the following information is displayed in the/var/log/messages file:

Lib.tsinghua.edu.cn: 93: # springer.lib.tsinghua.edu.cn: bad owner name (check-names)

The number indicates the row number where the error occurred. It seems that the Bind VERSION does not support the # annotation, but does not affect the normal operation of the named.

4) You need to modify the firewall configuration. At the beginning, the domain name can be resolved on the local machine, but other machines cannot use it to resolve the domain name. Add the following content to/etc/sysconfig/iptables:

RH-Firewall-1-INPUT A-p udp-m udp-dport 53-j ACCEPT
RH-Firewall-1-INPUT A-p tcp-m tcp-dport 53-j ACCEPT