CN109788080B - Domain name resolution method and device based on graph view, electronic equipment and medium - Google Patents
Domain name resolution method and device based on graph view, electronic equipment and medium Download PDFInfo
- Publication number
- CN109788080B CN109788080B CN201811492916.8A CN201811492916A CN109788080B CN 109788080 B CN109788080 B CN 109788080B CN 201811492916 A CN201811492916 A CN 201811492916A CN 109788080 B CN109788080 B CN 109788080B
- Authority
- CN
- China
- Prior art keywords
- view
- zone
- area
- group
- domain name
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a domain name resolution method, a domain name resolution device, electronic equipment and a domain name resolution medium based on a graph view, wherein the method comprises the following steps: grouping a plurality of views to be processed in different forms according to preset service requirements of different areas to obtain view groups respectively corresponding to the different areas, and establishing a relationship between area names of the different areas and the view groups; establishing an associated IP address set for each view and establishing an associated area set for each view; when a DNS request message is received, according to a source IP of the DNS request message, a corresponding target view is determined, a zone set of the target view is obtained, according to a domain name to be inquired, a zone unit matched with the domain name to be inquired is obtained from the zone set of the target view, and domain name resolution is carried out on the DNS request message by utilizing zone data in the matched zone unit. The invention provides a novel DNS multi-view analysis mode, which supports a user to self-define and set a view group according to the service requirement of the user, and meets the diversified service requirement of the user.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a domain name resolution method and device based on a graph view, electronic equipment and a medium.
Background
A Domain Name System (DNS) is mainly used to complete mapping from a Domain Name to an Internet Protocol (IP) address and resolution of other Internet resources, and is an important infrastructure in the Internet.
The speed of the user to access the internet is influenced by the line and the region of the operator, for example, the content downloading from the telecommunication server by the user in communication is relatively slow. In order to solve the problem, early network service providers respectively erect servers in the internet and the telecommunication, and set hyperlinks (such as internet downloading and telecommunication downloading) on web pages to enable users to manually select downloading lines, and the scheme has the problem of poor user experience.
In order to realize automatic selection of an access line, a DNS multi-view resolution technology appears, and the basic principle is as follows: the DNS authority resolution system configures multiple views in a linear structure, each view associating an operator's set of IP addresses and a set of zones (containing zone names and zone data). If the source IP address of the DNS request message matches the IP address set associated with the first view, analyzing by using the associated area, otherwise, matching the next view; if all views fail to match, the reject message is answered.
With the rapid development of the internet, many network service providers currently host domain names to professional DNS authority cloud resolution platforms. For a DNS authoritative cloud resolution platform, domain name resolution services need to be provided for a plurality of network service providers at the same time, and the existing multi-view resolution technology has the problems of being difficult to tune: the grouping of the current view is fixed (usually grouping is performed according to operator lines, such as grouping north-China telecom, south-China telecom, and the like into telecom), and it is difficult to meet the diversified service requirements of network service providers (for example, some network service providers want to group according to regions, such as grouping north-China telecom, north-China Unicom, and north-China Mobile into north-China).
Disclosure of Invention
Aiming at the problems in the prior art, the invention provides a domain name resolution method, a domain name resolution device, electronic equipment and a domain name resolution medium based on a graph view.
In order to solve the technical problems, the invention provides the following technical scheme:
in a first aspect, the present invention provides a domain name resolution method based on a graph view, including:
grouping a plurality of views to be processed in different forms according to preset service requirements of different areas to obtain view groups respectively corresponding to the different areas, and establishing a relationship between area names of the different areas and the view groups;
establishing an associated IP address set for each view;
determining the relationship between the area name and each view according to the relationship between the area name and each view group and the relationship between each view group and each view, and establishing a related area set for each view according to the relationship between the area name and each view, wherein the area set comprises one or more area units, each area unit is provided with corresponding area data or a corresponding area data index, the area data index is the number of other views in the same view group where the corresponding view is located, and the area data index is used for guiding and searching for corresponding area data shared by the same view group; whether each zone unit in the zone set is provided with corresponding zone data or a corresponding zone data index is determined by the relation between the zone files and the corresponding views in the preset service requirement of the zone;
determining a target view corresponding to a DNS request message to be subjected to domain name resolution according to a source IP of the DNS request message and an IP address set associated with each view;
and determining corresponding zone data according to the zone set associated with the target view and the domain name to be queried in the DNS request message, and performing domain name resolution on the DNS request message according to the determined zone data.
Further, the grouping of different forms of the multiple views to be processed according to the preset service requirements of different regions to obtain view groups respectively corresponding to the different regions, and establishing a relationship between the region names of the different regions and the view groups includes:
numbering each view to be processed in sequence, grouping the views in different forms according to preset service requirements of different areas to obtain view groups respectively corresponding to the different areas; wherein the view group comprises a view group consisting of more than two views, or a view group consisting of one or more single views and a view group; the view with the smallest number in each view group is the group leader view, and the other views are the group member views.
Further, the relationship between the area name and each view is determined according to the relationship between the area name and each view group and the relationship between each view group and each view, and an associated area set is established for each view according to the relationship between the area name and each view, the area set comprises one or more area units, each area unit is provided with corresponding area data or a corresponding area data index, the area data index is a number of other views in the same view group where the corresponding view is located, and the area data index is used for guiding to search for corresponding area data shared by the same view group; whether each zone unit in the zone set is provided with corresponding zone data or a corresponding zone data index is determined by the relationship between the zone files and the corresponding views in the preset service requirement of the zone, and the method comprises the following steps:
determining the relationship between the area name and each view according to the relationship between the area name and each view group and the relationship between each view group and each view, and establishing a related area set for each view according to the relationship between the area name and each view, wherein the area set comprises one or more area units; each zone unit comprises three items of content, namely a zone name, zone data and a view number;
when loading the zone file of the corresponding zone, if the zone file of the zone needs to be configured on a single view according to the preset service requirement of the zone, generating a zone unit, wherein the zone unit comprises the zone name of the zone, the zone data of the zone and the view number of the single view, and adding the generated zone unit into a zone set corresponding to the single view;
if the zone file of the zone needs to be configured on a view group according to the preset service requirement of the zone, generating a zone unit, wherein the zone unit comprises a zone name of the zone, zone data of the zone and a view number of a group length view of the view group, and adding the generated zone unit into a zone set corresponding to the group length view; and simultaneously generating another area unit, wherein the area unit comprises the area name and the null data of the area and the view number of the group length view of the view group, and sequentially adding the generated area unit to an area set corresponding to each group member view of the view group.
Further, the determining, according to the zone set associated with the target view and the domain name to be queried in the DNS request message, corresponding zone data, and performing domain name resolution on the DNS request message according to the determined zone data includes:
acquiring a zone unit matched with the domain name to be inquired from the zone set associated with the target view according to the zone set associated with the target view and the domain name to be inquired in the DNS request message, and if zone data in the matched zone unit is not null data, directly utilizing the zone data in the matched zone unit to carry out domain name resolution on the DNS request message; and if the zone data in the matched zone unit is null data, acquiring the zone unit matched with the domain name to be inquired from the zone set of the group leader view corresponding to the group leader view number according to the third content group leader view number in the matched zone unit, and performing domain name resolution on the DNS request message by using the zone data in the zone unit matched in the zone set of the group leader view.
Further, the method further comprises:
and if the zone unit matched with the domain name to be inquired is not obtained from the zone set associated with the target view according to the domain name to be inquired in the DNS request message, responding to a refusal message.
Further, the preset service requirement includes: the service division is carried out according to the operator, the service division is carried out according to the region, and the service division is carried out according to the region and the operator.
Further, the determining a target view corresponding to the DNS request packet according to the source IP of the DNS request packet to be subjected to domain name resolution and the IP address set associated with each view includes:
and according to the source IP of the DNS request message to be subjected to domain name resolution and the IP address set associated with each view, retrieving the IP address set associated with each view according to the longest matching principle, and determining a target view corresponding to the DNS request message.
In a second aspect, the present invention further provides a domain name resolution device based on a graph view, including:
the grouping module is used for grouping a plurality of views to be processed in different forms according to preset service requirements of different areas to obtain view groups respectively corresponding to the different areas, and establishing the relationship between the area names of the different areas and the view groups;
the first establishing module is used for establishing an associated IP address set for each view;
the second establishing module is used for determining the relationship between the area name and each view according to the relationship between the area name and each view group and the relationship between each view group and each view, and establishing a related area set for each view according to the relationship between the area name and each view, wherein the area set comprises one or more area units, each area unit is provided with corresponding area data or a corresponding area data index, the area data index is the number of other views in the same view group where the corresponding view is located, and the area data index is used for guiding and searching for corresponding area data shared by the same view group; whether each zone unit in the zone set is provided with corresponding zone data or a corresponding zone data index is determined by the relation between the zone files and the corresponding views in the preset service requirement of the zone;
the determining module is used for determining a target view corresponding to the DNS request message according to a source IP of the DNS request message to be subjected to domain name resolution and an IP address set associated with each view;
and the resolution module is used for determining corresponding zone data according to the zone set associated with the target view and the domain name to be queried in the DNS request message, and performing domain name resolution on the DNS request message according to the determined zone data.
In a third aspect, the present invention further provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the steps of the domain name resolution method based on the graph view according to the first aspect are implemented.
In a fourth aspect, the present invention also provides a computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps of the graphical view based domain name resolution method according to the first aspect.
As can be seen from the above technical solutions, the domain name resolution method based on graph views provided by the present invention first groups a plurality of views to be processed in different forms according to preset service requirements of different regions, to obtain view groups corresponding to the different regions, establishes a relationship between a region name of the different regions and each view group, then establishes an associated IP address set for each view, then determines a relationship between the region name and each view according to the relationship between the region name and each view group and the relationship between each view group and each view, and establishes an associated region set for each view according to the relationship between the region name and each view, where each region set includes one or more region units, and each region unit is provided with corresponding region data or a corresponding region data index; and finally, determining a target view corresponding to the DNS request message according to a source IP of the DNS request message to be subjected to domain name resolution and an IP address set associated with each view, determining corresponding zone data according to a zone set associated with the target view and a domain name to be inquired in the DNS request message, and performing domain name resolution on the DNS request message according to the determined zone data. Therefore, the invention provides a novel DNS multi-view analysis mode, which is characterized in that an associated IP address set is established for each view, a region set is established according to the relationship between the region name and the view, a DAG graph structure taking the view as a vertex and the region data sharing relationship as an edge is formed, a user is supported to self-define and set a view group according to the self business requirement, and the diversified business requirement of the user is met. Therefore, compared with the traditional multi-view structure defined by an administrator of the DNS authoritative cloud analysis platform, and the condition that the relationship among the views is fixed, the multi-view structure is defined by all users of the DNS authoritative cloud analysis platform together, the relationship among the views is dynamically changed, and the service requirement of the DNS authoritative cloud analysis platform for self-defining view grouping can be met. In addition, the view group shares the same region data in the group, thereby realizing the maximum resource sharing and improving the use benefit of system resources.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a flowchart of a domain name resolution method based on a graph view according to an embodiment of the present invention;
FIG. 2 is a view group G provided in an embodiment of the present invention1And G2A schematic diagram of (a);
FIG. 3 is a view group G provided in an embodiment of the present invention3And G4A schematic diagram of (a);
FIG. 4 is a schematic view of a view division for a user according to an embodiment of the present invention;
FIG. 5 is a graphical view schematic provided by one embodiment of the present invention;
fig. 6 is a schematic structural diagram of a domain name resolution device based on a graph view according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of an electronic device according to yet another embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In order to meet the requirement of a network service provider for user-defined view grouping on a DNS authoritative cloud resolution platform, the invention provides a domain name resolution method, a domain name resolution device, electronic equipment and a domain name resolution medium based on a graph view. Compared with the traditional multi-view structure defined by an administrator of the DNS authoritative cloud analysis platform, and the condition that the relationship among the views is fixed, the multi-view structure is defined by all users of the DNS authoritative cloud analysis platform together, and the relationship among the views is dynamically changed, so that the service requirement of the DNS authoritative cloud analysis platform for self-defining view grouping can be met. The present invention will be explained in detail below with reference to specific examples.
Fig. 1 shows a flowchart of a domain name resolution method based on a graph view according to an embodiment of the present invention, and referring to fig. 1, the domain name resolution method based on a graph view according to the embodiment of the present invention includes the following steps:
step 101: grouping a plurality of views to be processed in different forms according to preset service requirements of different areas to obtain view groups respectively corresponding to the different areas, and establishing a relationship between area names of the different areas and the view groups.
In this step, the multiple views to be processed are sequentially 1, 2. The preset service requirements include: the service division is carried out according to the operator, the service division is carried out according to the region, and the service division is carried out according to the region and the operator. For example, the service requirement of the area a is to perform service division according to an operator, the service requirement of the area b is to perform service division according to regions and operators, and the service requirement of the area c is to perform service division according to regions, then the views 1,2,.
Step 102: an associated set of IP addresses is established for each view.
In this step, an associated set A of IP addresses is established for each view iiAnd a is an IP address field.
Step 103: determining the relationship between the area name and each view according to the relationship between the area name and each view group and the relationship between each view group and each view, and establishing a related area set for each view according to the relationship between the area name and each view, wherein the area set comprises one or more area units, each area unit is provided with corresponding area data or a corresponding area data index, the area data index is the number of other views in the same view group where the corresponding view is located, and the area data index is used for guiding and searching for corresponding area data shared by the same view group; whether each zone unit in the zone set sets corresponding zone data or corresponding zone data index is determined by the relationship between the zone files and the corresponding views in the preset service requirement of the zone.
In this step, an associated area set is established for each view, that is, an area set having a service association relationship with a corresponding view is established, where the area set includes one or more area units (an area unit here refers to an area), each area unit is provided with corresponding area data or a corresponding area data index, the area data index is a number of another view in the same view group where the corresponding view is located, and the area data index is used to guide and search for corresponding area data shared by the same view group; whether each zone unit in the zone set sets corresponding zone data or corresponding zone data index is determined by the relationship between the zone files and the corresponding views in the preset service requirement of the zone. For example, if the corresponding zone file corresponds to a single view according to the preset service requirement of the zone, corresponding zone data is set in the zone unit in the zone set associated with the view; if the corresponding zone file corresponds to a view group according to the preset service requirement of the zone and the view is a group length view in the view group, corresponding zone data are set in the zone unit in the zone set associated with the view; if the corresponding zone file corresponds to a view group according to the preset service requirement of the zone, and the view is a member view in the view group, a corresponding zone data index is set in the zone unit in the zone set associated with the view, the zone data index is the number of the group leader view in the view group, and then the zone data (the data is the shared data in the view group) in the zone unit associated with the group leader view can be found according to the zone data index.
Step 104: and determining a target view corresponding to the DNS request message according to the source IP of the DNS request message to be subjected to domain name resolution and the IP address set associated with each view.
In this step, according to the source IP of the DNS request packet and the associated IP address set established for each view, all IP address sets can be retrieved according to the longest matching rule, and the target view corresponding to the DNS request packet is determined.
Step 105: and determining corresponding zone data according to the zone set associated with the target view and the domain name to be queried in the DNS request message, and performing domain name resolution on the DNS request message according to the determined zone data.
In this step, according to the zone set associated with the target view and the domain name to be queried in the DNS request message, a matching zone unit is found from the zone set associated with the target view, and then different processing is performed according to whether corresponding zone data exists in the matching zone unit. If the matched zone unit has corresponding zone data, performing domain name resolution on the DNS request message according to the corresponding zone data; if the matched zone unit does not have corresponding zone data but has a corresponding zone data index, the obtained target view is a member view in a view group, at this time, a view corresponding to the zone data index is found according to the zone data index, the view is a group length view, then a zone unit matched with the domain name to be inquired is found from a zone set associated with the group length view, and domain name resolution is performed on the DNS request message according to the zone data (shared zone data in the view group) in the zone unit.
It can be seen that, in this embodiment, corresponding view groups may be respectively established according to service requirements of different regions, that is, in this embodiment, a relationship between views is not fixed, but may be dynamically changed according to different service requirements, so that a service requirement of a DNS authoritative cloud analysis platform for custom view grouping may be met (for example, a network service provider may divide a view group according to regions, operators, and other various forms, so as to meet diversified service requirements of users). In this embodiment, corresponding view groups are respectively established according to service requirements of different regions, and a DAG graph structure with a view as a vertex and a region data sharing relationship as an edge is formed, so that the same region data in the view group sharing group is realized, thereby maximally realizing resource sharing and improving the use benefit of system resources.
As can be seen from the foregoing technical solutions, in the domain name resolution method based on graph views provided in this embodiment, first, a plurality of views to be processed are grouped in different forms according to preset service requirements of different regions, so as to obtain view groups respectively corresponding to the different regions, establish a relationship between a region name of the different regions and each view group, then establish an associated IP address set for each view, then determine a relationship between the region name and each view according to the relationship between the region name and each view group and the relationship between each view group and each view, and establish an associated region set for each view according to the relationship between the region name and each view, where each region set includes one or more region units, and each region unit is provided with corresponding region data or a corresponding region data index; and finally, determining a target view corresponding to the DNS request message according to a source IP of the DNS request message to be subjected to domain name resolution and an IP address set associated with each view, determining corresponding zone data according to a zone set associated with the target view and a domain name to be inquired in the DNS request message, and performing domain name resolution on the DNS request message according to the determined zone data. Therefore, the embodiment provides a novel DNS multi-view parsing method, which establishes an associated IP address set for each view, establishes a region set according to a relationship between a region name and a view, forms a DAG graph structure with the view as a vertex and a region data sharing relationship as an edge, supports a user to self-define a view group according to a service requirement of the user, and meets diversified service requirements of the user. Therefore, compared with the traditional multi-view structure defined by an administrator of the DNS authoritative cloud analysis platform, and the situation that the relationship between the views is fixed, the multi-view structure in the embodiment is defined by users of all the DNS authoritative cloud analysis platforms together, and the relationship between the views is dynamically changed, so that the service requirement of the DNS authoritative cloud analysis platform for customizing the view groups can be met. In addition, in this embodiment, the same region data in the graph group sharing group is viewed, so that resource sharing is realized to the maximum extent, and the use benefit of system resources is improved.
Based on the content of the foregoing embodiments, in a preferred implementation, the step 101 is implemented as follows:
numbering each view to be processed in sequence, grouping the views in different forms according to preset service requirements of different areas to obtain view groups respectively corresponding to the different areas; wherein the view group comprises a view group consisting of more than two views, or a view group consisting of one or more single views and a view group; the view with the smallest number in each view group is the group leader view, and the other views are the group member views.
Based on the content of the foregoing embodiments, in a preferred implementation, the step 103 is implemented as follows:
determining the relationship between the area name and each view according to the relationship between the area name and each view group and the relationship between each view group and each view, and establishing a related area set for each view according to the relationship between the area name and each view, wherein the area set comprises one or more area units; each zone unit comprises three items of content, namely a zone name, zone data and a view number;
when loading the zone file of the corresponding zone, if the zone file of the zone needs to be configured on a single view according to the preset service requirement of the zone, generating a zone unit, wherein the zone unit comprises the zone name of the zone, the zone data of the zone and the view number of the single view, and adding the generated zone unit into a zone set corresponding to the single view;
if the zone file of the zone needs to be configured on a view group according to the preset service requirement of the zone, generating a zone unit, wherein the zone unit comprises a zone name of the zone, zone data of the zone and a view number of a group length view of the view group, and adding the generated zone unit into a zone set corresponding to the group length view; and simultaneously generating another area unit, wherein the area unit comprises the area name and the null data of the area and the view number of the group length view of the view group, and sequentially adding the generated area unit to an area set corresponding to each group member view of the view group.
Based on the content of the foregoing embodiments, in a preferred implementation, the step 105 is implemented as follows:
acquiring a zone unit matched with the domain name to be inquired from the zone set associated with the target view according to the zone set associated with the target view and the domain name to be inquired in the DNS request message, and if zone data in the matched zone unit is not null data, directly utilizing the zone data in the matched zone unit to carry out domain name resolution on the DNS request message; and if the zone data in the matched zone unit is null data, acquiring the zone unit matched with the domain name to be inquired from the zone set of the group leader view corresponding to the group leader view number according to the third content group leader view number in the matched zone unit, and performing domain name resolution on the DNS request message by using the zone data in the zone unit matched in the zone set of the group leader view.
The following explains the domain name resolution method based on the graph view in detail by a more complete embodiment. Specifically, the domain name resolution method based on the graph view comprises the following steps:
s1: and numbering each view to be processed in sequence.
In this step, the views to be processed are numbered in sequence. For example, the view is denoted by the symbol i, and the views are numbered sequentially as 1, 2.
S2: grouping the views in different forms according to preset service requirements of different areas to obtain different view groups; wherein the view group comprises a view group consisting of more than two views, or a view group consisting of one or more single views and a view group; the view with the smallest number in each view group is the group leader view, and the other views are the group member views.
In this step, the preset service requirement may include: the service division is carried out according to the operator, the service division is carried out according to the region, and the service division is carried out according to the region and the operator. For example, the service requirement of the area a is service division according to an operator, the service requirement of the area b is service division according to regions and operators, and the service requirement of the area c is service division according to regions, then the views numbered in step 101 are grouped in different forms (for example, grouped according to the operator, grouped according to regions and operators, grouped according to regions, etc.) according to the service requirements of the area a, the area b, and the area c, and different view groups are obtained.
In this step, a view set is denoted by V, { i |1 ≦ i ≦ k }, a view group is denoted by G,
the view group may be a view group consisting of two or more individual views, or may be a view group consisting of one or more individual views and a view group. For example, for the view i1,i2,.. and view group G1,G2,.. view group G, performing a union operation: g ═ i1,i2,...}∪G1∪G2U.S.; wherein, for each view group, the view with the smallest number is the group leader view, and the other views are the group member views.
S3: an associated set of IP addresses is established for each view.
In this step, an associated set A of IP addresses is established for each view iiAnd a is an IP address field.
S4: establishing an associated region set for each view, the region set comprising one or more region units; each zone unit comprises three items of content, namely a zone name, zone data and a view number.
In this step, the process of establishing the associated region set for each view is as follows:
when loading the zone file of the corresponding zone, if the zone file of the zone needs to be configured on a single view according to the preset service requirement of the zone, generating a zone unit, wherein the zone unit comprises the zone name of the zone, the zone data of the zone and the view number of the single view, and adding the generated zone unit into a zone set corresponding to the single view;
if the zone file of the zone needs to be configured on a view group according to the preset service requirement of the zone, generating a zone unit, wherein the zone unit comprises a zone name of the zone, zone data of the zone and a view number of a group length view of the view group, and adding the generated zone unit into a zone set corresponding to the group length view; simultaneously generating another area unit, wherein the area unit comprises the area name and the null data of the area and the view number of the group length view of the view group, and sequentially adding the generated area unit to an area set corresponding to each group member view of the view group;
in this step, that is to say, the associated zone set Z is established for each view ii{ (n, d, p) | n is a region name, d is region data, p ∈ V, p < i if d is null, and p ═ i if d is not null, ZiThe initialization is empty. When loading the zone file, if the zone file f is configured on the view i, generating (n, d, i) by f and the view number i, and adding the (n, d, i) into the zone set Z of the view iiPerforming the following steps; if the zone file f is configured on the view group G, (n, d, i ') is generated by f and the group leader view number i', and is added to the zone set Z of the group leader view ii，In (n, null, i') is generated and added to the zone set Z of each team member view in turnh(h∈G,h≠i')。
S5: and receiving a DNS request message.
S6: and determining a target view corresponding to the DNS request message according to the source IP of the DNS request message.
S7: and acquiring the region set of the target view.
S8: and acquiring a zone unit matched with the domain name to be inquired from the zone set of the target view according to the domain name to be inquired in the DNS request message, and performing domain name resolution on the DNS request message by utilizing zone data in the matched zone unit.
In this step, according to the domain name to be queried in the DNS request message, a zone unit matched with the domain name to be queried is obtained from the zone set of the target view, and if the zone data in the matched zone unit is not null data, the domain name resolution is performed on the DNS request message by directly using the zone data in the matched zone unit; and if the zone data in the matched zone unit is null data, acquiring the zone unit matched with the domain name to be inquired from the zone set of the group leader view corresponding to the group leader view number according to the third content group leader view number in the matched zone unit, and performing domain name resolution on the DNS request message by using the zone data in the zone unit matched in the zone set of the group leader view.
In this stepThat is, according to the domain name to be queried in the DNS request message, the zone set Z of the target view can be retrieved according to the longest matching ruleiIf matching (n, null, p), then continue to search for Zp(ii) a If there is a match (n, d, i), then d is used for analysis.
It can be seen that, in this embodiment, corresponding view groups may be respectively established according to service requirements of different regions, that is, in this embodiment, a relationship between views is not fixed, but may be dynamically changed according to different service requirements, so that a service requirement of a DNS authoritative cloud analysis platform for custom view grouping may be met (for example, a network service provider may divide a view group according to regions, operators, and other various forms, so as to meet diversified service requirements of users). In this embodiment, corresponding view groups are respectively established according to service requirements of different regions, and a view with the smallest number in the view groups is selected as a group leader, and other views are selected as group members, so as to form a DAG graph structure with the view as a vertex and the region data sharing relationship as an edge, thereby implementing the same region data in the view group sharing group, thereby implementing resource sharing to the maximum extent and improving the use benefit of system resources. In addition, each view group always selects the view with the smallest number as the group length, so that the ring formation of the graphs can be effectively avoided, and the implementation is facilitated.
As can be seen from the above technical solutions, in the domain name resolution method based on graph views provided in this embodiment, first, the views to be processed are numbered in sequence, and then the views are grouped in different forms according to preset service requirements of different regions, so as to obtain different view groups; then, establishing an associated IP address set for each view and establishing an associated area set for each view; and finally, when a DNS request message is received, determining a target view corresponding to the DNS request message according to a source IP of the DNS request message, acquiring a zone set of the target view, then acquiring a zone unit matched with the domain name to be inquired from the zone set of the target view according to the domain name to be inquired in the DNS request message, and performing domain name resolution on the DNS request message by using zone data in the matched zone unit. Therefore, the embodiment provides a novel DNS multi-view parsing method, which establishes an associated IP address set for each view, establishes a region set according to a relationship between a region name and a view, forms a DAG graph structure with the view as a vertex and a region data sharing relationship as an edge, supports a user to self-define a view group according to a service requirement of the user, and meets diversified service requirements of the user. Therefore, compared with the traditional multi-view structure defined by an administrator of the DNS authoritative cloud analysis platform, and the condition that the relationship among the views is fixed, the multi-view structure in the invention is defined by all users of the DNS authoritative cloud analysis platform, and the relationship among the views is dynamically changed, so that the service requirement of the DNS authoritative cloud analysis platform for self-defining view grouping can be met. In addition, in this embodiment, the views are numbered, the numbers represent the views, the view with the smallest view number in the view group is defined as a group leader view, and the other views are group member views. Because each view group always selects the view with the smallest number as the group length, the method can effectively avoid the ring formation of the graphs and has high implementability. In addition, in this embodiment, the same region data in the graph group sharing group is viewed, so that resource sharing is realized to the maximum extent, and the use benefit of system resources is improved.
Based on the content of the foregoing embodiments, in a preferred implementation, the method further includes:
step 106: and if the zone unit matched with the domain name to be inquired is not obtained from the zone set of the target view according to the domain name to be inquired in the DNS request message, responding to a refusal message.
It should be noted that, on the premise that logics or structures of a plurality of preferred embodiments provided in this embodiment do not conflict with each other, the preferred embodiments may be freely combined, and the present invention is not limited to this.
The method for domain name resolution based on a graph view provided in this embodiment is illustrated below with reference to a specific example and fig. 2 to 5.
Taking four views of "north China Mobile", "north China telecom", "China Mobile", and "China telecom" as examples, where each view corresponds to a group of IP addresses, the network service provider 1 and the network service provider 2 have different view partitioning requirements.
The a.cn area of the network service provider 1 is divided by operators, and the same operators in different regions have the same area data resources. For the a.cn zones, "north china mobile" and "chinese mobile" have the same zone data resources, and "north china telecom" and "chinese telecom" have the same zone data resources. Two views of "mobile" and "telecom" are defined, wherein the "mobile" view includes two views of "north China mobile" and "China Mobile", and the "telecom" view includes two views of "north China telecom" and "China telecom". The cn region sets different region data on the view set "move" and "telecom", respectively.
The network facilitator 2 has two areas: cn and c. Cn is divided according to regions because of different region services, and is not required to be subdivided in the north China region, and the central China region is further subdivided according to operators. And c, the district data resources of the cn in North China and Central China are the same and do not need to be subdivided. For the b.cn zone, "north china mobile" and "north china telecom" have the same zone data resources. Defining the view group of north China, including north China Mobile and north China telecom. The cn area sets different area data on the north China view group, China Mobile and China telecom respectively. For c.cn, "north china mobile", "north china telecom", "chinese mobile", "chinese telecom" four views have the same zone data resources, defining the "north china" view group, including "north china" view group, "chinese mobile", and "chinese telecom". The cn area sets area data in the view group of "north china".
After the above specific service requirement is determined, the following processing is performed according to the domain name resolution method based on the graph view provided in this embodiment, which specifically includes a processing procedure:
firstly, numbering views 'North China Mobile', 'North China telecom', 'China Mobile' and 'China telecom' as 1,2,3 and 4 in sequence;
secondly, a user of the DNS authoritative cloud analysis platform sets a view group in a user-defined mode according to the service requirement of the user, and the description is as follows:
The network service provider 2 includes two areas, b.cn and c.cn. Define "North China" view group G3，G3Including "North China Mobile" and "North China Telecommunications", i.e. including View 1 and View 2, G 31, 2. Cn area of network facilitator 2 will be in view group G of north china3The zone data is set differently from the view 3 and the view 4. Define "North China center of China" view group G4，G4Comprising a "North China" view group G3"Huazhong move" view 3 and "Huazhong telecom" view 4, G4＝G3And u {3, 4} ═ {1,2,3,4 }. Cn area of network facilitator 2 will be in view group G of "north china4Upper set zone data, view group G3And G4Is defined as shown in fig. 3. Further, a view division diagram of the user is obtained as shown in fig. 4.
And thirdly, selecting the smallest view in each view group as a group leader view, and selecting other views as member views. For example, G1Group leader view is 1; g2The group leader view is 2; g3Group leader view is 1; g4The group leader view is 1.
Fourthly, establishing associated IP address set A for each viewi{ a | a is an IP address field };
fifthly, establishing a related area set for each view:
the set of zones for the "North China Mobile" View 1, Z, is shown in Table 1 below1＝{(a.cn,d_a1,1),(b.cn,d_b1,1),(c.cn,d_c1,1)}：
TABLE 1
The set of zones for "North China telecom" View 2, Z, is shown in Table 2 below2＝{(a.cn,d_a2,2),(b.cn,null,1),(c.cn,null,1)}：
TABLE 2
The set of zones for "Huazhong move" view 3 is shown in Table 3 below, as Z3＝{(a.cn,null,1),(b.cn,d_b3,3),(c.cn,null,1)}：
TABLE 3
The set of zones for "Huazhong telecom" view 4 is shown in Table 4 below, as Z4＝{(a.cn,null,2),(b.cn,d_b4,4),(c.cn,null,1)}：
TABLE 4
The specific graphical view relationship is shown in fig. 5.
Sixthly, receiving DNS request flow;
seventhly, searching an IP address set according to the request message source IP and the longest matching principle, and determining a view 4 of 'Huazhong telecom';
eighthly, searching the zone set Z of the view 4 according to the query domain name of the request message and the longest matching principle4Examples are described below:
if the query domain name is www.x.cn, if there is no matched area name, then the refusal message is answered;
if the query domain name is www.a.cn, match (a.cn, null,2), and view group length number is 2, continue at Z of view 22In Z, search for2If there is a match (a.cn, d _ a2,2), then the parsing response is performed with the zone data d _ a 1;
if the query domain name is www.b.cn, match (b.cn, d _ b4,4), then the parsing response is performed with the zone data d _ b 4;
if the query domain name is www.c.cn, match (c.cn, null,1), and view group length number is 1, continue at Z of view 11In Z, search for1Where there is a match (c.cn, d _ c1,1), a parse response is made with the zone data d _ c 1.
As can be seen from the above example analysis, in this embodiment, the relationship between the views is no longer a fixed relationship, but a view group suitable for the service requirement may be reestablished according to the specific service requirement of each area of the network service provider, so as to meet the requirement of service diversification. Furthermore, the same region data may be shared for each view within a view group, e.g., for view group G1In other words, the two views of "north China Mobile" and "China Mobile" can share the data d _ a 1; as another example, for view group G2In other words, the two views of north China telecom and China telecom can share the data d _ a 2; also as for view group G3In other words, the two views of "north China Mobile" and "north China telecom" can share the data d _ b 1; also as for view group G4For example, the data d _ c1 can be shared by four views of "north China Mobile", "North China telecom", "China Mobile", and "China telecom", so that the maximum sharing of resources can be realized. In addition, each view group always selects the view with the smallest number as the group length, so that the ring formation of the graphs can be effectively avoided, and the method has high implementability.
Based on the same inventive concept, another embodiment of the present invention provides a domain name resolution apparatus based on a graph view, referring to fig. 6, the apparatus including: a grouping module 21, a first establishing module 22, a second establishing module 23, a determining module 24 and a parsing module 25, wherein:
the grouping module 21 is configured to group a plurality of views to be processed in different forms according to preset service requirements of different areas, to obtain view groups respectively corresponding to the different areas, and to establish a relationship between area names of the different areas and the view groups;
a first establishing module 22, configured to establish an associated IP address set for each view;
a second establishing module 23, configured to determine a relationship between the area name and each view group according to the relationship between the area name and each view group and the relationship between each view group and each view, and establish an associated area set for each view according to the relationship between the area name and each view, where the area set includes one or more area units, each area unit is provided with corresponding area data or a corresponding area data index, the area data index is a number of another view in the same view group where the corresponding view is located, and the area data index is used to guide and search for corresponding area data shared by the same view group; whether each zone unit in the zone set is provided with corresponding zone data or a corresponding zone data index is determined by the relation between the zone files and the corresponding views in the preset service requirement of the zone;
a determining module 24, configured to determine, according to a source IP of a DNS request packet to be subjected to domain name resolution and an IP address set associated with each view, a target view corresponding to the DNS request packet;
and the resolution module 25 is configured to determine corresponding zone data according to the zone set associated with the target view and the domain name to be queried in the DNS request message, and perform domain name resolution on the DNS request message according to the determined zone data.
Based on the content of the foregoing embodiment, in a preferred implementation, the preset service requirement includes: the service division is carried out according to the operator, the service division is carried out according to the region, and the service division is carried out according to the region and the operator.
Based on the content of the foregoing embodiment, in a preferred implementation manner, the determining module 25 is specifically configured to:
according to a source IP of a DNS request message to be subjected to domain name resolution and an IP address set associated with each view, all the IP address sets are searched according to the longest matching principle, and a target view corresponding to the DNS request message is determined.
Based on the content of the foregoing embodiments, in a preferred implementation, the apparatus further includes:
and the response module is used for responding to a refusal message if a zone unit matched with the domain name to be inquired is not obtained from the zone set of the target view according to the domain name to be inquired in the DNS request message.
It should be noted that, on the premise that logics or structures of a plurality of preferred embodiments provided in this embodiment do not conflict with each other, the preferred embodiments may be freely combined, and the present invention is not limited to this.
Since the domain name resolution device based on the graph view provided by the embodiment can be used for executing the domain name resolution method based on the graph view described in the above embodiment, and the working principle and the beneficial effect are similar, detailed descriptions are omitted here, and specific contents can be referred to the description of the above embodiment.
Based on the same inventive concept, another embodiment of the present invention provides an electronic device, which specifically includes the following components, with reference to fig. 7: a processor 701, a memory 702, a communication interface 703 and a bus 704;
the processor 701, the memory 702 and the communication interface 703 complete mutual communication through the bus 704; the communication interface 703 is used for realizing information transmission between related devices such as modeling software, an intelligent manufacturing equipment module library and the like;
the processor 701 is configured to call a computer program in the memory 702, and when the processor executes the computer program, the processor implements all the steps of the above domain name resolution method based on the graph view, for example, when the processor executes the computer program, the processor implements the following steps:
step 101: grouping a plurality of views to be processed in different forms according to preset service requirements of different areas to obtain view groups respectively corresponding to the different areas, and establishing a relationship between area names of the different areas and the view groups.
Step 102: an associated set of IP addresses is established for each view.
Step 103: determining the relationship between the area name and each view according to the relationship between the area name and each view group and the relationship between each view group and each view, and establishing a related area set for each view according to the relationship between the area name and each view, wherein the area set comprises one or more area units, each area unit is provided with corresponding area data or a corresponding area data index, the area data index is the number of other views in the same view group where the corresponding view is located, and the area data index is used for guiding and searching for corresponding area data shared by the same view group; whether each zone unit in the zone set sets corresponding zone data or corresponding zone data index is determined by the relationship between the zone files and the corresponding views in the preset service requirement of the zone.
Step 104: and determining a target view corresponding to the DNS request message according to the source IP of the DNS request message to be subjected to domain name resolution and the IP address set associated with each view.
Step 105: and determining corresponding zone data according to the zone set associated with the target view and the domain name to be queried in the DNS request message, and performing domain name resolution on the DNS request message according to the determined zone data.
Based on the same inventive concept, yet another embodiment of the present invention provides a computer-readable storage medium, having a computer program stored thereon, which, when being executed by a processor, implements all the steps of the above-mentioned graphical-view-based domain name resolution method, for example, when the processor executes the computer program, the processor implements the following steps:
step 101: grouping a plurality of views to be processed in different forms according to preset service requirements of different areas to obtain view groups respectively corresponding to the different areas, and establishing a relationship between area names of the different areas and the view groups.
Step 102: an associated set of IP addresses is established for each view.
Step 103: determining the relationship between the area name and each view according to the relationship between the area name and each view group and the relationship between each view group and each view, and establishing a related area set for each view according to the relationship between the area name and each view, wherein the area set comprises one or more area units, each area unit is provided with corresponding area data or a corresponding area data index, the area data index is the number of other views in the same view group where the corresponding view is located, and the area data index is used for guiding and searching for corresponding area data shared by the same view group; whether each zone unit in the zone set sets corresponding zone data or corresponding zone data index is determined by the relationship between the zone files and the corresponding views in the preset service requirement of the zone.
Step 104: and determining a target view corresponding to the DNS request message according to the source IP of the DNS request message to be subjected to domain name resolution and the IP address set associated with each view.
Step 105: and determining corresponding zone data according to the zone set associated with the target view and the domain name to be queried in the DNS request message, and performing domain name resolution on the DNS request message according to the determined zone data.
In the description of the present invention, it should be noted that the terms "upper", "lower", and the like indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, which are merely for convenience in describing the present invention and simplifying the description, and do not indicate or imply that the referred device or element must have a specific orientation, be constructed in a specific orientation, and operate, and thus, should not be construed as limiting the present invention. Unless expressly stated or limited otherwise, the terms "mounted," "connected," and "connected" are intended to be inclusive and mean, for example, that they may be fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood by those skilled in the art according to specific situations.
It is further noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, 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. The term "comprising", without further limitation, means that the element so defined is not excluded from the group consisting of additional identical elements in the process, method, article, or apparatus that comprises the element.
The above examples are only for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A domain name resolution method based on a graph view is characterized by comprising the following steps:
grouping a plurality of views to be processed in different forms according to preset service requirements of different areas to obtain view groups respectively corresponding to the different areas, and establishing a relationship between area names of the different areas and the view groups;
establishing an associated IP address set for each view;
determining the relationship between the area name and each view according to the relationship between the area name and each view group and the relationship between each view group and each view, and establishing a related area set for each view according to the relationship between the area name and each view, wherein the area set comprises one or more area units, each area unit is provided with corresponding area data or a corresponding area data index, the area data index is the number of other views in the same view group where the corresponding view is located, and the area data index is used for guiding and searching for corresponding area data shared by the same view group; whether each zone unit in the zone set is provided with corresponding zone data or a corresponding zone data index is determined by the relation between the zone files and the corresponding views in the preset service requirement of the zone;
determining a target view corresponding to a DNS request message to be subjected to domain name resolution according to a source IP of the DNS request message and an IP address set associated with each view;
and determining corresponding zone data according to the zone set associated with the target view and the domain name to be queried in the DNS request message, and performing domain name resolution on the DNS request message according to the determined zone data.
2. The method according to claim 1, wherein the grouping of the different forms of the multiple views to be processed according to the preset service requirements of the different regions to obtain view groups respectively corresponding to the different regions, and establishing the relationship between the region names of the different regions and the view groups comprises:
numbering each view to be processed in sequence, grouping the views in different forms according to preset service requirements of different areas to obtain view groups respectively corresponding to the different areas; wherein the view group comprises a view group consisting of more than two views, or a view group consisting of one or more single views and a view group; the view with the smallest number in each view group is the group leader view, and the other views are the group member views.
3. The method according to claim 2, wherein the relationship between the area name and each view is determined according to the relationship between the area name and each view group and the relationship between each view group and each view, and an associated area set is established for each view according to the relationship between the area name and each view, the area set comprises one or more area units, each area unit is provided with corresponding area data or a corresponding area data index, the area data index is a number of other views in the same view group where the corresponding view is located, and the area data index is used for guiding to search for corresponding area data shared by the same view group; whether each zone unit in the zone set is provided with corresponding zone data or a corresponding zone data index is determined by the relationship between the zone files and the corresponding views in the preset service requirement of the zone, and the method comprises the following steps:
determining the relationship between the area name and each view according to the relationship between the area name and each view group and the relationship between each view group and each view, and establishing a related area set for each view according to the relationship between the area name and each view, wherein the area set comprises one or more area units; each zone unit comprises three items of content, namely a zone name, zone data and a view number;
when loading the zone file of the corresponding zone, if the zone file of the zone needs to be configured on a single view according to the preset service requirement of the zone, generating a zone unit, wherein the zone unit comprises the zone name of the zone, the zone data of the zone and the view number of the single view, and adding the generated zone unit into a zone set corresponding to the single view;
if the zone file of the zone needs to be configured on a view group according to the preset service requirement of the zone, generating a zone unit, wherein the zone unit comprises a zone name of the zone, zone data of the zone and a view number of a group length view of the view group, and adding the generated zone unit into a zone set corresponding to the group length view; and simultaneously generating another area unit, wherein the area unit comprises the area name and the null data of the area and the view number of the group length view of the view group, and sequentially adding the generated area unit to an area set corresponding to each group member view of the view group.
4. The method according to claim 3, wherein the determining, according to the zone set associated with the target view and the domain name to be queried in the DNS request message, corresponding zone data, and performing domain name resolution on the DNS request message according to the determined zone data includes:
acquiring a zone unit matched with the domain name to be inquired from the zone set associated with the target view according to the zone set associated with the target view and the domain name to be inquired in the DNS request message, and if zone data in the matched zone unit is not null data, directly utilizing the zone data in the matched zone unit to carry out domain name resolution on the DNS request message; and if the zone data in the matched zone unit is null data, acquiring the zone unit matched with the domain name to be inquired from the zone set of the group leader view corresponding to the group leader view number according to the third content group leader view number in the matched zone unit, and performing domain name resolution on the DNS request message by using the zone data in the zone unit matched in the zone set of the group leader view.
5. The method of claim 4, further comprising:
and if the zone unit matched with the domain name to be inquired is not obtained from the zone set associated with the target view according to the domain name to be inquired in the DNS request message, responding to a refusal message.
6. The method according to any one of claims 1 to 5, wherein the preset service requirement comprises: the service division is carried out according to the operator, the service division is carried out according to the region, and the service division is carried out according to the region and the operator.
7. The method according to any one of claims 1 to 5, wherein the determining a target view corresponding to the DNS request message according to a source IP of the DNS request message to be subjected to domain name resolution and an IP address set associated with each view includes:
and according to the source IP of the DNS request message to be subjected to domain name resolution and the IP address set associated with each view, retrieving the IP address set associated with each view according to the longest matching principle, and determining a target view corresponding to the DNS request message.
8. A domain name resolution device based on a graph view, comprising:
the grouping module is used for grouping a plurality of views to be processed in different forms according to preset service requirements of different areas to obtain view groups respectively corresponding to the different areas, and establishing the relationship between the area names of the different areas and the view groups;
the first establishing module is used for establishing an associated IP address set for each view;
the second establishing module is used for determining the relationship between the area name and each view according to the relationship between the area name and each view group and the relationship between each view group and each view, and establishing a related area set for each view according to the relationship between the area name and each view, wherein the area set comprises one or more area units, each area unit is provided with corresponding area data or a corresponding area data index, the area data index is the number of other views in the same view group where the corresponding view is located, and the area data index is used for guiding and searching for corresponding area data shared by the same view group; whether each zone unit in the zone set is provided with corresponding zone data or a corresponding zone data index is determined by the relation between the zone files and the corresponding views in the preset service requirement of the zone;
the determining module is used for determining a target view corresponding to the DNS request message according to a source IP of the DNS request message to be subjected to domain name resolution and an IP address set associated with each view;
and the resolution module is used for determining corresponding zone data according to the zone set associated with the target view and the domain name to be queried in the DNS request message, and performing domain name resolution on the DNS request message according to the determined zone data.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the program implements the steps of the graphical view based domain name resolution method according to any of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the graphical view based domain name resolution method according to any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811492916.8A CN109788080B (en) | 2018-12-07 | 2018-12-07 | Domain name resolution method and device based on graph view, electronic equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811492916.8A CN109788080B (en) | 2018-12-07 | 2018-12-07 | Domain name resolution method and device based on graph view, electronic equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109788080A CN109788080A (en) | 2019-05-21 |
| CN109788080B true CN109788080B (en) | 2021-09-21 |
Family
ID=66496088
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811492916.8A Active CN109788080B (en) | 2018-12-07 | 2018-12-07 | Domain name resolution method and device based on graph view, electronic equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109788080B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114124887B (en) * | 2021-11-29 | 2023-09-05 | 牙木科技股份有限公司 | View query method of DNS server, DNS server and readable storage medium |
| CN116389411B (en) * | 2023-06-07 | 2023-08-18 | 阿里巴巴（中国）有限公司 | Domain name data processing method, device and equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103731516A (en) * | 2014-01-24 | 2014-04-16 | 互联网域名***北京市工程研究中心有限公司 | DNS (Domain Name Server) analysis method based on nested view and DNS analysis system based on nested view |
| CN105611000A (en) * | 2016-03-31 | 2016-05-25 | 中国互联网络信息中心 | DNS (domain name system) domain name rapid search method of domain name server |
| CN105635343A (en) * | 2016-02-02 | 2016-06-01 | 中国互联网络信息中心 | IP address list storage and query method applied to DNS query |
| CN106506729A (en) * | 2017-01-11 | 2017-03-15 | 中国互联网络信息中心 | A kind of DNS policy resolution method and devices based on DNS views |
| CN108881516A (en) * | 2018-07-27 | 2018-11-23 | 网宿科技股份有限公司 | A kind of method and apparatus for dispatching more CDN service systems |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TWI223942B (en) * | 2001-02-20 | 2004-11-11 | Li Jian Min | Contents transmission network system and creating method thereof |
| US7843911B2 (en) * | 2005-11-15 | 2010-11-30 | Nominum, Inc. | Data grouping approach to telephone number management in domain name systems |
-
2018
- 2018-12-07 CN CN201811492916.8A patent/CN109788080B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103731516A (en) * | 2014-01-24 | 2014-04-16 | 互联网域名***北京市工程研究中心有限公司 | DNS (Domain Name Server) analysis method based on nested view and DNS analysis system based on nested view |
| CN105635343A (en) * | 2016-02-02 | 2016-06-01 | 中国互联网络信息中心 | IP address list storage and query method applied to DNS query |
| CN105611000A (en) * | 2016-03-31 | 2016-05-25 | 中国互联网络信息中心 | DNS (domain name system) domain name rapid search method of domain name server |
| CN106506729A (en) * | 2017-01-11 | 2017-03-15 | 中国互联网络信息中心 | A kind of DNS policy resolution method and devices based on DNS views |
| CN108881516A (en) * | 2018-07-27 | 2018-11-23 | 网宿科技股份有限公司 | A kind of method and apparatus for dispatching more CDN service systems |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109788080A (en) | 2019-05-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| RU2400806C2 (en) | Organisation of mating requests for resource with according resources | |
| US6553368B2 (en) | Network directory access mechanism | |
| US8055788B1 (en) | Efficient person search mechanism in peer-to-peer networks | |
| CN1764171A (en) | Rendezvousing resource requests with corresponding resources | |
| CN109729187B (en) | Proxy communication method, system, device and storage medium | |
| EP3461226B1 (en) | Home gateway and forwarding service method thereof | |
| CN109788080B (en) | Domain name resolution method and device based on graph view, electronic equipment and medium | |
| JP6865763B2 (en) | Data processing method and equipment | |
| CN110336730B (en) | Network system and data transmission method | |
| CN114024886B (en) | Cross-resource-pool network intercommunication method, electronic equipment and readable storage medium | |
| US20240171509A1 (en) | Method and device for identification management and optimized forwarding in large-scale polymorphic network | |
| CN113645304A (en) | Data service processing method and related equipment | |
| WO2019071995A1 (en) | Content distribution method, device and system | |
| WO2007085167A1 (en) | A method, system and application of implementing an identification of a service based on an address | |
| US20160239499A1 (en) | Object Creation Based on Copying Objects Corresponding to Similar Entities | |
| CN116982307A (en) | Method and computing device for enforcing functional filtering rules in a clustered infrastructure | |
| CN106028311A (en) | Terminal register method and device | |
| CN105207904A (en) | Message processing method, device and router | |
| CN111078773A (en) | Data processing method and device | |
| CN114157633B (en) | Message forwarding method and device | |
| KR100720190B1 (en) | Fast rule lookup with arbitrary ip range configurations | |
| CN116016448A (en) | Service network access method, device, equipment and storage medium | |
| CN112910776B (en) | Data forwarding method, device, equipment and medium | |
| CN114356575A (en) | User request processing method and device | |
| CN115004657B (en) | Addressing method, addressing system and addressing device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |