WO2011091646A1

WO2011091646A1 - Method, server and domain name system for realizing synchronization of the domain name system zone creation

Info

Publication number: WO2011091646A1
Application number: PCT/CN2010/074573
Authority: WO
Inventors: 毛伟; 李晓东; 王欣; 金键; 韩枫
Original assignee: 中国科学院计算机网络信息中心
Priority date: 2010-01-26
Filing date: 2010-06-28
Publication date: 2011-08-04
Also published as: CN101841409B; CN101841409A

Abstract

The present invention provides a method, primary Domain Name System(DNS) server, secondary DNS server and domain name system for realizing synchronization of the DNS zone creation, wherein the method includes: the primary DNS server creates a DNS zone and sets the dependence relationship between each DNS server in the DNS zone, and each DNS server includes a primary DNS server and at least two levels of secondary DNS servers(11); according to the dependence relationship, the primary DNS server sends to the secondary DNS servers level by level a notification message including the information of the higher-level server of the secondary DNS servers, until each secondary DNS server has recorded the information of the higher-level server which each secondary DNS server belongs to, and has obtained the zone file from each higher-level server according to the notification message(12). The defect of the prior art that when the DNS server creates a new DNS zone, the DNS administer needs to execute manual update on the zone file corresponding to the newly created DNS zone and the higher-level server information of the secondary DNS server in the secondary DNS server is changed, and thus when the DNS server creates a new DNS zone, an automatic update is realized.

Description

Method, server and domain name system for implementing synchronization of DNS zone

Technical field

The embodiments of the present invention relate to the field of domain name system technologies, and in particular, to a method for implementing synchronization creation of a DNS zone, a primary DNS server, a secondary DNS server, and a domain name system. Background technique

The Domain Name System (DNS) is a distributed database that includes domain names and Internet Protocol (IP) addresses. The DNS is stored on a DNS server distributed around the world. The DNS service packs the primary master server H (secondary server). Among them, the primary server refers to the server that stores the relevant files of the zone, and is the most fundamental source of domain information. It is the source of all secondary servers for domain transfers; the primary server reads domain data from local hard disk files. The secondary server, also known as the secondary server, is responsible for transferring all information about a zone from another server (primary or secondary) and storing the file on its local hard drive. The secondary server can also provide the necessary redundant services. At the same time, all servers (including the primary server and all secondary servers) should be listed in the name server (Name Server; hereinafter short record) of the upper-level domain.

In the prior art, when the DNS administrator independently creates a new DNS zone on the primary server, the DNS administrator can separately create the zone file corresponding to the new DNS zone on each secondary server, or by using some software tools, for example. : rdist or rsync, manually update the zone files on each secondary server to ensure that the zone files on each server in the DNS are synchronized. In the process of implementing the present invention, the inventor has found that at least the following problems exist in the prior art: In the prior art, when a new DNS zone is created for a DNS server, the DNS administrator needs to create a new DNS zone in the primary server and the secondary server respectively. The corresponding zone file is manually updated, which makes the administrator's operation relatively cumbersome. Summary of the invention

The embodiment of the present invention provides a method for synchronizing a DNS zone, a primary DNS server, a secondary DNS server, and a domain name system, which are used to solve the problem of creating a new DNS zone for a DNS server in the prior art, where the DNS administrator needs to be in the primary server and A defect in the secondary server that manually updates the zone file corresponding to the newly created DNS zone.

An embodiment of the present invention provides a method for implementing synchronization of a DNS zone, including:

The primary DNS server creates a DNS zone and sets a dependency relationship between the DNS servers in the DNS zone, where each DNS server includes a primary DNS server and at least a secondary secondary DNS server;

The primary DNS server sends a notification message including the upper-level server information of the secondary DNS server to the secondary DNS server in a stepwise manner, until the secondary DNS server records the information of the upper-level server, and according to the dependency relationship, The notification message acquires the zone file from the respective superior server.

The embodiment of the invention further provides a method for implementing synchronization of a DNS zone, including:

The secondary DNS server receives the notification message sent by the primary DNS server, where the notification message includes the upper-level server information of the secondary DNS server;

The secondary DNS server records the superior server information according to the notification message, and acquires the zone file of the DNS zone created by the primary DNS server to the upper-level server corresponding to the superior server information.

An embodiment of the present invention provides a primary DNS server, including:

