CN116389411B

CN116389411B - Domain name data processing method, device and equipment

Info

Publication number: CN116389411B
Application number: CN202310665370.6A
Authority: CN
Inventors: 顾武强
Original assignee: Alibaba China Co Ltd
Current assignee: Alibaba China Co Ltd
Priority date: 2023-06-07
Filing date: 2023-06-07
Publication date: 2023-08-18
Anticipated expiration: 2043-06-07
Also published as: CN116389411A

Abstract

The application provides a domain name data processing method, a device and equipment, wherein the method comprises the following steps: receiving an update notification sent by a main DNS device, wherein the update notification is used for indicating that a domain name file corresponding to a target domain name in the main DNS device is updated; according to the update notification, requesting to obtain update information corresponding to the target domain name from the main DNS equipment; and updating a domain name file corresponding to the target domain name in the DNS equipment and structured data according to the updating information, wherein the structured data comprises a plurality of domain names and domain name addresses corresponding to the domain names. The timeliness of acquiring the structured data is improved.

Description

Domain name data processing method, device and equipment

Technical Field

The present application relates to the field of computers, and in particular, to a domain name data processing method, device and equipment.

Background

A primary DNS device is included in a domain name system (Domain Name System, DNS) cluster. A plurality of domain name files may be included in the primary DNS device, and domain name resolution data may be included in the domain name files.

In the related art, a domain name file may be exported at the primary DNS device, and then domain name resolution data in the domain name file may be converted into structured data. However, in the above manner, when the domain name file is large, the export time taken is long, resulting in poor timeliness of acquiring the structured data.

Disclosure of Invention

The application provides a domain name data processing method, device and equipment, which are used for improving timeliness of obtaining structured data.

In a first aspect, an embodiment of the present application provides a domain name data processing method, applied to a DNS device of a slave domain name system, where the method includes:

receiving an update notification sent by a main DNS device, wherein the update notification is used for indicating that a domain name file corresponding to a target domain name in the main DNS device is updated;

requesting to obtain update information corresponding to the target domain name from the main DNS equipment according to the update notification;

and updating the domain name file corresponding to the target domain name in the slave DNS equipment and structured data according to the updating information, wherein the structured data comprises a plurality of domain names and domain name addresses corresponding to the domain names.

In a possible implementation manner, the main DNS device includes multiple views, where the views include domain name files corresponding to multiple domain names; the update notification comprises a first key and the target domain name; requesting to obtain update information corresponding to the target domain name from the main DNS equipment according to the update notification, wherein the update information comprises:

Obtaining a mapping relation according to the update notification, wherein the mapping relation comprises a plurality of keys and view identifications corresponding to the keys;

if the first key exists in the plurality of keys, a first view identifier is determined according to the first key and the mapping relation, and the update information is requested to be acquired from the main DNS equipment according to the first view identifier and the target domain name.

In a possible implementation manner, according to the first view identifier and the target domain name, the request for obtaining the update information from the primary DNS device includes:

determining whether a first domain name file corresponding to the target domain name exists in the slave DNS equipment according to the first view identifier and the target domain name;

if yes, requesting to acquire a target update record from the main DNS equipment, wherein the update information is the target update record;

if not, requesting to obtain a domain name file corresponding to the target domain name in a first view from the main DNS equipment, wherein the update information is the domain name file corresponding to the target domain name, and the first view corresponds to the first view identifier.

In a possible implementation manner, the update notification further includes a first update sequence number; requesting the primary DNS device to obtain a target update record, including:

Acquiring a second updated sequence number corresponding to the first domain name file;

if the second update sequence number is smaller than the first update sequence number, a first synchronization request is sent to the main DNS equipment, wherein the first synchronization request comprises the first key, the target domain name and the second update sequence number;

and receiving the target update record sent by the main DNS equipment, wherein the target update record comprises an update domain name and a domain name address corresponding to the update domain name, and the update sequence number of the update record is larger than the second update sequence number and smaller than or equal to the first update sequence number.

In a possible implementation manner, the request for obtaining, from the primary DNS device, a domain name file corresponding to the target domain name in the first view includes:

sending a second synchronization request to the main DNS equipment, wherein the second synchronization request comprises the first key and the target domain name;

and receiving a domain name file corresponding to the target domain name in the first view sent by the main DNS equipment.

In a possible implementation manner, the mapping relationship further includes an access line corresponding to the view identifier; updating the structured data in the slave DNS device according to the update information, including:

Determining a first access line according to the first view identifier and the mapping relation;

and updating the structured data according to the updating information and the first access line, wherein the structured data comprises the corresponding relation among the domain name, the access line and the domain name address.

In one possible implementation, updating the structured data according to the update information and the first access line includes:

determining an updated domain name, an updated domain name address corresponding to the updated domain name and an updated type according to the updated information, wherein the updated type is an added type, a deleted type or a modified type;

determining a first structured record according to the updated domain name, the updated domain name address and the access line;

and updating the structured data according to the update type and the first structured record.

In one possible implementation, updating the structured data according to the update type and the first structured record includes:

if the update type is the add type, the first structured record is newly added in the structured data;

if the update type is the deletion type, deleting the first structured record in the structured data;

And if the update type is the modification type, updating the domain name address corresponding to the updated domain name and the access line in the structured data into the updated domain name address.

In a second aspect, an embodiment of the present application provides a domain name data processing method, applied to a primary DNS device, where the method includes:

sending an update notification to a slave DNS device, wherein the update notification is used for indicating that a domain name file corresponding to a target domain name in the master DNS device is updated;

receiving a synchronization request corresponding to the target domain name sent by the DNS equipment;

and according to the synchronous request, sending update information corresponding to the target domain name to the slave DNS equipment, wherein the update information is used for updating a domain name file corresponding to the target domain name and structured data by the slave DNS equipment.

In a possible implementation manner, the main DNS device includes multiple views, where the views include domain name files corresponding to multiple domain names; the synchronization request comprises a first key, a target domain name and a second updating sequence number;

according to the synchronization request, sending update information corresponding to the target domain name to the slave DNS equipment, wherein the update information comprises:

Determining an update record file according to the first key and the target domain name in the synchronous request, wherein the update record file comprises a plurality of update records and update sequence numbers corresponding to the update records, and the update records comprise update domain names and domain name addresses corresponding to the update domain names;

determining a target update record in the update record file according to the second update sequence number, wherein the update sequence number of the target update record is larger than the second update sequence number;

and sending the target update record to the slave DNS equipment, wherein the update information is the target update record.

In one possible implementation, the primary DNS device includes multiple views therein; the synchronization request includes a first key and a target domain name; according to the synchronization request, sending update information corresponding to the target domain name to the slave DNS equipment, wherein the update information comprises:

determining a domain name file corresponding to the target domain name in a first view according to the first key and the target domain name in the synchronous request;

and sending a domain name file corresponding to the target domain name in the first view to the slave DNS equipment, wherein the updating information is the domain name file.

In a third aspect, an embodiment of the present application provides a domain name data processing apparatus, applied to a DNS device of a slave domain name system, the apparatus including: the device comprises a first receiving module, an acquisition module and an updating module, wherein,

