DNS polling via Webmin managed bind under CentOS 6.5

First, Introduction
1, Webmin
The following Webmin introduction from Baidu Encyclopedia.
Webmin is currently the most powerful Web-based UNIX system Management tool. The administrator accesses Webmin's various management functions through the browser and completes the corresponding management actions. Currently, Webmin supports the vast majority of Unix systems, including AIX, HPUX, Solaris, UnixWare, IRIX, and FreeBSD, in addition to various versions of Linux.

Webmin allows you to manage your hosts remotely using a Web interface that supports HTTPS (HTTP on SSL) protocols. This provides a simple, in-depth remote management with the assurance of security. This makes Webmin ideal for system administrators, because all major platforms have Web browsers that meet or exceed the above requirements. Furthermore, Webmin has its own "Web server", so it does not need to run third-party software (such as a Web server). Everything has. Webmin's modular architecture allows you to write your own configuration modules when you need them. In addition to the modules described here, Webmin also includes many modules. While we will focus primarily on Web services, you will see that almost every part of your system can be configured and managed through Webmin.

Webmin's official website is: http://www.webmin.com/, the latest version is 1.530.

2. BIND
Bind (Berkeley Internet Name Daemon) is the most commonly used DNS server software on the Internet today, and the DNS server that uses bind as the server software accounts for approximately 90% of all DNS servers. Bind is now being developed and maintained by the Internet Systems Association (Internet system Consortium).

Bind's official site is: Http://www.isc.org/software/bind, currently the latest version is 9.8.0.

Second, installation
1. Install bind via Yum (can also download the source package to compile itself)

1. Yum install-y bind* caching-nameserver*

2. Download and install Webmin

1. wget http://prdownloads.sourceforge.net/webadmin/webmin-1.530.tar.gz
2. Tar zxf webmin-1.530.tar.gz
3. MV Webmin-1.530/usr/local/webmin
4. Cd/usr/local/webmin
5. ./setup.sh

All the way to the default configuration, note that the last to enter the management of the account password, the default port is 10000 (and China Telecom not a half-dime relationship), after the installation of the management address is HTTP://IP: port.

Third, management
Open HTTP://IP: Port, see a landing page, enter the account number and password that you just set, see a left and right frame of the page, the left is the Management menu, the server's information on the rights side.

If you are not accustomed to English students can be in Webmin->change Language and theme switch to Simplified Chinese, but I still suggest you use English version, after all, we still deal with letters and numbers more.

Click Servers can see the current server has installed some of the services, including the "BIND DNS Server" We have just installed, we have to manage today is it, and other people to study on their own.

The first time you enter the BIND DNS server will let you set the DNS type, the first intranet with, the latter 2 is used for public network, we first select the intranet to test.

1. Establish a master zone (master zones)

The first is the domain name to resolve, the second is the host name of the machine, and the third is the mailbox.

2. Add a record
Add a few A records to the address, such as:

DNS polling is accomplished by adding several identical a records.

3. Testing
Change the DNS of this machine to the machine we used to test, such as 192.168.1.2
Open the terminal (run input cmd under windows from Start), run Nslookup www.test.com, and if you see the following output, the setting is successful.

1. Name:www.test.com
2. address:192.168.1.100
3. Name:www.test.com
4. Address:192.168.1.101
5. Name:www.test.com
6. address:192.168.1.102

Or just use ping www.test.com to see the effect, notice that Windows caches DNS results and requires "ipconfig/flushdns" to empty the DNS cache after each ping.