Creating a DNS zone module, configured to create a DNS zone and set a dependency relationship between the DNS servers in the DNS zone, where each DNS server includes a primary DNS server and at least a secondary secondary DNS server;

The notification message sending module is connected to the created DNS zone module, and is configured to send, according to the dependency relationship, a notification message including the upper-level server information of the secondary DNS server to the secondary DNS server step by step, until each secondary DNS The server records the respective upper server information, and Obtaining a zone file from the respective upper-level servers according to the notification message.

The embodiment of the invention further provides a secondary DNS server, including:

a notification message receiving module, configured to receive a notification message sent by the primary DNS server, where the notification message includes upper server information of the secondary DNS server;

The obtaining area file module is connected to the notification message receiving module, configured to record the upper-level server information according to the notification message, and acquire the DNS created by the primary DNS server from the upper-level server corresponding to the upper-level server information District area file.

The embodiment of the present invention further provides a domain name system, including the primary DNS server described above and at least two secondary DNS servers described above.

The method for implementing synchronization of the DNS zone, the primary DNS server, the secondary DNS server, and the domain name system are implemented by the primary DNS server, and the dependencies between the DNS servers in the DNS zone are set, and according to the dependency The relationship is sent to the secondary DNS server to send a notification message including the upper-level server information of the secondary DNS server, until each secondary DNS server records the respective upper-level server information, and acquires the zone file from the respective upper-level servers according to the notification message. When the new DNS zone is created for the DNS server in the prior art, the DNS administrator needs to manually update the zone file corresponding to the newly created DNS zone and the superior server information of the secondary DNS server in the secondary server, and implements the DNS. The server automatically updates when creating a new zone, and effectively reduces the amount of labor for the administrator. DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description of the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any inventive labor.

1 is a flowchart of a method for synchronizing DNS zone creation according to Embodiment 1 of the present invention; FIG. 2 is a flowchart of a method for synchronizing DNS zone creation according to Embodiment 2 of the present invention; FIG. 3 is still another flowchart of a method for implementing synchronization of a DNS zone according to Embodiment 2 of the present invention; FIG. 4 is a schematic diagram of a tree dependency relationship between DNS servers in a DNS zone according to Embodiment 2 of the present invention;

FIG. 5 is a flowchart of a method for synchronizing DNS zone creation according to Embodiment 3 of the present invention; FIG. 6 is a flowchart of a method for synchronizing DNS zone creation according to Embodiment 4 of the present invention; FIG. 8 is another flowchart of a method for implementing synchronization of a DNS zone according to Embodiment 4 of the present invention; FIG. 9 is a flowchart of a primary DNS provided by Embodiment 5 of the present invention; Schematic diagram of the server;

10 is a schematic structural diagram of a secondary DNS server according to Embodiment 6 of the present invention;

FIG. 11 is a schematic structural diagram of a domain name system according to Embodiment 6 of the present invention. detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

Embodiment 1

FIG. 1 is a flowchart of a method for implementing synchronization of a DNS zone according to Embodiment 1 of the present invention. As shown in FIG. 1, the method includes:

Step 11. The primary DNS server creates a DNS zone and sets a dependency relationship between the DNS servers in the DNS zone. Each DNS server includes a primary DNS server and at least a secondary secondary DNS server.

Step 12: The primary DNS server sends a notification message including the upper-level server information of the secondary DNS server to the secondary DNS server according to the dependency relationship, until each secondary DNS server records the information of the upper-level server, and obtains the area from the upper-level server according to the notification message. file.

In step 12, the superior server information of the secondary DNS server is specifically the primary in the new DNS zone. DNS server, or another secondary DNS server in the new DNS zone. When the upper-level server information of the secondary DNS server is the primary DNS server, the secondary DNS server obtains the zone file from the primary DNS server according to the notification message; when the superior server information of the secondary DNS server is another secondary DNS server, the secondary DNS server according to the notification Message, get the zone file from another secondary DNS server. It is worth noting that the zone file is composed of Resource Record (hereinafter referred to as RR), and RR is the core data of DNS. In other words, the RR contains resource information of all secondary DNS servers and primary DNS servers in the DNS.