the first receiving module is used for receiving an update notification sent by a main DNS device, wherein the update notification is used for indicating that a domain name file corresponding to a target domain name in the main DNS device is updated;

the acquisition module is used for requesting the main DNS equipment to acquire the update information corresponding to the target domain name according to the update notification;

the updating module is used for updating the domain name file corresponding to the target domain name in the slave DNS equipment and the structured data according to the updating information, wherein the structured data comprises a plurality of domain names and domain name addresses corresponding to the domain names.

In a possible implementation manner, the main DNS device includes multiple views, where the views include domain name files corresponding to multiple domain names; the update notification comprises a first key and the target domain name; the acquisition module is specifically configured to:

In one possible implementation manner, the acquiring module is specifically configured to:

In a possible implementation manner, the update notification further includes a first update sequence number; the acquisition module is specifically configured to:

In a possible implementation manner, the mapping relationship further includes an access line corresponding to the view identifier; the updating module is specifically configured to:

In a possible implementation manner, the updating module is specifically configured to:

In a fourth aspect, an embodiment of the present application provides a domain name data processing apparatus, applied to a primary DNS device, where the apparatus includes: a first transmitting module, a second receiving module and a second transmitting module, wherein,

The first sending module is used for sending an update notification to the slave DNS equipment, wherein the update notification is used for indicating that a domain name file corresponding to a target domain name in the master DNS equipment is updated;

the second receiving module is used for receiving the synchronous request corresponding to the target domain name sent by the DNS equipment;

the second sending module is configured to send, according to the synchronization request, update information corresponding to the target domain name to the slave DNS device, where the update information is used for updating, by the slave DNS device, a domain name file corresponding to the target domain name and structured data.

In a possible implementation manner, the main DNS device includes multiple views, where the views include domain name files corresponding to multiple domain names; the synchronization request comprises a first key, a target domain name and a second updating sequence number; the second sending module is specifically configured to:

In one possible implementation, the primary DNS device includes multiple views therein; the synchronization request includes a first key and a target domain name; the second sending module is specifically configured to:

In a fifth aspect, an embodiment of the present application provides a slave DNS device, including: a memory and a processor;

the memory stores computer-executable instructions;

the processor executing computer-executable instructions stored in the memory, causing the processor to perform the domain name data processing method according to any one of the first aspects.

In a sixth aspect, an embodiment of the present application provides a primary DNS device, including: a memory and a processor;

The memory stores computer-executable instructions;

the processor executing computer-executable instructions stored in the memory, causing the processor to perform the domain name data processing method of any of the second aspects.

In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium having stored therein computer-executable instructions for implementing the domain name data processing method of any one of the first aspects when the computer-executable instructions are executed by a processor.

In an eighth aspect, embodiments of the present application provide a computer-readable storage medium having stored therein computer-executable instructions for implementing the domain name data processing method of any one of the second aspects when the computer-executable instructions are executed by a processor.

In a ninth aspect, an embodiment of the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the domain name data processing method of any of the first aspects.

In a tenth aspect, embodiments of the present application provide a computer program product comprising a computer program which when executed by a processor implements the domain name data processing method of any of the second aspects.

The embodiment of the application provides a domain name data processing method, a device and equipment, wherein a slave DNS equipment can receive an update notification sent by a master DNS equipment and send a synchronous request to the master DNS equipment according to the update notification so as to request to acquire update information corresponding to a target domain name. The master DNS device may send update information corresponding to the target domain name to the slave DNS device according to the synchronization request. The slave DNS device may update, according to the update information, a domain name file corresponding to the target domain name in the slave DNS device, and the structured data. The slave DNS equipment can synchronize the updated information in the master DNS equipment in real time so as to keep the consistency of the domain name file in the slave DNS equipment and the domain name file in the master DNS equipment; and the structured data can be generated from the DNS equipment according to the domain name file, and can be updated in real time according to the update information, so that the timeliness of acquiring the structured data is improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:

fig. 1 is a schematic diagram of providing a domain name file in a primary DNS device according to an exemplary embodiment of the present application;

FIG. 2 is a schematic view of a scenario provided by an exemplary embodiment of the present application;

fig. 3 is a flow chart of a domain name data processing method according to an exemplary embodiment of the present application;

FIG. 4 is a flowchart of another domain name data processing method according to an exemplary embodiment of the present application;

fig. 5 is a schematic process diagram of a domain name data processing method according to an exemplary embodiment of the present application;

FIG. 6 is a schematic diagram of a page displaying structured data according to an exemplary embodiment of the present application;

FIG. 7 is a schematic diagram of an aggregate optimized page provided by an exemplary embodiment of the present application;

fig. 8 is a schematic structural diagram of a domain name data processing device according to an exemplary embodiment of the present application;

fig. 9 is a schematic structural diagram of another domain name data processing apparatus according to an exemplary embodiment of the present application;

fig. 10 is a schematic structural diagram of a slave DNS device according to an exemplary embodiment of the present application;

fig. 11 is a schematic structural diagram of a primary DNS device according to an exemplary embodiment of the present application.

Detailed Description

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with related laws and regulations and standards, and provide corresponding operation entries for the user to select authorization or rejection.

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

In order to facilitate understanding of the technical solution of the present application, the description of the domain name file in the primary DNS device is first described with reference to fig. 1.

Fig. 1 is a schematic diagram of providing a domain name file in a primary DNS device according to an exemplary embodiment of the present application. Referring to fig. 1, a plurality of views may be provided in a primary DNS device. For example, 3 views, view 1, view 2, and view 3, respectively, may be included in the primary DNS device.

For any view, the view may include a key, a plurality of domain names, and domain name files corresponding to the plurality of domain names, respectively. For example, key 1, domain name dnstest1.Com, and corresponding domain name file 1 and domain name dnstest2.Com, and corresponding domain name file 2 may be included in view 1.

For any one domain name, the domain name may correspond to multiple domain name files under different views. For example, for a domain name dnstest1.Com, the domain name may correspond to 3 domain name files, namely, domain name file 1, domain name file 3, and domain name file 5, with domain name file 1 in view 1, domain name file 3 in view 2, and domain name file 5 in view 3.

For any one domain name file, the domain name file may include domain name resolution data such as a Time To Live (TTL) duration corresponding To the domain name file, a sequence number, a sub-domain name prefix corresponding To the domain name, a record type, and a domain name address corresponding To the sub-domain name.

For example, if the domain name 1 is dnstest1.Com, the domain name file 1 may include TTL of 600 seconds(s), serial number 008, corresponding subdomain name prefix rr01, record type a, and the domain name address corresponding to the subdomain name includes 1.1.1.1 and 2.2.2.2. Wherein record type a represents an internet protocol version 4 (Internet Protocol version, IPv 4) address resolution record, i.e., domain name to IPv4 address mapping. Since the domain name 1 is dnstest1.Com and the sub-domain name prefix is rr01, it is possible to determine that the sub-domain name is rr01.Dnstest1.Com from the domain name 1 and the sub-domain name prefix.

