CN114244805B - Domain name configuration method and device - Google Patents
Domain name configuration method and device Download PDFInfo
- Publication number
- CN114244805B CN114244805B CN202111315998.0A CN202111315998A CN114244805B CN 114244805 B CN114244805 B CN 114244805B CN 202111315998 A CN202111315998 A CN 202111315998A CN 114244805 B CN114244805 B CN 114244805B
- Authority
- CN
- China
- Prior art keywords
- domain name
- candidate resource
- resource
- screening
- matching
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
- H04L61/3015—Name registration, generation or assignment
- H04L61/3025—Domain name generation or assignment
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application discloses a domain name configuration method and device, wherein the method comprises the following steps: configuring a resource matching rule for a target domain name, wherein the resource matching rule comprises one or more groups of binding matching conditions and an execution strategy; the matching condition is used for limiting an IP address set to which the resource matching rule is applicable; the execution strategy is used for screening available candidate resource nodes from a plurality of candidate resource nodes, and determining the priority of each candidate resource node so as to allocate one or more available candidate resource nodes to a client accessing the target domain name based on the determined priority. The technical scheme provided by the application can improve the configuration efficiency of the DNS records, simplify the complexity of configuration management and improve the scheduling flexibility.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a domain name configuration method and device.
Background
In the current domain name resolution process, after receiving a domain name resolution request sent by a client, a domain name resolution server provides a corresponding IP address for the client according to a mapping relationship between a preconfigured domain name and the IP address. In this way, the client may obtain access resources from the corresponding resource node according to the received IP address.
To provide stable services to users, domain name vendors typically deploy multiple resource nodes. Thus, in order to provide the IP address of the appropriate resource node for the user, the IP address of the optional resource node is usually configured in the domain name resolution server in advance, and then the corresponding resource node is provided for the client by means of load balancing or random allocation.
However, in the existing domain name configuration method, a great deal of manpower is required to maintain a mapping table between the domain name and the IP address, and when the domain name configuration is changed or updated, for example, the mapping relationship between the domain name and the IP address of the resource node is changed, the updated configuration result needs to be pushed to all edge nodes, and the domain name configuration management is complex and the scheduling is inflexible.
Disclosure of Invention
The application aims to provide a domain name configuration method and device, which can improve domain name configuration efficiency, simplify configuration management complexity and improve scheduling flexibility.
In order to achieve the above object, an aspect of the present application provides a domain name configuration method, including: configuring a resource matching rule for a target domain name, wherein the resource matching rule comprises one or more groups of binding matching conditions and an execution strategy; the matching condition is used for limiting an IP address set to which the resource matching rule is applicable; the execution strategy is used for screening available candidate resource nodes from a plurality of candidate resource nodes, and determining the priority of each candidate resource node so as to allocate one or more available candidate resource nodes to a client accessing the target domain name based on the determined priority.
In order to achieve the above object, another aspect of the present application further provides a domain name configuration device, where the domain name configuration device includes a memory and a processor, and the memory is configured to store a computer program, where the computer program is executed by the processor to implement the domain name configuration method described above.
From the foregoing, it can be seen that, in the technical solutions provided in one or more embodiments of the present application, a resource matching rule may be configured in advance for a domain name, where the resource matching rule may include a matching condition and a corresponding execution policy. The domain name resolution request can be compared with each matching condition, so that the matched target matching condition is determined. The target execution policy with the target matching condition bound may screen out the resource nodes that are suitable for the domain name resolution request from among the plurality of resource nodes. By providing the IP address of the resource node to the client that initiated the domain name resolution request, the domain name resolution process can be completed. In the prior art, the resolution result of the domain name is usually deployed in the domain name resolution server, and once the resolution result is changed, the domain name resolution server needs to update the resolution result synchronously. The technical scheme provided by the application does not need to configure the analysis result in the domain name analysis server, but configures the resource matching rule, and then the appropriate resource node can be queried from a plurality of resource nodes based on the resource matching rule. Generally, the resource matching rule does not change along with the change of a single analysis result, so that the configuration information in the domain name analysis server does not need to be frequently updated, the complexity of configuration management is greatly simplified, and meanwhile, the resource node is screened based on the resource matching rule, so that the scheduling flexibility is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a resource matching rule in an embodiment of the present application;
FIG. 2 is a flow chart of a domain name configuration method in an embodiment of the application;
fig. 3 is a schematic diagram of an IP address set corresponding to a constraint in an embodiment of the present application;
FIG. 4 is a schematic diagram of functional blocks of a domain name resolution system according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a domain name resolution apparatus according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a domain name configuration apparatus in an embodiment of the present application.
Detailed Description
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 in conjunction with the detailed description of the present application and the corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present application without making any inventive effort, are intended to fall within the scope of the present application.
In the present application, resource matching rules may be preconfigured for different domain names. One or more sets of bound matching conditions and execution policies may be included in the resource matching rules. Wherein, the matching condition can be represented by M, and the execution strategy can be represented by CAPS according to different operators. Wherein C may represent a filter operator, A may represent an available judgment operator, P may represent a priority operator, and S may represent a selection operator. Thus, the matching condition and the execution strategy can form one MCAPS record, and a plurality of MCAPS records can be included in the same resource matching rule.
For example, for a target domain name, the configured resource matching rules may be as shown in FIG. 1. In the resource matching rule, four MCAPS records may be included. Wherein the matching condition in each MCAPS record may comprise at least one of a geographical location (region), an autonomous domain (autonomous system, as), an operator (isppgroup). For example, in the first MCAPS record, the geographical location and the operator's restrictions may be included, while in the second through fourth MCAPS records, only the geographical location restrictions may be included. Of course, in practical application, the MCAPS record may not include any constraint, in which case, the MCAPS may serve an IP address field where any client is located or an IP address of a recursive server.
The domain name configuration method provided in one embodiment of the present application may include a plurality of steps as shown in fig. 2.
S1: and configuring a resource matching rule for the target domain name, wherein the resource matching rule comprises one or more groups of binding matching conditions and execution strategies.
S3: the matching condition is used for limiting an IP address set to which the resource matching rule is applicable.
S5: the execution strategy is used for screening available candidate resource nodes from a plurality of candidate resource nodes, and determining the priority of each candidate resource node so as to allocate one available candidate resource node to a client accessing the target domain name based on the determined priority.
In this embodiment, the domain name resolution server may configure a corresponding resource matching rule for the target domain name according to the foregoing manner, so that after receiving the domain name resolution request, the domain name resolution server may identify the resource matching rule corresponding to the domain name to be resolved according to the domain name to be resolved included in the domain name resolution request. In the resource matching rule, each constraint within the matching condition may correspond to a set of IP addresses. For example, for a defined condition of a geographic location, it is the set of individual IP addresses that are located within the geographic location that corresponds. One or more limiting conditions in the matching conditions can correspond to one or more IP address sets, and the IP address set corresponding to the intersection of the limiting conditions can be used as the IP address set limited by the matching conditions. For example, in fig. 3, the set of IP addresses in the shaded portion of fig. 3 may be obtained from the intersection of three constraints, geographic location, autonomous domain, and operator.
The set of IP addresses defined by the matching condition may be used as a reference basis for whether the matching condition is applicable to the current domain name resolution request. Specifically, if the domain name resolution request includes an IP address field where the client is located, and the IP address field where the client is located in the IP address set defined by the matching condition, then the matching condition is indicated to be applicable to the current domain name resolution request. For another example, if the IP address of the recursive server is in the set of IP addresses defined by the matching condition, the matching condition is also indicated to be applicable to the current domain name resolution request, provided that the domain name resolution request does not carry the IP address segment where the client is located, but carries the IP address of the recursive server in the domain name resolution process.
In the resource matching rule, each MCAPS record may have a certain arrangement sequence, and when determining a matching condition applicable to the domain name resolution request, it may sequentially determine whether the IP address of the recursive server or the IP address field where the client is located in the IP address set defined by the current matching condition according to the arrangement sequence. If the matching condition is located, the current matching condition can be used as a target matching condition matched with the domain name resolution request.
For example, in fig. 1, the domain name resolution request carries the IP address of the recursive server, which is located in the Xiamen and which is served by the telecommunications. Thus, the domain name resolution request hits the first MCAPS record, and the matching condition in the first MCAPS record is the matching condition for the adaptation.
In this embodiment, after determining the target matching condition adapted to the domain name resolution request, a corresponding resource node may be allocated to the domain name resolution request according to the target execution policy bound to the target matching condition.
Specifically, the target execution policy may include four operators, such as CAPS, where each operator may undergo respective processing, so as to finally obtain which resource node should be fed back to the domain name resolution request.
Wherein, the filtering operator C (candidate) can generate a candidate list according to the matching condition, and the candidate list comprises candidate resource nodes determined from a resource node pool. A plurality of defined conditions in the matching conditions may be passed to the screening operator by an expression. In this expression, two kinds of arithmetic logic of "or" and "may be included. Different arithmetic logic may be represented in different forms. For example, a particular expression may be expressed as:
[[“sr:as.xm”,“sr:as.tw”],[“app:cs”]]
where sr: as.xm may define the geographical location "Xiamen" and sr: as.tw may define the geographical location "taiwan", the two geographical locations being located in the same bracket, and the bracket being the bracket of the innermost layer, the selection relationship between the two geographical locations may be "or". app:cs denotes a cache server. It can be seen that the innermost brackets define the geographic location and server type, respectively, and that the brackets in the two groups may be in an "and" relationship. That is, by the above expression, it is necessary to screen out the cache server located in Xiamen or Taiwan.
In this embodiment, each resource node may have a tag (tag) corresponding to itself, where the tag may represent a geographic location where the resource node is located, an operator supported by the resource node, a server type corresponding to the resource node, and so on. By comparing the above expression with the labels of the respective resource nodes, resource nodes conforming to the above expression can be screened out.
In practical applications, the above expression may also take more forms, for example, it may comprise a combination of a negative sign and a defined condition, wherein the negative sign precedes the defined condition. Specifically, a "-" label may be employed to indicate a negative meaning. By marking the "to" label before the limiting condition, it can be indicated that other resource nodes than the resource node defined by the limiting condition can be used as the resource node for providing the service. For example, an expression with a "-" label may be expressed as:
[[“～sr:as.cn.fj.xm”,“sr:as.cn.fj”],[“app:cs”]]
the expression represents a cache server (app: cs) of other fowls provinces (cn.fj) except for the Xiamen (cn.fj.xm).
It can be seen that, based on the screening operator, a candidate list can be generated in which candidate resource nodes determined from a pool of resource nodes can be included. The candidate list obtained in the above example includes resource nodes of cache servers in Xiamen or Taiwan.
In this embodiment, after determining candidate resource nodes based on the filtering operator, whether each candidate resource node is Available may be determined according to the Available determining operator a (Available). In particular, the availability judgment operator may identify producers associated with a candidate resource node and, in the event that each of the producers is available, judge that the candidate resource node is available. The producer associated with the candidate resource node may refer to a router/switch connected to the candidate resource node, a machine room where the candidate resource node is located, an access point cluster where the candidate resource node is located, and so on. To ensure availability of a candidate resource node, it may be determined that the candidate resource node is available when both of these associated producers are available.
In this embodiment, after determining available candidate resource nodes, the Priority of each candidate resource node may be determined according to a Priority operator P (Priority), so that one of the available candidate resource nodes is allocated to the domain name resolution request based on the determined Priority.
In practical applications, the domain name resolution request may carry an IP address field where the client is located, or may not carry an IP address field where the client is located, but carries an IP address of a recursive server that is in communication with the client. Based on different IP addresses, clusters of different candidate resource nodes may be obtained. For example, for a domain name resolution request carrying an IP address of a client, an available candidate resource node may be obtained through accurate node probing, or a matching candidate resource node may be obtained only through identification of a geographic location. The manner of accurate node detection can be recorded as PROBE, and the manner of geographic location based identification can be recorded as GEO. Thus, two different node screening modes, namely ECS-PROBE and ECS-GEO, can be provided for the IP address field (marked as ECS) where the client is located. Similarly, for the IP address of the recursive server (denoted as LIP), there are two different node screening approaches, LIP-PROBE and LIP-GEO. In general, the accuracy of the resource nodes obtained based on the client IP address and the accurate probing method is obviously higher, so the priority of the four node screening methods from high to low can be expressed as: ECS-PROBE > LIP-PROBE > ECS-GEO > LIP-GEO.
The above priority is adopted for different candidate resource nodes, and the confidence level of different screening modes can be combined to comprehensively measure. That is, a screening manner of each of the candidate resource nodes may be determined and a confidence level of the screening manner may be identified to set a priority of the candidate resource node based on the confidence level and the screening manner.
Specifically, if the candidate resource node is obtained by screening based on the IP address field where the client is located and the current confidence level meets the preset condition, the candidate resource node may be classified into the first priority.
And if the candidate resource node is obtained based on the screening of the IP address of the recursion server and the current confidence coefficient meets the preset condition, the candidate resource node can be divided into a second priority.
When the two priorities are not satisfied, whether the candidate resource node is obtained by screening based on the IP address field where the client is located can be judged, if so, the candidate resource node can be classified into a third priority, and if the IP address field where the client is located has a corresponding geographic position label.
If the candidate resource node is obtained based on the filtering of the IP address of the recursive server, and the IP address of the recursive server has a corresponding geographic location tag, the candidate resource node may be classified into the fourth priority.
If none of the above cases belong, the candidate resource node may be classified as a fifth priority.
For different candidate resource nodes, the priority operator P may perform the above processing, so as to determine the priority of the candidate resource node.
In one embodiment, the confidence level of the above screening method may be determined by:
and aiming at the IP addresses defined by the screening mode, if the number of the effectively detected access points reaches a specified number threshold, judging that the screening mode is credible.
The meaning of effective detection may mean that the detection time of the access point is not expired, wherein the expiration time may be 6 hours, and may be flexibly set in practical application, for example, may be 24 hours. The number threshold may be flexibly set according to actual requirements, for example, may be set to 14.
In addition, for the IP address defined by the screening mode, if a specified number of access points exist, and the detection method of each access point is in a preset list, the screening mode is determined to be credible.
The specified number of access points may be the top three access points, and the probing methods in the preset list may be, for example, ICMP probing methods and UDP probing methods.
In addition, for the IP address defined by the screening mode, if the detection result is in a preset range, the screening mode is determined to be credible.
The detection result may be an RTT (Round-Trip Time) value, and the preset range may be, for example, 0 to 2000ms.
In practical application, when the above three conditions meet one of them, the screening mode may be considered as trusted, and of course, when all the above three conditions are met, the screening mode may be considered as trusted, which is not limited in the present application.
In this embodiment, after determining the priority of each candidate resource node by the priority operator P, the IP address of the target resource node fed back to the client may be determined by the selection operator S (selection). In practical application, the selection operator S may take the candidate resource node with the highest priority as the feedback target resource node, and if there are multiple candidate resource nodes with the highest priority, the candidate resource node with the best performance and the most idle may be screened out according to the load balancing policy. After the target resource node is determined, the domain name resolution device can feed back the IP address of the target resource node to the client, and the client can initiate resource access to the target resource node.
In one embodiment, the same domain name is considered, and may be configured according to different network types (e.g., IPv4 and IPv 6). The supported candidate resource nodes may also be different for different network types. In view of this, different resource matching rules may be generated for the domain name for different network types. After receiving the domain name resolution request for the domain name, the network type corresponding to the domain name resolution request can be judged, so that the corresponding resource matching rule can be selected for screening the resource nodes.
In one embodiment, most domain names may have underlying resource matching rules, while some domain names may be adjusted for some particular region. In view of this, a final resource matching rule for the domain name can be generated by inheritance.
In particular, one domain name may be provided with an initial resource matching rule, and the domain name may choose whether to inherit the resource matching rule from another domain name (inherited domain name). If the resource matching rule can be inherited from the inherited domain name, when the policy element is missing in the resource matching rule of a certain target domain name, the missing policy element can be inherited from the resource matching rule corresponding to the inherited domain name in the policy inheritance relationship. The policy element may be any element in MCAPS. When inheriting the missing policy element from the inherited domain name, a conflict may occur with other policy elements that exist themselves. For example, filter operator C may conflict. In this case, if the policy element inherited is a filter operator, a filter operator override (override) in the resource matching rule of the inherited domain name is used as the filter operator in the resource matching rule of the target domain name. Of course, depending on the application scenario, when the policy element is inherited, the methods of intersection (intersection), union (unit) and the like may be adopted, and are not limited to the heavy load method.
In one embodiment, if the missing policy element does not exist in the resource matching rule corresponding to the inherited domain name, the missing policy element may be inherited from a global default rule. The configuration of the target domain name is realized in an inheritance mode, so that the configuration information of the target domain name is partially or completely inherited from the inherited domain name, if some personalized settings are required for the configuration information of the target domain name, the corresponding configuration items can be directly added or modified in the configuration information of the target domain name, the inherited configuration information is not affected in the process, and the customization and personalized configuration of the configuration information are increased. In addition, if the content in the configuration information of the inherited domain name is changed and the changed content is inherited into the new configuration information, the content in the new configuration information is changed accordingly, so if the configuration information of a plurality of domain names with inheritance relations needs to be uniformly modified, only the content of the inherited configuration information needs to be modified, the modified content takes effect on the configuration items in the configuration information of other domain names with inheritance relations according to the inheritance relations, the configuration information of the inherited domain names does not need to be modified one by one, the domain name configuration complexity is greatly simplified, and the domain name configuration efficiency is improved.
Referring to fig. 4, the present application further provides a domain name resolution system, where the domain name resolution system includes:
the device comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving a domain name resolution request, and the domain name resolution request comprises a domain name to be resolved;
the rule acquisition unit is used for acquiring a resource matching rule corresponding to the domain name to be resolved, wherein the resource matching rule comprises a binding matching condition and an execution policy;
the node allocation unit is used for determining a target matching condition matched with the domain name resolution request in the resource matching rule, and allocating resource nodes for the domain name resolution request based on a target execution strategy bound with the target matching condition.
Referring to fig. 5, the present application further provides a domain name resolution device, where the domain name resolution device includes a memory and a processor, and the memory is configured to store a computer program, and when the computer program is executed by the processor, implement the domain name resolution method described above.
Referring to fig. 6, the present application further provides a domain name configuration device, where the domain name configuration device includes a memory and a processor, and the memory is configured to store a computer program, and when the computer program is executed by the processor, implement the domain name configuration method described above.
In the present application, the memory may include physical means for storing information, typically by digitizing the information before storing it in a medium using electrical, magnetic or optical methods. The memory may in turn comprise: means for storing information by means of electrical energy, such as RAM or ROM; means for storing information using magnetic energy, such as hard disks, floppy disks, magnetic tape, magnetic core memory, bubble memory, or U disk; devices for storing information optically, such as CDs or DVDs. Of course, there are other ways of storing, such as quantum storage or graphene storage, etc.
In the present application, the processor may be implemented in any suitable manner. For example, the processor may take the form of, for example, a microprocessor or processor, and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), a programmable logic controller, and an embedded microcontroller, among others.
From the foregoing, it can be seen that, in the technical solutions provided in one or more embodiments of the present application, a resource matching rule may be configured in advance for a domain name, where the resource matching rule may include a matching condition and a corresponding execution policy. The domain name resolution request can be compared with each matching condition, so that the matched target matching condition is determined. The target execution policy with the target matching condition bound may screen out the resource nodes that are suitable for the domain name resolution request from among the plurality of resource nodes. By providing the IP address of the resource node to the client that initiated the domain name resolution request, the domain name resolution process can be completed. In the prior art, the resolution result of the domain name is usually deployed in the domain name resolution server, and once the resolution result is changed, the domain name resolution server needs to update the resolution result synchronously. The technical scheme provided by the application does not need to configure the analysis result in the domain name analysis server, but configures the resource matching rule, and then the appropriate resource node can be queried from a plurality of resource nodes based on the resource matching rule. Generally, the resource matching rule does not change along with the change of the analysis result, so that the content in the domain name analysis server does not need to be frequently updated, the complexity of configuration management is greatly simplified, and meanwhile, the resource node is screened based on the resource matching rule, so that the scheduling flexibility is improved.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are referred to each other, and each embodiment is mainly described as different from other embodiments. In particular, reference may be made to the description of embodiments of the method described above for both embodiments of the system and apparatus.
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 application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. 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 description is only illustrative of the application and is not to be construed as limiting the 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 (16)
1. A domain name configuration method, the method comprising:
configuring a resource matching rule for a target domain name, wherein the resource matching rule comprises one or more groups of binding matching conditions and an execution strategy;
defining an IP address set applicable to the resource matching rule by limiting conditions of the matching conditions, wherein the IP address set is an IP address set corresponding to an intersection of the limiting conditions;
the execution strategy is used for generating a plurality of candidate resource nodes, judging whether each candidate resource node is available or not, screening available candidate resource nodes from the plurality of candidate resource nodes, determining the priority of each candidate resource node according to the screening mode of each candidate resource node, and distributing one or more available candidate resource nodes to a client accessing the target domain name based on the determined priority; in the process of determining the priority of each candidate resource node, if the screening modes of the candidate resource nodes are different, the priorities corresponding to the candidate resource nodes are different.
2. The method according to claim 1, wherein the matching condition includes at least one of a geographical location, an autonomous domain, and an operator.
3. The method of claim 1, wherein the execution policy includes a filtering operator, the filtering operator configured to generate a candidate list according to the matching condition, the candidate list including candidate resource nodes determined from a pool of resource nodes.
4. A method according to claim 3, wherein the matching condition comprises one or more defined conditions, the defined conditions being used to characterize candidate resource nodes meeting the matching condition, and different defined conditions being connected to each other by arithmetic logic.
5. A method according to claim 3, wherein the matching condition comprises a combination of a negative flag and a limiting condition, wherein the negative flag is located before the limiting condition and is used for characterizing other resource nodes than the resource node defined by the limiting condition.
6. The method of claim 1, wherein the execution policy includes an available judgment operator, the available judgment operator being used to identify producers associated with candidate resource nodes, and to judge that the candidate resource nodes are available if each of the producers is available; the producer associated with the candidate resource node comprises a router or a switch connected with the candidate resource node, a machine room where the candidate resource node is located and an access point cluster where the candidate resource node is located.
7. The method of claim 1, wherein the execution policy includes a priority operator, the priority operator being configured to determine a screening manner for each candidate resource node, and identify a confidence level of the screening manner, to set a priority of the candidate resource node based on the confidence level and the screening manner.
8. The method of claim 7, wherein prioritizing the candidate resource nodes based on the confidence level and the screening manner comprises:
if the candidate resource nodes are obtained based on screening of the IP address field where the client is located and the current confidence degree meets the preset condition, dividing the candidate resource nodes into a first priority;
and if the candidate resource nodes are obtained based on the screening of the IP address of the recursion server and the current confidence degree meets the preset condition, dividing the candidate resource nodes into a second priority.
9. The method of claim 7 or 8, wherein identifying the confidence level of the screening method comprises:
for the IP addresses defined by the screening mode, if the number of the effectively detected access points reaches a specified number threshold, judging that the screening mode is credible;
or alternatively
For the IP addresses defined by the screening mode, if a specified number of access points exist, and the detection method of each access point is in a preset list, judging that the screening mode is credible;
or alternatively
And aiming at the IP address limited by the screening mode, if the detection result is in a preset range, judging that the screening mode is credible.
10. The method according to claim 1, wherein the method further comprises:
if the strategy element is missing in the resource matching rule of the target domain name, inheriting the missing strategy element from the resource matching rule corresponding to the inherited domain name in the strategy inheritance relation.
11. The method according to claim 10, wherein the method further comprises:
and if the missing policy element does not exist in the resource matching rule corresponding to the inherited domain name, inheriting the missing policy element from a global default rule.
12. The method of claim 10, wherein in inheriting the missing policy element, the method further comprises:
and if the inherited strategy element is a screening operator, reloading the screening operator in the resource matching rule of the inherited domain name as the screening operator in the resource matching rule of the target domain name.
13. The method according to claim 1, wherein the method further comprises:
receiving a domain name resolution request, wherein the domain name resolution request comprises a domain name to be resolved;
acquiring a resource matching rule corresponding to the domain name to be resolved;
and determining a target matching condition matched with the domain name resolution request in the resource matching rule, and distributing resource nodes for the domain name resolution request based on a target execution strategy bound with the target matching condition.
14. The method of claim 13, wherein the domain name resolution request further includes an IP address of a recursive server or an IP address field where the client is located;
determining, in the resource matching rule, a target matching condition that is adapted to the domain name resolution request includes:
according to the arrangement sequence of each matching condition in the resource matching rule, judging whether the IP address of the recursion server or the IP address segment of the client is positioned in the IP address set limited by the current matching condition in sequence; and if the matching condition is located, taking the current matching condition as a target matching condition matched with the domain name resolution request.
15. The method of claim 13, wherein allocating resource nodes for the domain name resolution request comprises:
and screening available candidate resource nodes from a plurality of candidate resource nodes, and determining the priority of each candidate resource node so as to allocate one or more available candidate resource nodes to the domain name resolution request based on the determined priority.
16. A domain name configuration device, characterized in that it comprises a memory and a processor, the memory being adapted to store a computer program which, when executed by the processor, implements the method according to any of claims 1 to 15.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111315998.0A CN114244805B (en) | 2021-11-08 | 2021-11-08 | Domain name configuration method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111315998.0A CN114244805B (en) | 2021-11-08 | 2021-11-08 | Domain name configuration method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114244805A CN114244805A (en) | 2022-03-25 |
| CN114244805B true CN114244805B (en) | 2023-10-03 |
Family
ID=80748691
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111315998.0A Active CN114244805B (en) | 2021-11-08 | 2021-11-08 | Domain name configuration method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114244805B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115225504B (en) * | 2022-06-10 | 2024-03-19 | 中国科学院信息工程研究所 | Resource allocation method, device, electronic equipment and storage medium |
| CN115834372A (en) * | 2022-11-21 | 2023-03-21 | 北京有竹居网络技术有限公司 | Node configuration method, device, equipment and medium for target address |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107071089A (en) * | 2017-05-18 | 2017-08-18 | 腾讯科技（深圳）有限公司 | Dispatch control method, device and system |
| CN107360269A (en) * | 2017-07-21 | 2017-11-17 | 中国移动通信集团江苏有限公司 | Domain name analysis system optimization method, device, equipment and storage medium |
| CN108234685A (en) * | 2017-12-20 | 2018-06-29 | 中国移动通信集团江苏有限公司 | Method, apparatus, equipment and the medium of user terminal gateway equipment DNS scheduling |
| CN109104506A (en) * | 2017-06-20 | 2018-12-28 | 腾讯科技（深圳）有限公司 | The determination method, apparatus and computer readable storage medium of domain name mapping rule |
| US10243919B1 (en) * | 2016-09-28 | 2019-03-26 | Amazon Technologies, Inc. | Rule-based automation of DNS service discovery |
| CN109862131A (en) * | 2019-02-20 | 2019-06-07 | 北京奇艺世纪科技有限公司 | Distribution method, device and the computer readable storage medium of server access address |
| CN110995888A (en) * | 2019-12-17 | 2020-04-10 | 互联网域名系统北京市工程研究中心有限公司 | Intelligent resolution method of domain name system |
| US10944714B1 (en) * | 2019-04-16 | 2021-03-09 | Amazon Technologies, Inc. | Multi-factor domain name resolution |
| CN112954089A (en) * | 2021-04-12 | 2021-06-11 | 平安科技（深圳）有限公司 | Method, device and equipment for analyzing data and storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111917829B (en) * | 2017-10-27 | 2022-06-14 | 华为技术有限公司 | Domain name access method and device |
| CN108494891A (en) * | 2018-02-28 | 2018-09-04 | 网宿科技股份有限公司 | A kind of domain name analytic method, server and system |
| US10681001B2 (en) * | 2018-03-29 | 2020-06-09 | Akamai Technologies, Inc. | High precision mapping with intermediary DNS filtering |
-
2021
- 2021-11-08 CN CN202111315998.0A patent/CN114244805B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10243919B1 (en) * | 2016-09-28 | 2019-03-26 | Amazon Technologies, Inc. | Rule-based automation of DNS service discovery |
| CN107071089A (en) * | 2017-05-18 | 2017-08-18 | 腾讯科技（深圳）有限公司 | Dispatch control method, device and system |
| CN109104506A (en) * | 2017-06-20 | 2018-12-28 | 腾讯科技（深圳）有限公司 | The determination method, apparatus and computer readable storage medium of domain name mapping rule |
| CN107360269A (en) * | 2017-07-21 | 2017-11-17 | 中国移动通信集团江苏有限公司 | Domain name analysis system optimization method, device, equipment and storage medium |
| CN108234685A (en) * | 2017-12-20 | 2018-06-29 | 中国移动通信集团江苏有限公司 | Method, apparatus, equipment and the medium of user terminal gateway equipment DNS scheduling |
| CN109862131A (en) * | 2019-02-20 | 2019-06-07 | 北京奇艺世纪科技有限公司 | Distribution method, device and the computer readable storage medium of server access address |
| US10944714B1 (en) * | 2019-04-16 | 2021-03-09 | Amazon Technologies, Inc. | Multi-factor domain name resolution |
| CN110995888A (en) * | 2019-12-17 | 2020-04-10 | 互联网域名系统北京市工程研究中心有限公司 | Intelligent resolution method of domain name system |
| CN112954089A (en) * | 2021-04-12 | 2021-06-11 | 平安科技（深圳）有限公司 | Method, device and equipment for analyzing data and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 基于策略的DNS及其配置;孙成英, 陈黎君;江苏通信技术;第23卷(第03期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114244805A (en) | 2022-03-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11172032B2 (en) | Private service endpoints in isolated virtual networks | |
| CN114244805B (en) | Domain name configuration method and device | |
| CN109643251B (en) | Resource oversubscription based on utilization patterns in computing systems | |
| US8438286B2 (en) | Methods and apparatus to allocate resources associated with a distributive computing network | |
| CN109684092B (en) | Resource allocation method and device | |
| US10104187B2 (en) | System, computer program, and method for dividing services into subsets based on interdependencies | |
| EP3192212A1 (en) | Policy enforcement in a topology abstraction system | |
| US8775629B1 (en) | System and method for managing internet protocol (IP) address space for enterprise network | |
| CN109327559B (en) | Domain name resolution method and device based on hybrid cloud platform | |
| US11228490B1 (en) | Storage management for configuration discovery data | |
| CN113676511B (en) | Cloud storage method, system, equipment and storage medium | |
| CN105357233A (en) | Remote call method and device | |
| US20170091252A1 (en) | Reconciling sensor data in a database | |
| CN113810230A (en) | Method, device and system for carrying out network configuration on containers in container cluster | |
| US10944714B1 (en) | Multi-factor domain name resolution | |
| CN110798507B (en) | Method and system for DHCP address allocation memory | |
| US20110153787A1 (en) | Information technology asset management | |
| US20230161634A1 (en) | Mapping an application signature to designated cloud resources | |
| US11736444B2 (en) | Cloud-based private area network | |
| US11303606B1 (en) | Hashing name resolution requests according to an identified routing policy | |
| US11120052B1 (en) | Dynamic distributed data clustering using multi-level hash trees | |
| CN114244696B (en) | Deployment method and configuration platform of configuration information | |
| US20240113968A1 (en) | Using crds to create externally routable addresses and route records for pods | |
| US11916766B1 (en) | Synthetic resource records | |
| CN112738271B (en) | CDN quality detection method, system and domain name server |
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 |