In this embodiment, the DNS zone is created by the primary DNS server, and the dependencies between the DNS servers in the DNS zone are set, and the superior server information including the secondary DNS server is sent to the secondary DNS server step by step according to the dependency relationship. The notification message is sent until the secondary DNS servers record their respective upper-level server information, and obtain the zone file from the respective upper-level servers according to the notification message. When the new DNS zone is created for the DNS server in the prior art, the DNS administrator needs to manually update the zone file corresponding to the newly created DNS zone and the superior server information of the secondary DNS server in the secondary server, and implements the DNS. The server automatically updates when creating a new zone, and effectively reduces the amount of labor for the administrator.

Embodiment 2

FIG. 2 is a flowchart of a method for implementing synchronization of a DNS zone according to Embodiment 2 of the present invention. As shown in FIG. 2, step 12 of the method includes:

Step 121: The primary DNS server sends a notification message including the information of the upper-level server of the first secondary DNS server to the first secondary DNS server according to the dependency relationship.

Step 122: When the primary DNS server receives the first feedback information of the first secondary DNS server successfully acquiring the zone file, the primary DNS server sends a notification message including the upper-level server information of the second secondary DNS server to the second secondary DNS server, where The secondary DNS server is the upper-level server of the second secondary DNS server, until each secondary DNS server records the respective superior service information, and acquires the zone file from the respective upper-level servers according to the notification message.

Further, FIG. 3 is a method for implementing synchronization of DNS zone creation according to Embodiment 2 of the present invention. In another embodiment, in the embodiment, when the primary DNS server receives the second feedback information that the first secondary DNS server fails to obtain the zone file, the specific implementation of the method is based on the foregoing embodiment. The mode is as shown in FIG. 3, and after step 121, the method further includes:

Step 123: When the primary DNS server receives the second feedback information that the first secondary DNS server does not successfully obtain the zone file, step 11 is performed.

In this embodiment, the technical solution of the present invention is described in detail in a new DNS zone, including a primary DNS server and seven secondary DNS servers. FIG. 4 is a schematic diagram of creating a DNS server in a DNS zone according to Embodiment 2 of the present invention. A schematic diagram of the tree-dependent relationship between the two, as shown in FIG. 4, the specific relationship between the primary DNS server and the secondary DNS server in the DNS zone is: The first-level server under the primary DNS server includes the first secondary DNS server and the first The second secondary DNS server, the second level server under the primary DNS server includes a second secondary DNS server and a third secondary DNS server, and the third level server under the primary DNS server includes a fourth secondary DNS server and a fifth secondary DNS server, The sixth secondary DNS server and the seventh secondary secondary server; at the same time, it can be known that the upper secondary server of the first secondary DNS server is the primary DNS server, and the second secondary DNS server has two upper-level servers, respectively, the primary DNS server and The first secondary DNS server, the upper secondary server of the third secondary DNS server is the first secondary DNS server, the fourth secondary DNS server, and the fifth secondary The upper-level server of the DNS server is the second secondary DNS server, and the upper-level server of the sixth secondary DNS server and the seventh secondary DNS server is the third secondary DNS server.

The primary DNS server first sends a notification message to the first secondary DNS server and the second secondary DNS server in the first-level server according to the tree-dependency relationship between the DNS servers in the DNS zone, where The upper server information of the first secondary DNS server sent by the DNS server (ie, the primary DNS server), and the notification message sent to the second secondary DNS server includes the upper server information of the second secondary DNS server (ie, the primary DNS server), the first The secondary DNS service and the second secondary DNS server respectively record the upper-level server information (that is, the primary DNS server information) according to the notification message, and acquire the zone file respectively from the primary DNS server corresponding to the upper-level server information.