The primary DNS device may include an updated record file corresponding to each domain name file. The update record file may include update records for adding, deleting and modifying the domain name file, and an update sequence number corresponding to each update record. The master DNS device may operate on the corresponding domain name file to update the domain name file at regular time according to the update record in the update record file.

For example, the domain name file 1 may correspond to the update record file 1, and the update record file 1 may include the update record 1 and the corresponding update sequence number 009, the update record 2 and the corresponding update sequence number 010. Assume that update record 1 is to add rr01, record type a, domain name address 1.1.1.2 in domain name file 1; update record 2 is deleting rr01, record type a and domain name address 1.1.1 in domain name file 1, then the master DNS device may add "rr01, record type a and domain name address 1.1.2" in domain name file 1 according to update record 1 in update record file 1, and update the sequence number in domain name file 1 to 009 according to update sequence number 009; it is possible to delete "rr01, record type a, domain name address 1.1.1" in the domain name file 1 based on the update record 2 in the update record file 1, and update the sequence number in the domain name file 1 to 010 based on the update sequence number 010.

It should be noted that, when the update record file corresponding to the domain name file exists in the main DNS device, it indicates that the domain name file is updated, including that the domain name file may be updated according to the update record file, or that the domain name file may be updated according to the update record file.

For example, if the update period is 10min, the last update time is 15:00, the next update time is 15:10, if the domain name file 1 corresponds to the update record file 1, the update record file 1 includes the update record 1 generated by 15:05 and the corresponding update serial number is 009, if the serial number in the domain name file 1 is 008, the current time is 15:08, and since the next update time is not 15:10 yet, the domain name file 1 is updated according to the update record file 1; if the serial number in the domain name file 1 is 009, the current time is 15:11, and since the next update time is 15:10, it is indicated that the domain name file has been updated according to the update record.

Fig. 2 is a schematic view of a scenario provided in an exemplary embodiment of the present application. Referring to fig. 2, a master DNS device and a slave DNS device are included.

The main DNS device may include a domain name file and an update record file corresponding to the domain name file, where the update record file may include a plurality of update records, and the domain name file may be modified according to the update record file. For example, if the domain name file is the domain name file 1, the update record file 1 may include the update record 1, and the update record 1 may be a new domain name address 1 added to the domain name file 1, then the domain name address 1 may be newly added to the domain name file 1 according to the update record 1.

When the master DNS device has an update record file, the master DNS device may send an update notification to the slave DNS device to cause the slave DNS device to request the master DNS device to obtain update information.

Domain name files and structured data may be included from the DNS device. After the update information is obtained from the DNS device, the domain name file may be updated according to the update information, and the structured data may be updated. The structured data may be a domain name resolution data table generated from domain name resolution data in a domain name file.

In the embodiment of the application, the slave DNS equipment can be arranged, and the slave DNS equipment can synchronize the updated information in the master DNS equipment in real time so as to keep the consistency of the domain name file in the slave DNS equipment and the domain name file in the master DNS equipment; and the slave DNS equipment can generate the structured data according to the domain name file in real time, and the slave DNS equipment can generate the structured data according to the domain name file, and can update the structured data according to the update information in real time, so that the timeliness of acquiring the structured data is improved.

The technical scheme shown in the application is described in detail by specific examples. It should be noted that the following embodiments may exist alone or in combination with each other, and for the same or similar content, the description will not be repeated in different embodiments.

Fig. 3 is a flowchart of a domain name data processing method according to an exemplary embodiment of the present application. Referring to fig. 3, the method may include:

s301, the master DNS equipment sends an update notification to the slave DNS equipment.

The master DNS device and the slave DNS device may be located in one DNS cluster. The master DNS device and the slave DNS device may communicate with each other.

The main DNS device may include a target domain name, a domain name file corresponding to the target domain name, and an update record file corresponding to the domain name file. For example, if the target domain name is dnstest1.Com, the domain name 1 may have 3 domain name files corresponding to each of the 3 domain name files, namely, the domain name file 1, the domain name file 3, and the domain name file 5, and the 3 domain name files may have corresponding updated record files.

Optionally, the update record file may include an update record for the domain name file, and an update sequence number corresponding to each update record.

For example, if the target domain name is dnstest1.Com, there is a corresponding domain name file 1, the domain name file 1 has a corresponding update record file 1, and the update record file 1 may include an update record 1 and a corresponding update sequence number 009 for the domain name file 1, and an update record 2 and a corresponding update sequence number 010 for the domain name file 1.

The update notification may be used to indicate that the domain name file in the primary DNS device corresponding to the target domain name is updated. The update notification may include the target domain name, the first key, and the first update sequence number.

The first key may be a key in a first view in which the updated domain name file is located. For example, if the target domain name is dnstest1.Com, the domain name file in which the update occurs is domain name file 1, and the domain name file 1 is located in view 1, the first key is key 1 in view 1, and it is assumed that the first key may be a001.

The first update sequence number may be the largest update sequence number in the update record file corresponding to the domain name file in which the update occurs. For example, if the domain name file in which the update has occurred is domain name file 1, and update record file 1 is associated, update record file 1 includes update sequence number 009 and update sequence number 010, the first update sequence number is 010.

For example, if the target domain name is dnstest1.Com, the occurrence update domain name file corresponding to the target domain name is domain name file 1, the update record file 1 corresponding to the domain name file 1 includes the update record for the domain name file 1, and the largest update sequence number is 010, the domain name file 1 is located in view 1, and the key 1 in view 1 is a001, the update notification 1 may include the target domain name dnstest1.Com, the first key a001, and the first update sequence number 010.

Alternatively, when the domain name file corresponding to the target domain name in the master DNS device is updated, the master DNS device may send an update notification to the slave DNS device. For example, if the target domain name is dnstest1.Com, the target domain name corresponds to domain name file 1, and the update record file 1 includes an update record for the domain name file 1, that is, indicates that the domain name file 1 is updated, the master DNS device may send an update notification 1 to the slave DNS device, and it is assumed that the update notification 1 may include the target domain name dnstest1.Com, the first key a001, and the first update sequence number 010.

S302, the slave DNS equipment sends a synchronous request to the master DNS equipment according to the update notification.

In an alternative embodiment, a synchronization request may be sent to the primary DNS device according to the update notification to request to obtain update information corresponding to the target domain name in the following manner: acquiring a mapping relation according to the update notification; if the first key exists in the plurality of keys, determining a first view identifier according to the first key and the mapping relation, and requesting to acquire update information from the main DNS equipment according to the first view identifier and the target domain name.

Optionally, the update information may be a target update record in the update record file, or may be a domain name file corresponding to the target domain name. For example, if the target domain name is dnstest1.Com, and there is a corresponding domain name file 1, and the update record file 1 corresponding to the domain name file 1 includes an update record 1 and an update record 2 for the domain name file 1, the update information may include the update record 1 and the update record 2; if the update record file 1 does not exist, the update information may be the domain name file 1 corresponding to the target domain name dnstest1. Com.

