Configuring DNS Secondary servers: DNS series four

In the previous blog, we described how to create a common DNS record in a DNS server, and in this article we'll show you how to configure a secondary server for DNS, as well as a stub zone similar to a secondary zone.

A DNS secondary server is a fault-tolerant design, considering that once a DNS primary server fails or the load is too heavy to respond to client requests in a timely manner, the secondary server will step forward to solve problems for the primary server. The secondary server's zone data is replicated from the primary server, so the secondary server's data is read-only, and of course, if necessary, we can easily upgrade the secondary server to the primary server. We showed you how to configure a DNS secondary server through one of the following experiments, as shown in the following illustration, Ns1.hexun.com is the hexun.com primary server and ns2.hexun.com is the hexun.com secondary server.

One permission setting

If we want to configure ns2.hexun.com as a hexun.com secondary server, first we have to set permissions on the primary server ns1.hexun.com. For security reasons, the primary server does not allow any DNS servers to replicate data from its own zone, and by default only DNS servers in this zone are allowed to be secondary DNS servers. As the following illustration shows, switching to the "Zone copy" tab in the properties of the hexun.com zone, we find that the default setting is to allow zone replication, except that the hexun.com domain name server is allowed.

Switch to the Name Server tab, as shown in the following illustration, the hexun.com zone has two name servers, ns1.hexun.com and ns2.hexun.com,ns1.hexun.com are primary servers, so obviously ns2.hexun.com is getting zone To authorize a secondary server.