In this embodiment, the first secondary DNS server and the secondary secondary DNS server are taken as an example. The workflow of the first secondary DNS server after receiving the notification message is as follows: If the first secondary DNS server fails to obtain the zone file, the first secondary DNS server sends the second feedback information of the zone file to the primary DNS server. According to the received second feedback information, according to the dependency relationship, the notification message is repeatedly sent to the first secondary DNS server in the first-level secondary server within a certain period of time until the first secondary DNS server successfully obtains the area of the primary DNS server. file. If the first secondary DNS server obtains the zone file successfully, sending the first feedback information of the first secondary DNS server to obtain the zone file to the primary DNS server, and the primary DNS server according to the received first feedback information, according to the dependency relationship, The second secondary DNS server and the third secondary DNS server in the second-level secondary DNS server send a notification message. When the second secondary DNS server receives the notification message, it first determines whether the acquired zone file has been stored, and if it is stored, Recording the superior server information information (ie, the first secondary DNS server information) in the current notification message, and sending the first feedback information to the primary DNS server; if there is no storage, for example, causing the second secondary DNS due to a network failure or the like If the server does not successfully obtain the zone file from the primary DNS server, the second secondary DNS server obtains the zone file from the first secondary DNS server corresponding to the upper-level server information, and if the second secondary DNS server obtains the zone file sent by the first secondary DNS server, Sending the first feedback information of the second secondary DNS server to obtain the zone file to the primary DNS server, The primary DNS server sends a notification message to the lower secondary server of the second secondary DNS server, that is, the fourth secondary DNS server and the fifth secondary DNS server according to the received first feedback information and the dependency relationship, and the fourth secondary DNS server and the fifth The workflow of obtaining the zone file by the secondary DNS server is the same as that of the second secondary DNS server, and is not described here. It is worth mentioning that the workflow of the other secondary DNS servers in the new DNS zone is the same as that of the second secondary DNS server, and details are not described herein.

In addition, the primary DNS server may further set a notification message sending list according to the dependency relationship between the DNS servers in the new DNS zone, where the notification message sending list stores information corresponding to all the secondary DNS servers in the new DNS zone. Notification message. When the primary DNS server receives the first feedback information sent by the secondary DNS server, the first feedback information may further include the secondary DNS server information, and the primary DNS server deletes the notification message sending list according to the secondary DNS server information. A notification message corresponding to the secondary DNS server information indicates that the notification message corresponding to the secondary DNS server information is successfully completed. It should be noted that a secondary DNS server may have N upper-level servers, where N is a natural number and is greater than or equal to 1, so that the secondary DNS server needs to receive N notification messages. For example, if a secondary DNS server has three upper-level servers, the primary DNS server sends three notification messages to the secondary DNS server. Each notification message carries the corresponding superior server information in the secondary DNS server, and the secondary DNS server receives the information. When the first notification message is received, the area file is obtained from the first upper-level server according to the notification message, and if the acquisition area file is successful, the first feedback information is sent to the primary DNS server; when the secondary DNS server receives the second When the notification message is sent, the secondary DNS server has acquired the zone file at this time, so only the first feedback information needs to be sent to the primary DNS server; when the secondary DNS server receives the third notification message, the principle and the received The second notification message has the same workflow. In other words, whether the secondary DNS server has several upper-level servers, as long as the successful acquisition of the zone file from a superior server is successful, when receiving the notification message of the other superior server information, it is only necessary to record the superior server information in the notification message and The primary DNS server sends the first feedback information to inform the successful acquisition of the zone file. In addition, it is worth mentioning that each time the secondary DNS server receives a notification message, it will record the superior server information in the notification message accordingly.

When the primary DNS server receives the second feedback information corresponding to the secondary DNS server that is sent by the secondary DNS server, the primary DNS server keeps the notification message sending list unchanged, and after a certain period of time, the auxiliary corresponding to the secondary DNS server information The DNS server sends a notification message.

In this embodiment, when the primary DNS server creates a new DNS zone, each secondary DNS server automatically obtains the zone file from the upper-level server of the secondary DNS server according to the received notification message, thereby effectively reducing the primary to a certain extent. The load on the DNS server reduces the administrator's work intensity.

Embodiment 3

FIG. 5 is a flowchart of a method for synchronizing DNS zone creation according to Embodiment 3 of the present invention. As shown in FIG. 5, the method includes: Step 21: The secondary DNS server receives the notification message sent by the primary DNS server, where the notification message includes the upper-level server information of the secondary DNS server.

Step 22: The secondary DNS server records the upper-level server information according to the notification message, and obtains the zone file of the DNS zone created by the primary DNS server by the upper-level server corresponding to the upper-level server information.

In step 21, the upper-level server information of the secondary DNS server is specifically the primary DNS server in the new DNS zone, or another secondary DNS server in the new DNS zone. When the upper-level server information of the secondary DNS server is the primary DNS server, the secondary DNS server records the primary DNS server information according to the notification message, and obtains the zone file from the primary DNS server; when the secondary server information of the secondary DNS server is another secondary DNS server When the secondary DNS server records another secondary DNS server information according to the notification message, and acquires the zone file from another secondary DNS server.