The mapping relationship may include a plurality of keys and view identifiers corresponding to the keys, and may further include an access line (linecode) corresponding to the view identifiers.

For example, the mapping relationship may be as shown in table 1:

TABLE 1

Alternatively, the mapping relationship may be stored in the slave DNS device or in the first device. After the update notification may be received from the DNS device, the mapping relationship may be obtained from the DNS device or the first device according to the update notification.

Since the first key is included in the update notification and the plurality of keys are included in the mapping relationship, it can be determined whether the first key exists among the plurality of keys. If the first key exists, the update notification is not tampered, and if the update notification is verified to be legal, the first view identifier can be determined in the mapping relation according to the first key. For example, if the key 1 in the mapping relationship is a001 and the first key is a001, it may be determined that the first key exists in the mapping relationship, and the corresponding first view identifier may be determined as the view identifier 1 in the mapping relationship according to the first key.

Optionally, after the DNS determines the first view identifier, determining, according to the first view identifier and the target domain name, whether a first domain name file corresponding to the target domain name exists in the DNS device. If the first domain name file exists, the slave DNS equipment can send a synchronous request to the master DNS equipment to request updating information, and the updating information can be a target updating record corresponding to the first domain name file; if the domain name file does not exist, the slave DNS equipment can send a synchronous request to the master DNS equipment to request updating information, and the updating information can be a domain name file corresponding to the target domain name.

At the DNS slaves, the target domain name may correspond to multiple domain name files under different views. The first domain name file may be any one of the plurality of domain name files.

For example, if the first view identifier is view identifier 1 and the target domain name is dnstest1.Com, if the slave DNS device determines that, according to view identifier 1 and target domain name dnstest1.Com, there is a domain name file 1 corresponding to the target domain name dnstest1.Com in the view corresponding to view identifier 1, then a synchronization request 1 may be sent to the master DNS device to request a target update record of domain name file 1; if the first domain name file does not exist, a synchronization request 2 may be sent to the master DNS device to request a domain name file corresponding to the target domain name dnstest1.Com, that is, domain name file 1.

S303, the master DNS equipment sends update information corresponding to the target domain name to the slave DNS equipment according to the synchronous request.

For example, if the master DNS device receives the synchronization request 1, where the synchronization request 1 is used to request a target update record of the domain name file 1 corresponding to the target domain name dnstest1.Com, the master DNS device may determine, according to the synchronization request 1, a multi-entry target update record of the domain name file 1 corresponding to the target domain name dnstest1.Com in the master DNS device, and send update information 1 to the slave DNS device, where the update information 1 includes the multi-entry target update record.

For example, if the master DNS device receives the synchronization request 2, where the synchronization request 2 is used to request the domain name file 1 corresponding to the target domain name dnstest1.Com, the master DNS device may determine, in the master DNS device, the domain name file 1 corresponding to the target domain name dnstest1.Com according to the synchronization request 2, send update information 2 to the slave DNS device, where the update information 2 includes the domain name file 1 corresponding to the target domain name dnstest1. Com.

S304, the slave DNS equipment updates the domain name file corresponding to the target domain name in the slave DNS equipment and the structured data according to the update information.

Alternatively, the slave DNS device may include a domain name file and structured data, and the update information may be used to update the domain name file corresponding to the target domain name, and the structured data from the DNS device.

Multiple views can be included in the DNS device, and each view can include a key, multiple domain names, and domain name files respectively corresponding to the multiple domain names. The view from the DNS device, and the key, the plurality of domain names, and the domain name file respectively corresponding to the plurality of domain names included in the view may be consistent with the maintenance in the master DNS device. For example, 3 views, view 1, view 2 and view 3, respectively, may also be included from the DNS device. Wherein, the key 1, the domain name dnstest1.Com, and the corresponding domain name file 1 and the domain name dnstest2.Com, and the corresponding domain name file 2 may be included in the view 1.

For any one of the domain name files, the domain name file may include a plurality of resolution data therein. For example, in the slave DNS device, the target domain name dnstest1.Com may correspond to the domain name file 1 in fig. 1, where the domain name file 1 may include domain name resolution data such as TTL 600 seconds(s), serial number 008, corresponding sub domain name prefix rr01, record type a, and the domain name address corresponding to the sub domain name includes 1.1.1.1 and 2.2.2.2.

The structured data may be an resolution data table generated according to domain name resolution data in a domain name file, and the structured data may include a correspondence between a domain name, an access line, and a domain name address. The domain name may include a target domain name and a subdomain name.

For example, the structured data may be as shown in table 2:

TABLE 2

Alternatively, the access lines may be divided according to regions. For example, the access line 1 may be a domestic line, which may be denoted by "CN".

A plurality of structured records may be included as in table 2. For example, the target domain name dnstest1.Com, the subdomain name rr01.Dnstest1.Com, the line 1, and the domain name address 1.1.1.1.1 may be included in the structured record 1.

It should be noted that, since the correspondence between the view identifier and the line included in the mapping relationship is shown in table 1, in table 2, 2 structured records including the line 1 are generated according to the domain name file 1 corresponding to the target domain name dnstest1.Com in the view 1 corresponding to the view identifier 1; the structured record comprising the line 2 is generated according to a domain name file 3 corresponding to a target domain name dnstest1.Com in a view 2 corresponding to the view identifier 2; the structured record including line 3 is generated from the domain name file 5 corresponding to the target domain name dnstest1.Com in view 3 corresponding to view identifier 3.

Optionally, if the update information includes a domain name file corresponding to the target domain name, after receiving the update information from the DNS device, the domain name file corresponding to the target domain name may be stored in the view corresponding to the first view identifier; if the update information includes the target update record, the slave DNS device may update the first domain name file according to the target update record.

For example, if the first view identifier is view identifier 1, and the update information includes domain name file 1, the DNS device may store the domain name file 1 in view 1 corresponding to view identifier 1; if the first domain name file is domain name file 1 corresponding to the target domain name dnstest1.Com, and the update information includes target update record 1, and the target update record 1 is that rr01, record type a, and domain name address 1.1.1.2 are added to the domain name file 1, then "rr01, record type a, and domain name address 1.1.1.2" may be added to the domain name file 1 corresponding to the target domain name dnstest1.Com from the DNS device according to the update record 1.

Alternatively, the slave DNS device may determine the first access line according to the first view identifier and the mapping relationship, and update the structured data according to the update information and the first access line.

For example, if the structured data is shown in table 2, the first view identifier is view identifier 1, the mapping relationship is shown in table 1, then the slave DNS device may determine that the first access line is line 1 according to the view identifier 1, if the update information includes the target update record 1, the target update record 1 is that rr01, record type a, and domain name address 1.1.1.2 are added in the domain name file 1, then the slave DNS device may add the structured record 1 in the structured data according to the update record 1, and the structured record 1 may include the target domain name dnstest1.com, the subdomain name rr01.Dnstest1.com, the line 1, and the domain name address 1.1.1.2 as shown in table 3:

TABLE 3 Table 3