In this embodiment, the secondary DNS server records the upper-level server information according to the notification message sent by the primary DNS server, and obtains the area file of the DNS zone created by the primary DNS server from the upper-level server. When the new DNS zone is created for the DNS server in the prior art, the DNS administrator needs to manually update the zone file corresponding to the newly created DNS zone and the superior server information of the secondary DNS server in the secondary server, and implements the DNS. The server automatically updates when creating a new zone, and effectively reduces the amount of labor for the administrator.

Embodiment 4

FIG. 6 is a flowchart of a method for synchronizing DNS zone creation according to Embodiment 4 of the present invention. In this embodiment, after the secondary DNS server obtains the zone file, the request message sent by the subordinate server of the secondary DNS server is For example, the technical solution of the present invention is introduced in detail. As shown in FIG. 6, after step 22, the method further includes:

Step 23: The secondary DNS server receives the request message sent by the lower-level server of the secondary DNS server. Step 24: The secondary DNS server sends the area file of the DNS zone to the lower-level server according to the request message.

Further, FIG. 7 is still another flowchart of a method for implementing synchronization of a DNS zone according to Embodiment 4 of the present invention. In this embodiment, after receiving a notification message, the secondary DNS server assists The success of the DNS server is as follows. The technical solution of the present invention is described in detail. As shown in FIG. 7, after step 22, the method further includes:

Step 25: The secondary DNS server sends the first feedback information of the secondary DNS server to the primary DNS server to obtain the zone file, so that the primary DNS server sends a notification message including the secondary DNS server information to the secondary server of the secondary DNS server.

Further, FIG. 8 is another flowchart of a method for implementing synchronization of a DNS zone according to Embodiment 4 of the present invention. In this embodiment, after the secondary DNS server receives the notification message, the secondary DNS server is unsuccessful. The method of obtaining the zone file is taken as an example, and the technical solution of the present invention is introduced in detail. As shown in FIG. 8, after step 22, the method further includes:

Step 26: The secondary DNS server sends the second feedback information that the secondary DNS server does not successfully obtain the zone file to the primary DNS server, and step 21 is performed.

In this embodiment, the second secondary DNS server in the tree-dependent relationship between the DNS servers in the DNS zone is taken as an example in FIG. 4 of the second embodiment, and the technical solution of the present invention is introduced in detail. The second secondary DNS server receives the request message sent by the fourth secondary DNS server and the fifth secondary DNS server, and sends the area file of the DNS zone to the fourth secondary DNS server and the fifth secondary DNS server according to the request message, if the fourth auxiliary If the DNS server and the fifth secondary DNS server obtain the zone file successfully, the fourth secondary DNS server and the fifth secondary DNS server respectively send the first feedback information to the primary DNS server; if the fourth secondary DNS server and/or the fifth If the secondary DNS server fails to obtain the zone file successfully, the second feedback information is sent to the primary DNS server, and the primary DNS server repeatedly sends the notification message to the fourth secondary DNS server and/or the fifth secondary DNS server until the first The four secondary DNS servers and the fifth secondary DNS server succeeded in obtaining the zone file.

Embodiment 5

FIG. 9 is a schematic structural diagram of a primary DNS server according to Embodiment 5 of the present invention. As shown in FIG. 9, the primary DNS server includes: a DNS zone module 31 and a notification message sending module 32. Create a DNS zone and set the dependencies between DNS servers in the DNS zone. Each DNS server includes a primary DNS server and at least a secondary secondary DNS server. The sending module 32 is connected to the created DNS area module 31, and is configured to send, according to the dependency relationship, a notification message including the upper-level server information of the secondary DNS server to the secondary DNS server, until each secondary DNS server records the information of the upper-level server, and according to The notification message acquires the zone file from the respective superior server.

In this embodiment, the DNS zone module 31 of the primary DNS server creates a DNS zone and sets a dependency relationship between the DNS servers in the DNS zone. Each DNS server includes a primary DNS server and at least a secondary secondary DNS server, where each The secondary secondary DNS server may include multiple secondary DNS servers, and the notification message sending module 32 sends a notification message including the upper-level server information of the secondary DNS server to the secondary DNS server according to the dependency relationship until the secondary DNS servers record their respective upper-level servers. Information, and acquiring a zone file from the respective upper server according to the notification message.

In this embodiment, the DNS zone is created by the primary DNS server, and the dependencies between the DNS servers in the DNS zone are set, and the superior server information including the secondary DNS server is sent to the secondary DNS server step by step according to the dependency relationship. The notification message is up until each secondary DNS server records the respective upper-level server information, and acquires the zone file from the respective upper-level servers according to the notification message. When the new DNS zone is created for the DNS server in the prior art, the DNS administrator needs to manually update the zone file corresponding to the newly created DNS zone and the superior server information of the secondary DNS server in the secondary server, and implements the DNS. The server automatically updates when creating a new zone, and effectively reduces the amount of labor for the administrator.

Further, in order to ensure that the secondary DNS server can successfully obtain the zone file, the notification message sending module 32 of the primary DNS server further includes: a notification message sending unit 321 and a first feedback information receiving unit 322; wherein the notification message sending unit 321 and the creation The DNS area module 31 is connected to send a notification message including the upper-level server information of the first secondary DNS server to the first secondary DNS server according to the dependency relationship; the first feedback information receiving unit 322 is configured to receive the first auxiliary The DNS server successfully obtains the first feedback information of the zone file. At the same time, the notification message sending unit 321 is connected to the first feedback information receiving unit 322, and is further configured to receive the first secondary DNS server successfully by the first feedback information receiving unit 322. When obtaining the first feedback information of the zone file, the second secondary DNS service is obtained. The server sends a notification message including the upper-level server information of the second secondary DNS server, and the first secondary DNS server is the upper-level server of the second secondary DNS server.

Further, the notification message sending module 32 of the primary DNS server further includes: a second feedback information receiving unit 323, configured to receive second feedback information that the first secondary DNS server does not successfully acquire the zone file; and then notify the message sending unit 321 And being connected to the second feedback information receiving unit 323, and is further configured to repeat to the first secondary DNS server when the second feedback information receiving unit 323 receives the second feedback information that the first secondary DNS server does not successfully acquire the zone file. A notification message including the upper server information of the first secondary DNS server is sent.

Embodiment 6

10 is a schematic structural diagram of a secondary DNS server according to Embodiment 6 of the present invention. As shown in FIG. 10, the secondary DNS server includes: a notification message receiving module 41 and an acquisition area file module 42. The notification message receiving module 41 is used by Receiving the notification message sent by the primary DNS server, the notification message includes the upper-level server information of the secondary DNS server; the acquisition area file module 42 is connected to the notification message receiving module 41, and is configured to record the upper-level server information according to the notification message, and the upper-level server information The corresponding upper-level server obtains the zone file of the DNS zone created by the primary DNS server.

In this embodiment, the notification message receiving module 41 of the secondary DNS server receives the notification message sent by the primary DNS server, where the notification message includes the upper-level server information of the secondary DNS server, where the upper-level server information may specifically correspond to the primary DNS server, or Another secondary DNS server, it is worth mentioning that another secondary DNS server is the upper-level server of the secondary DNS server; the acquisition zone file module 42 obtains the zone of the DNS zone created by the primary DNS server according to the notification message to the upper-level server. File, that is, the zone file of the created DNS zone is obtained from the primary server or another secondary DNS server.

In this embodiment, the secondary DNS server records the upper-level server information according to the notification message sent by the primary DNS server, and acquires the area file of the DNS zone created by the primary DNS server by the upper-level server corresponding to the upper-level server information. When the new DNS zone is created for the DNS server in the prior art, the DNS administrator needs to manually update the zone file corresponding to the newly created DNS zone and the superior server information of the secondary DNS server in the secondary server, and implements the DNS. The server is creating a new The automatic update of the zone time, and effectively reduce the amount of labor of the administrator.

Further, in order to improve the security and reliability of the notification message carrying the configuration information between the first server and the server, the secondary DNS server may further determine the received notification message to determine whether the notification message is reliable. If reliable, according to the notification message, the upper-level server acquires the zone file; if it is not reliable, it waits to receive the notification message sent by the next primary DNS server. For example, a trusted source server list may be manually configured on each secondary DNS server. When the secondary DNS server receives the notification message, the secondary DNS server queries the trusted source server list to determine whether the server that sends the notification message includes In the list, if the server that sends the notification message is included in the list, according to the notification message, the request message is sent to the upper server to acquire the area file; if the server that sends the notification message is not in the list, In response, continue to wait for the next notification message.