If the structured data is shown in table 3, the structured data is a line corresponding to the view identifier, and a plurality of structured records are stored. The structured records in table 3 that include multiple lines, i.e., domain name resolution data in multiple under-view domain name files. When managing the domain name resolution data corresponding to the target domain name, the management can be performed uniformly in table 3, and the domain name resolution data in the plurality of domain name files are managed without determining the plurality of domain name files corresponding to the target domain name in different views.

In the embodiment of the application, the master DNS device can send an update notification to the slave DNS device, and the slave DNS device can send a synchronization request to the master DNS device according to the update notification. The master DNS device may send update information corresponding to the target domain name to the slave DNS device according to the synchronization request, and the slave DNS device updates a domain name file corresponding to the target domain name in the slave DNS device and the structured data according to the update information. The slave DNS equipment can synchronize the updated information in the master DNS equipment in real time so as to keep the consistency of the domain name file in the slave DNS equipment and the domain name file in the master DNS equipment; and the structured data can be generated from the DNS equipment according to the domain name file, and can be updated in real time according to the update information, so that the timeliness of acquiring the structured data is improved.

The domain name data processing method described above will be described in detail with reference to fig. 4, based on the embodiment shown in fig. 3.

Fig. 4 is a flowchart of another domain name data processing method according to an exemplary embodiment of the present application. Referring to fig. 4, the method includes:

s401, the master DNS equipment sends an update notification to the slave DNS equipment.

It should be noted that, the execution of step S401 may refer to the execution of step S301, and will not be described herein.

S402, acquiring a mapping relation from the DNS equipment according to the update notification, wherein the mapping relation comprises a plurality of keys.

Alternatively, the mapping relationship may be stored in the slave DNS device or in the first device.

After the update notification may be received from the DNS device, the mapping relationship may be obtained from the DNS device or the first device according to the update notification. The mapping relationship includes a plurality of keys and view identifications corresponding to the keys, as shown in table 1.

S403, if a first key exists in the plurality of keys, determining a first view identifier from the DNS equipment according to the first key and the mapping relation.

Since the first key is included in the update notification and the plurality of keys are included in the mapping relationship, it can be determined whether the first key exists among the plurality of keys. If the first key exists, the update notification is not tampered, and if the update notification is verified to be legal, the first view identifier can be determined in the mapping relation according to the first key.

For example, if the first key is a001 and the key 1 in the mapping relationship is a001, it may be determined that the first key exists in the mapping relationship, and the corresponding first view identifier may be determined as the view identifier 1 in the mapping relationship according to the first key.

S404, determining whether a first domain name file corresponding to the target domain name exists or not according to the first view identifier and the target domain name from the DNS equipment.

Optionally, the slave DNS device may determine, according to the first view identifier, a corresponding view, and determine whether a first domain name file corresponding to the target domain name exists in the view. If so, S405 may be performed; if not, S406 may be performed.

For example, if the target domain name is dnstest1.Com, the first view identifier is view identifier 1, and view identifier 1 corresponds to view 1 in the slave DNS device, it may be determined in view 1 whether there is a domain name file 1 corresponding to the target domain name dnstest1. Com. If there is a domain name file 1 corresponding to the target domain name dnstest1.Com in view 1, S405 may be performed; if the domain name file 1 corresponding to the target domain name dnstest1.Com does not exist in view 1, S406 may be performed.

S405, the slave DNS equipment sends a first synchronization request to the master DNS equipment.

In an alternative embodiment, a first synchronization request is sent to the primary DNS device to request acquisition of a target update record based on the first view identification and the target domain name: acquiring a second updated serial number corresponding to the first domain name file; and if the second updated sequence number is smaller than the first updated sequence number, sending a first synchronization request to the main DNS equipment.

The first domain name file may include a second updated sequence number therein, which may be determined from the DNS device in the first domain name file. For example, the second update sequence number may be 008.

Because the update notification includes the first update sequence number, if the first domain name file in the slave DNS device has the corresponding second update sequence number, if the second update sequence number is smaller than the first update sequence number, a first synchronization request may be sent to the master DNS device to request to obtain the target update record, where the update information is the target update record.

The first synchronization request may include the first key, the target domain name, and the second updated sequence number.

For example, if the update notification includes the first update sequence number 010 and the second update sequence number 008, since the second update sequence number 008 is smaller than the first update sequence number 010, the slave DNS device may send the first synchronization request 1 to the master DNS device to request the update information 1. The first synchronization request 1 may include the first key a001, the target domain name dnstest1.Com, and the second update sequence number 008. Update information 1 may include update record 1 corresponding to update sequence number 009, and update record 2 corresponding to update sequence number 010.

S406, the master DNS equipment sends a second synchronization request to the master DNS equipment.

Because the first domain name file corresponding to the target domain name does not exist in the slave DNS device, the master DNS device may send a second synchronization request to the master DNS device to request to acquire the first domain name file corresponding to the target domain name in the first view.

Since the first domain name file does not exist, and therefore, the second update sequence number corresponding to the first domain name file does not exist, the second synchronization request may include the first key and the target domain name. For example, the first key a001 and the target domain name dnstest1.Com may be included in the second synchronization request.

S407, the master DNS equipment sends update information corresponding to the target domain name to the slave DNS equipment according to the first synchronous request or the second synchronous request.

In an alternative embodiment, since the first synchronization request includes the first key, the target domain name, and the second update sequence number, the update record file may be determined according to the first key and the target domain name in the first synchronization request; determining a target update record in the update record file according to the second update sequence number; and sending the target update record to the slave DNS equipment, wherein the update information is the target update record.

The update record file may include a plurality of update records and update sequence numbers corresponding to the update records. For example, update record 1 and corresponding update sequence 009, and update record 2 and corresponding update sequence number 010, may be included in update record file 1.

For any update record, the update record may include an update domain name and a domain name address corresponding to the update domain name. For example, update record 1 may include update domain name rr01. Dnstest1.Com, with a corresponding domain name address of 1.1.1.0.

The update sequence number of the target update record may be greater than the second update sequence number. For example, if the second update sequence number is 008, it is possible to determine that update record 1 corresponding to update sequence number 009 and update record 2 corresponding to update sequence number 010 are target update records.

For example, if the first synchronization request includes the first key as key 1, the target domain name as dnstest1.Com, and the second update sequence number as 008, if the file in the master DNS device is as shown in fig. 1, the master DNS device may determine the domain name file 1 according to the key 1 and the target domain name 1, and further determine the update record file 1. If the update record file 1 includes the update record 1 and the corresponding update sequence 009, and the update record 2 and the corresponding update sequence number 010, the master DNS device may determine, in the update record file 1, the update record 1 corresponding to the update sequence number 009, and the update record 2 corresponding to the update sequence number 010 as target update records according to the second update sequence number 008. The master DNS device may send update information corresponding to the target domain name to the slave DNS device, where the update information includes 2-entry target update records, i.e., update record 1 and update record 2.

In an optional embodiment, since the second synchronization request includes the first key and the target domain name, a domain name file corresponding to the target domain name in the first view may be determined according to the first key and the target domain name in the second synchronization request; and sending a domain name file corresponding to the target domain name in the first view to the slave DNS equipment, and updating information into the domain name file.