Further, when the sub-server of the secondary DNS server sends a request message to obtain the area file of the secondary DNS server, the secondary DNS server further includes: a request message receiving module 43 and a zone file sending module 44; wherein the request message receiving module 43 a request message sent by the lower-level server for receiving the secondary DNS server; the zone file sending module 44 is connected to the request message receiving module 43 and the acquisition zone file module 42 for transmitting the zone file of the DNS zone to the lower-level server according to the request message. .

Further, in order to ensure that the secondary DNS server can successfully obtain the zone file of the newly created DNS zone of the upper-level server, the secondary DNS server further includes: a first feedback information sending module 45, connected to the acquisition zone file module 42, for The first feedback information of the secondary DNS server successfully acquiring the zone file is sent to the primary DNS server, so that the primary DNS server sends a notification message including the secondary DNS server information to the secondary server of the secondary DNS server.

Further, in order to ensure that the secondary DNS server can successfully obtain the zone file of the new DNS zone of the upper-level server, the secondary DNS server further includes: a second feedback information sending module 46, connected to the acquisition zone file module 44, for The second feedback information that the secondary DNS server does not successfully obtain the zone file is sent to the primary DNS server; the notification message receiving module 41 is connected to the second feedback information sending module 46, and is configured to send the second feedback information sending module 46 to the primary DNS. Server sends secondary DNS When the server does not successfully obtain the second feedback information of the zone file, the server re-receives the notification message including the upper-level server information of the secondary DNS server.

Example 7

FIG. 11 is a schematic structural diagram of a domain name system according to Embodiment 6 of the present invention. As shown in FIG. 11, the domain name system includes the primary DNS server 51 according to the fifth embodiment and the at least secondary secondary DNS described in the foregoing sixth embodiment. The server 52; wherein, the primary DNS server 51 is configured to create a DNS zone and set a dependency relationship between the DNS servers in the DNS zone, and send the superior server information including the secondary DNS server 52 to the secondary DNS server 52 step by step according to the dependency relationship. The notification message until the secondary DNS server 52 records the respective upper-level server information, and acquires the zone file from the respective upper-level servers according to the notification message; the secondary DNS server 52 receives the notification message sent by the primary DNS server 51, and the notification message includes the secondary DNS server 52. The upper-level server information is recorded; and the upper-level server information is recorded according to the notification message, and the zone file of the DNS zone created by the primary DNS server 51 is obtained by the upper-level server corresponding to the upper-level server information.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The steps of the foregoing method embodiments are included; and the foregoing storage medium includes: a medium that can store a program code, such as a ROM, a RAM, a magnetic disk, or an optical disk.

It should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art that: The technical solutions described in the foregoing embodiments are modified, or some of the technical features are equivalently replaced. The modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

Rights request

A method for implementing synchronization of a DNS zone, which is characterized by comprising:

The primary DNS server creates a DNS zone and sets a dependency relationship between the DNS servers in the DNS zone, and each of the DNS servers includes the primary DNS server and at least a secondary secondary DNS server; And sending, to the secondary DNS server, a notification message including the upper-level server information of the secondary DNS server, until each secondary DNS server records the respective upper-level server information, and acquiring the area according to the notification message to the respective upper-level server. file.

The method for implementing synchronization of a DNS zone according to claim 1, wherein the primary DNS server sends a superior server including the secondary DNS server to the secondary DNS server step by step according to the dependency relationship. Notification messages for information, including:

And sending, by the primary DNS server, a notification message including the upper-level server information of the first secondary DNS server to the first secondary DNS server according to the dependency relationship;

When the primary DNS server receives the first feedback information that the first secondary DNS server successfully acquires the zone file, the primary DNS server sends a superior of the second secondary DNS server to the second secondary DNS server. A notification message of the server information, where the first secondary DNS server is a superior server of the second secondary DNS server.

The method for implementing synchronization of a DNS zone according to claim 1, further comprising:

When the primary DNS server receives the second feedback information that the first secondary DNS server does not successfully acquire the zone file, the primary DNS server repeatedly sends the first secondary DNS server to the first secondary DNS server, including the first secondary A notification message for the superior server information of the DNS server.