For example, if the first key is key 2 and the target domain name is dnstest1.Com are included in the second synchronization request, and if the file in the primary DNS device is as shown in fig. 1, the primary DNS device may determine the domain name file 3 in view 2 according to the key 2 and the target domain name dnstest1. Com. The master DNS device may send update information corresponding to the target domain name to the slave DNS device, where the update information includes the domain name file 3.

S408, the slave DNS equipment updates the domain name file corresponding to the target domain name in the slave DNS equipment according to the update information.

If the update information includes the target update record, the slave DNS device may update, according to the update information, a domain name file corresponding to the target domain name, that is, the first domain name file. For example, if the target update record 1 is to add rr01, record type a, and domain name address 1.1.1.2 in domain name file 1; the target update record 2 is deleting rr01, record type A and domain name address 1.1.1 in the domain name file 1, then according to the update record 1, the slave DNS equipment can add 'rr 01, record type A and domain name address 1.1.1.2' in the domain name file 1, and according to the update sequence number 009, the sequence number in the domain name file 1 is updated to 009; it is possible to delete "rr01, record type a, domain name address 1.1.1.1" in domain name file 1 according to the target update record 2, and update the sequence number in domain name file 1 to 010 according to the update sequence number 010.

If the update information includes a domain name file corresponding to the target domain name, the domain name file may be stored in a view corresponding to the first view identifier from the DNS device. For example, if the update information is a domain name file 1, the DNS device may store the domain name file 1 in view 1 corresponding to view identifier 1.

S409, determining a first access line according to the first view identifier and the mapping relation.

Because the secret key, the view identifier and the access lines in the mapping relation are in one-to-one correspondence, the first access line can be determined in the mapping relation according to the first view identifier.

For example, if the mapping relationship is shown in table 1, the first view identifier is view identifier 1, and the first access line may be determined to be line 1 in the mapping relationship according to view identifier 1.

S410, updating the structured data according to the updating information and the first access line.

In an alternative embodiment, the structured data may be updated according to the update information and the first access line by: determining an updated domain name, an updated domain name address corresponding to the updated domain name and an updated type according to the updated information; determining a first structured record according to the updated domain name, the updated domain name address and the access line; and updating the structured data according to the update type and the first structured record.

The update type may include an add type, a delete type, or a modify type.

For example, if the update information includes the target update record 1, and the target update record 1 is to add rr01, record type a, and domain name address 1.1.1.2 to the domain name file 1, it may be determined that the update domain name is rr01.Dnstest1.com, the update domain name address is 1.1.1.2, and the update type is an add type according to the target update record 1.

Alternatively, the slave DNS device may determine the first structured record based on the updated domain name, the updated domain name address, and the access line. The first structured record may include an updated domain name, an updated domain name address, and an access line. For example, if it is determined from the DNS device that the first access line is line 1, and it is determined that the updated domain name is rr01.Dnstest1.Com and the updated domain name address is 1.1.1.2 according to the updated information, it may be determined that the updated domain name rr01.Dnstest1.Com, the updated domain name address 1.1.1.2, and the line 1 may be included in the first structured record 1.

Optionally, according to the update type and the first structured record, updating the structured data may include 3 cases:

case 1: the update type is an add type.

In this case, then, a first structured record may be newly added to the structured data.

For example, if the update type is the addition type as shown in table 2, and the first structured record 1 includes the updated domain name rr01.Dnstest1.Com, the updated domain name address 1.1.1.2, and the line 1, then the first structured record 1 may be newly added to the structured data, i.e., table 2.

Case 2: the update type is a delete type.

In this case, the first structured record may then be deleted from the structured data.

For example, if the structured data is a deletion type as shown in table 2, and the first structured record 2 includes the updated domain name rr01.Dnstest1.Com, the updated domain name address 1.1.1.1 and the line 1, the first structured record 2 may be deleted in the structured data, i.e., table 2.

Case 3: the update type is a modification type.

In this case, the domain name address corresponding to the updated domain name and the access line in the structured data may be updated to the updated domain name address.

For example, if the structured data is a modification type as shown in table 2, and the first structured record 3 includes the updated domain name rr01.Dnstest1.Com, the updated domain name address 3.3.3.1, and the line 2, the domain name address 3.3.3.3 corresponding to the line 2 may be updated to the updated domain name address 3.3.3.1 in the structured data, i.e., table 2.

By the technical scheme, the slave DNS equipment can generate the structured data in real time according to the domain name resolution data in the domain name file. The staff can manage the structured data, so that the management efficiency of domain name resolution data is improved; and the structured data can be obtained without greatly changing the main DNS equipment, so that the reliability of the main DNS equipment is improved.

In the embodiment of the application, the master DNS equipment can send the update notification to the slave DNS equipment, and the slave DNS equipment acquires the mapping relation according to the update notification, wherein the mapping relation comprises a plurality of keys. If the first key exists in the plurality of keys, the slave DNS equipment can determine the first view identifier according to the first key and the mapping relation, and determine whether a first domain name file corresponding to the target domain name exists according to the first view identifier and the target domain name. If so, the slave DNS device can send a first synchronization request to the master DNS device; if not, the slave DNS device may send a second synchronization request to the master DNS device. The master DNS device may send update information corresponding to the target domain name to the slave DNS device according to the first synchronization request or the second synchronization request. The slave DNS equipment can update a domain name file corresponding to a target domain name in the slave DNS equipment according to the update information, and determine a first access line according to the first view identifier and the mapping relation, so that the structured data can be updated according to the update information and the first access line. The slave DNS equipment can synchronize the updated information in the master DNS equipment in real time so as to keep the consistency of the domain name file in the slave DNS equipment and the domain name file in the master DNS equipment; and the structured data can be generated from the DNS equipment according to the domain name file, and can be updated in real time according to the update information, so that the timeliness of acquiring the structured data is improved.

The domain name data processing method described above will be described in further detail by way of a specific example with reference to fig. 5 on the basis of any of the above embodiments.

Fig. 5 is a schematic process diagram of a domain name data processing method according to an exemplary embodiment of the present application. Referring to fig. 5, a master DNS device and a slave DNS device are included.

The main DNS device may include 3 views, and each view may include a key, a plurality of domain names, and a domain name file corresponding to the plurality of domain names. The domain name file may have a corresponding updated record file. For example, the domain name dnstest1.Com and the corresponding domain name file 1 may be included in view 1, and the domain name file 1 may have the corresponding update record file 1. Update record 1 and corresponding update sequence number 009, update record 2 and corresponding update sequence number 010, update record 3 and corresponding update sequence number 011 may be included in update record file 1.