4. A method for implementing synchronization of a DNS zone, which is characterized by comprising:

The secondary DNS server records the superior server information according to the notification message, and The upper-level server corresponding to the upper-level server information acquires the area file of the DNS zone created by the primary DNS server.

The method for implementing the synchronization of the DNS zone according to claim 4, wherein the secondary DNS server records the information of the upper-level server according to the notification message, and sends the information to the upper-level server corresponding to the upper-level server information. After obtaining the zone file of the DNS zone created by the primary DNS server, the method further includes:

And the secondary DNS server receives the request message sent by the lower-level server of the secondary DNS server; and the secondary DNS server sends the area file of the DNS zone to the lower-level server according to the request message.

The method for implementing synchronization of a DNS zone according to claim 4, further comprising:

Sending, by the secondary DNS server, the first feedback information that the secondary DNS server successfully obtains the area file to the primary DNS server, so that the primary DNS server sends the secondary DNS server to a lower-level server of the secondary DNS server, including the auxiliary Notification message for DNS server information.

The method for implementing the DNS zone creation synchronization according to claim 4, further comprising:

The secondary DNS server sends, to the primary DNS server, the second feedback information that the secondary DNS server does not successfully obtain the zone file, and the secondary DNS server repeatedly receives the notification of the upper-level server information including the secondary DNS server. Message.

8. A primary DNS server, comprising:

a notification message sending module, configured to be connected to the created DNS zone module, configured to send, according to the dependency relationship, a notification message including the upper-level server information of the secondary DNS server to the secondary DNS server, until each secondary DNS The server records the respective upper server information, and according to The notification message acquires a zone file from the respective superior server.

The primary DNS server according to claim 8, wherein the notification message sending module comprises:

a notification message sending unit, configured to be connected to the created DNS zone module, configured to send, to the first secondary DNS server, a notification message including the upper server information of the first secondary DNS server according to the dependency relationship;

a first feedback information receiving unit, configured to receive the first feedback information that the first secondary DNS server successfully obtains the area file;

The notification message sending unit is connected to the first feedback information receiving unit, and is further configured to receive, by the first feedback information receiving unit, the first feedback that the first secondary DNS server successfully acquires the area file. And sending, to the second secondary DNS server, a notification message including the upper-level server information of the second secondary DNS server, where the first secondary DNS server is an upper-level server of the second secondary DNS server.

The primary DNS server according to claim 9, wherein the notification message sending module further comprises:

a second feedback information receiving unit, configured to receive second feedback information that the first secondary DNS server does not successfully obtain the zone file;

The notification message sending unit is connected to the second feedback information receiving unit, and is further configured to receive, by the second feedback information receiving unit, the second feedback information that the first secondary DNS server does not successfully acquire the area file. And transmitting, to the first secondary DNS server, a notification message including the upper server information of the first secondary DNS server.

11. A secondary DNS server, comprising:

The acquiring area file module is connected to the notification message receiving module, and configured to record the upper-level server information according to the notification message, and provide the superior service corresponding to the upper-level server information The device obtains the zone file of the DNS zone created by the primary DNS server.

The secondary DNS server according to claim 11, further comprising: a request message receiving module, configured to receive a request message sent by a lower-level server of the secondary DNS server;

And a zone file sending module, configured to connect to the request message module and the acquiring zone file module, and configured to send the zone file of the DNS zone to the lower-level server according to the request message.

The secondary DNS server according to claim 11, further comprising: a first feedback information sending module, connected to the acquiring area file module, for using the main

The DNS server sends the first feedback information of the area file to the secondary DNS server, so that the primary DNS server sends a notification message including the secondary DNS server information to a lower-level server of the secondary DNS server.

The secondary DNS server according to claim 11, further comprising: a second feedback information sending module, connected to the acquiring area file module, for using the main

The second server sends the second feedback information that is not successfully obtained by the secondary DNS server; the notification message receiving module is connected to the second feedback information sending module, and is configured to send the second feedback information. When the module sends the second feedback information that the secondary DNS server fails to acquire the zone file to the primary DNS server, the module repeatedly receives the notification message including the upper-level server information of the secondary DNS server.

A domain name system, comprising: a primary DNS server according to any one of claims 8 to 10; and at least two secondary DNS servers according to any one of claims 1 to 14.