Optionally, since there is a corresponding key in each view in the master DNS device, the program statement "allow-transfer { key $tsigkey1}" may be added to the master DNS device, allowing update files to be sent to the slave DNS device according to the key; an update notification (Notify) may be sent after the domain name file is changed in the primary DNS device add notification (Notify) configuration, i.e., the IPkey $tsigkey1 of also-Notify { $dnsfover, so that the secondary DNS device may send a synchronization request in time to obtain update information.

In step (1), when the domain name file corresponding to the target domain name in the master DNS device is updated, the master DNS device may send an update notification to the slave DNS device. For example, if the target domain name is dnstest1.Com, and the corresponding domain name file 1 is updated, the master DNS device may send an update notification to the slave DNS device, where the update notification may include the key 1, the first update sequence number 011, and the target domain name dnstest1.Com.

In step (2), after receiving the update notification from the DNS device, the mapping relationship may be acquired, and the view identifier 1 may be determined in the mapping relationship according to the key 1 in the update notification. From the DNS device can determine whether there is a domain name file 1 corresponding to the target domain name dnstest1.Com in view 1 corresponding to view identification 1.

In step (3), if it is determined that the domain name file 1 corresponding to the target domain name dnstest1.Com exists in the view 1 corresponding to the view identifier 1, and the second update sequence number in the domain name file 1 is 008, the slave DNS device may send a first synchronization request to the master DNS device, where the first synchronization request may include the key 1, the second update sequence number 008, and the target domain name dnstest1.Com.

In step (4), the master DNS device may determine, according to the first synchronization request, an update record file, and determine, in the update record file, an update record with an update sequence number greater than the second update sequence number as a target update record according to the second update sequence number, so as to send update information to the slave DNS device, where the update information includes multiple-entry update records. For example, the primary DNS device may determine the domain name file 1, and thus the update record file 1, based on the key 1 in the first synchronization request and the target domain name dnstest1.Com. The primary DNS device may determine, as the target update record, update record 1 corresponding to update sequence number 009, update record 2 corresponding to update sequence number 010, and update record 3 corresponding to update sequence number 011 in update record file 1 according to the second update sequence number 008. The master DNS device may send update information corresponding to the target domain name to the slave DNS device, where the update information includes 3-entry target update records, that is, update record 1, update record 2, and update record 3.

In step (5), after receiving the update information from the DNS device, the domain name file corresponding to the target domain name may be updated according to the update information. For example, if the update information includes update record 1, update record 2 and update record 3, wherein update record 1 is to modify domain name address 1.1.1.1 in domain name file 1 to update domain name address 1.1.1.2; updating the record 2 to delete the sub-domain name prefix rr01, the record type A and the domain name address 2.2.2.2 in the domain name file 1; update record 3 is a new sub-domain name prefix rr01, record type a and domain name address 5.5.5.5 in domain name file 1, and the domain name address 1.1.1.1 can be modified from DNS device to update domain name address 1.1.1.2 in domain name file 1 according to update record 1; the domain name prefix rr01, the record type A and the domain name address 2.2.2.2 can be deleted in the domain name file 1 according to the updated record 2; the second update sequence number of the domain name file 1 may be updated to 011 according to the update record 3 by adding the domain name prefix rr01, the record type a, and the domain name address 5.5.5.5 to the domain name file 1.

In step (6), the slave DNS device may determine line 1 in the mapping relationship from view identification 1.

If the original structured data in the slave DNS device is shown in the resolved data table 1, in step (7), the slave DNS device may update the resolved data table 1 according to the update information and the line 1. Since the update information includes update record 1, update record 2 and update record 3, it can be determined that update record 1 is of a modification type, and according to update record 1 and line 1, a first structured record 1 is determined, where the first structured record 1 includes update domain name rr01.Dnstest1.Com, domain name address 1.1.1.2 and line 1; update record 2 may be determined to be of a delete type, and a first structured record 2 may be determined from update record 2 and line 1, where update domain name rr01.Dnstest1.Com, domain name address 2.2.2.2 and line 1 may be included in first structured record 2; the update record 3 may be determined to be of an addition type, and the first structured record 3 may be determined according to the update record 3 and the line 1, and the first structured record 3 may include the update domain name rr01.Dnstest1.Com, the domain name address 5.5.5.5, and the line 1, and then the parsing data table 1 may be updated according to the first structured record 1, the first structured record 2, and the first structured record 3, to obtain the parsing data table 2.

Alternatively, the structured data may be stored in the slave DNS device or in the first device. If the structured data is stored in the first device, after the update information is obtained from the DNS device, the domain name file or the target update record may be converted into a plurality of structured records according to the update information and the mapping relationship, and the plurality of structured records may be sent to the first device, where the structured data in the first device is updated.

Alternatively, the staff may manage the structured data in the first device by parsing the data software or platform on the terminal device.

Fig. 6 is a schematic diagram of a page displaying structured data according to an exemplary embodiment of the present application. Referring to fig. 6, if the structured data is shown in the resolution data table 2 in fig. 5, a worker may log in software or a platform on the terminal device, search for the subdomain name rr01.Dnstest1.Com, the terminal device may send a data request to the first device to obtain structured data corresponding to the subdomain name rr01.Dnstest1.Com, that is, structured domain name resolution data, and display the structured domain name resolution data, as shown in fig. 6, where the subdomain name rr01.Dnstest1.Com may correspond to structured resolution data under different lines, so that a global view configuration of the subdomain name rr01.Dnstest1.Com may be intuitively presented. The staff can perform unified management on the structured resolution data under different lines, namely, the staff can perform unified management on the domain resolution data in a plurality of domain name files under different views.

Optionally, if the domain name resolution data of each line corresponding to the subdomain name is the same, aggregation optimization can be performed on the display page, so as to facilitate unified management and modification.

Fig. 7 is a schematic diagram of an aggregation optimized page according to an exemplary embodiment of the present application. Referring to fig. 7, an interface 701 and an interface 702 are included. For example, if the subdomain name rr01.Dnstest1.Com, the record types in line 1, line 2 and line 3 are all a, the domain addresses are all 1.1.1.1, the TTL is all 600, and all lines include line 1, line 2 and line 3 in total, the structured parsing data in the interface 701 may be aggregated and optimized, and displayed as shown in the interface 702. The staff member can uniformly modify the structured resolution data under all lines corresponding to the sub domain name rr01.Dnstest1.Com in the interface 702.

In the technical solution of the present application, DNS conversion (Converter) software may be provided in the slave DNS device. The Dns Converter software can be divided into two parts, and the roles of the slave DNS equipment can be realized through update notification and a synchronous request between the Dns Converter software and the master DNS equipment, so that non-invasive data synchronous access is realized; the first device can convert the resolution data in the domain name file format into the structural resolution data through the data converter, any required data format can be realized through an expansion mode, and the view can be converted into a line, so that in the terminal device, the domain name resolution data can take the domain name as a main body, and the resolution data under different views corresponding to the domain name can be intuitively displayed.

In the embodiment of the application, the master DNS equipment can send the update notification to the slave DNS equipment, and the slave DNS equipment acquires the mapping relation according to the update notification, wherein the mapping relation comprises a plurality of keys. If the first key exists in the plurality of keys, the slave DNS equipment can determine the first view identifier according to the first key and the mapping relation, and determine whether a first domain name file corresponding to the target domain name exists according to the first view identifier and the target domain name. If so, the slave DNS device may send a first synchronization request to the master DNS device. The master DNS device may send update information corresponding to the target domain name to the slave DNS device according to the first synchronization request. The slave DNS equipment can update a domain name file corresponding to a target domain name in the slave DNS equipment according to the update information, and determine a first access line according to the first view identifier and the mapping relation, so that the structured data can be updated according to the update information and the first access line. The slave DNS equipment can synchronize the updated information in the master DNS equipment in real time so as to keep the consistency of the domain name file in the slave DNS equipment and the domain name file in the master DNS equipment; and the structured data can be generated from the DNS equipment according to the domain name file, and can be updated in real time according to the update information, so that the timeliness of acquiring the structured data is improved.

Fig. 8 is a schematic structural diagram of a domain name data processing device according to an exemplary embodiment of the present application. For application to a slave domain name system DNS device, referring to fig. 8, the apparatus 10 includes: a first receiving module 11, an acquisition module 12 and an updating module 13, wherein,

the first receiving module 11 is configured to receive an update notification sent by a primary DNS device, where the update notification is used to indicate that a domain name file corresponding to a target domain name in the primary DNS device is updated;

the acquiring module 12 is configured to request, according to the update notification, the primary DNS device to acquire update information corresponding to the target domain name;

the updating module 13 is configured to update, according to the updating information, a domain name file corresponding to the target domain name in the slave DNS device, and structured data, where the structured data includes a plurality of domain names and domain name addresses corresponding to the domain names.

The domain name data processing device provided by the embodiment of the application can execute the technical scheme shown in the embodiment of the method, and the implementation principle and the beneficial effects are similar, and are not repeated here.

In a possible implementation manner, the main DNS device includes multiple views, where the views include domain name files corresponding to multiple domain names; the update notification comprises a first key and the target domain name; the acquiring module 12 is specifically configured to:

In one possible implementation, the obtaining module 12 is specifically configured to:

In a possible implementation manner, the update notification further includes a first update sequence number; the acquiring module 12 is specifically configured to:

In a possible implementation manner, the mapping relationship further includes an access line corresponding to the view identifier; the update module 13 is specifically configured to:

In a possible implementation manner, the updating module 13 is specifically configured to:

Fig. 9 is a schematic structural diagram of another domain name data processing apparatus according to an exemplary embodiment of the present application. For application to a primary DNS device, referring to fig. 9, the apparatus 20 includes: a first transmitting module 21, a second receiving module 22 and a second transmitting module 23, wherein,

the first sending module 21 is configured to send an update notification to a slave DNS device, where the update notification is used to indicate that a domain name file corresponding to a target domain name in the master DNS device is updated;

the second receiving module 22 is configured to receive a synchronization request corresponding to the target domain name sent from the DNS device;

the second sending module 23 is configured to send, according to the synchronization request, update information corresponding to the target domain name to the slave DNS device, where the update information is used for updating, by the slave DNS device, a domain name file corresponding to the target domain name and structured data.

In a possible implementation manner, the main DNS device includes multiple views, where the views include domain name files corresponding to multiple domain names; the synchronization request comprises a first key, a target domain name and a second updating sequence number; the second sending module 23 is specifically configured to:

In one possible implementation, the primary DNS device includes multiple views therein; the synchronization request includes a first key and a target domain name; the second sending module 23 is specifically configured to:

An exemplary embodiment of the present application provides a schematic structural diagram of a slave DNS device, referring to fig. 10, the slave DNS device 30 may include a processor 31 and a memory 32. The processor 31, the memory 32, and the like are illustratively interconnected by a bus 33.

The memory 32 stores computer-executable instructions;

the processor 31 executes computer-executable instructions stored in the memory 32, so that the processor 31 executes the domain name data processing method as shown in the above-described method embodiment.

An exemplary embodiment of the present application provides a schematic structural diagram of a primary DNS device, referring to fig. 11, the primary DNS device 40 may include a processor 41 and a memory 42. The processor 41, the memory 42, are illustratively interconnected by a bus 43.

The memory 42 stores computer-executable instructions;

The processor 41 executes computer-executable instructions stored in the memory 42, so that the processor 41 executes the domain name data processing method as shown in the above-described method embodiment.

Accordingly, an embodiment of the present application provides a computer readable storage medium, where computer executable instructions are stored, where the computer executable instructions are used to implement the domain name data processing method according to any one of the above method embodiments when executed by a processor.

Accordingly, embodiments of the present application may also provide a computer program product, including a computer program, which when executed by a processor may implement the domain name data processing method shown in any of the above method embodiments.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in the scope of the claims of the present application.

Claims

1. A domain name data processing method, applied to a slave domain name system DNS device, the method comprising:

updating a domain name file corresponding to the target domain name in the DNS equipment and structured data according to the updating information, wherein the structured data comprises a plurality of domain names and domain name addresses corresponding to the domain names;

the main DNS equipment comprises a plurality of views, wherein the views comprise domain name files corresponding to a plurality of domain names; the update notification comprises a first key and the target domain name; requesting to obtain update information corresponding to the target domain name from the main DNS equipment according to the update notification, wherein the update information comprises:

2. The method of claim 1, wherein requesting the primary DNS device to obtain the update information based on the first view identifier and the target domain name comprises:

3. The method of claim 2, wherein the update notification further includes a first update sequence number; requesting the primary DNS device to obtain a target update record, including:

4. The method of claim 2, wherein requesting, from the primary DNS device, to obtain a domain name file corresponding to the target domain name in the first view, includes:

5. The method according to any one of claims 1-4, wherein the mapping relationship further comprises an access line corresponding to the view identifier; updating the structured data in the slave DNS device according to the update information, including:

6. The method of claim 5, wherein updating the structured data based on the update information and the first access line comprises:

7. The method of claim 6, wherein updating the structured data based on the update type and the first structured record comprises:

8. A domain name data processing method, applied to a primary DNS device, where the primary DNS device includes multiple views, each view having a corresponding key, the method comprising:

according to the synchronization request, sending update information corresponding to the target domain name to the slave DNS equipment, wherein the update information is used for updating a domain name file corresponding to the target domain name and structured data by the slave DNS equipment, and the structured data comprises a plurality of domain names and domain name addresses corresponding to the domain names;

if the view comprises domain name files corresponding to a plurality of domain names; the synchronization request comprises a first key, a target domain name and a second updating sequence number; according to the synchronization request, sending update information corresponding to the target domain name to the slave DNS equipment, wherein the update information comprises:

9. The method of claim 8, wherein if the synchronization request includes a first key and a target domain name; according to the synchronization request, sending update information corresponding to the target domain name to the slave DNS equipment, wherein the update information comprises:

10. A slave DNS device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor;

wherein the memory stores instructions executable by the at least one processor to cause the slave DNS device to perform the method of any of claims 1-7.

11. A primary DNS device, comprising:

at least one processor; and

A memory communicatively coupled to the at least one processor;

wherein the memory stores instructions executable by the at least one processor to cause the primary DNS device to perform the method of any of claims 8-9.

12. A computer readable storage medium having stored therein computer executable instructions which, when executed by a processor, implement the method of any one of claims 1-7 or any one of claims 8-9.