CN112671866A - DNS (Domain name Server) shunt analysis method, DNS server and computer readable storage medium - Google Patents
DNS (Domain name Server) shunt analysis method, DNS server and computer readable storage medium Download PDFInfo
- Publication number
- CN112671866A CN112671866A CN202011482918.6A CN202011482918A CN112671866A CN 112671866 A CN112671866 A CN 112671866A CN 202011482918 A CN202011482918 A CN 202011482918A CN 112671866 A CN112671866 A CN 112671866A
- Authority
- CN
- China
- Prior art keywords
- domain name
- dns
- record
- resolution
- target domain
- 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.)
- Granted
Links
Images
Abstract
The invention provides a DNS intelligent distribution analysis method, a DNS intelligent distribution analysis system and a computer readable storage medium, which can provide hierarchical service and solve the problem of a large amount of iterative flow generated when forwarding multilayer CNAME records. The invention provides an intelligent DNS distribution analysis method, which specifically comprises the following steps: step S1, classifying the target domain name; step S2, according to the classification of the target domain name, selecting a DNS server to analyze the target domain name; step S3, when the unspecified domain name is analyzed, if there is a domain name of the specified domain name in each level of domain names, the specified DNS server corresponding to the specified domain name is selected to analyze the specified domain name. The DNS intelligent distribution analysis method provided by the invention provides domain name classification service and solves the problem of a large amount of iterative flow generated when forwarding multi-layer CNAME records.
Description
Technical Field
The invention relates to the technical field of network communication, in particular to a DNS distribution analysis method, a DNS server and a computer readable storage medium.
Background
A Domain Name System (DNS) is a naming System having a hierarchical structure, and maps a Domain Name and an IP address with each other to form a distributed database System. The DNS servers in the DNS system are arranged according to a hierarchy, each DNS server only manages one part of the domain name system, and the DNS servers are divided into a root domain name server, a top level domain name server, an authority domain name server, a local domain name server and the like according to the functions of the DNS servers. Generally, when a DNS server receives a domain name resolution request generated when a user accesses a domain name, a plurality of layers of iterative queries are performed sequentially through a root domain name server, a top-level domain name server, an authority domain name server, a local domain name server, and the like, and a large amount of iterative traffic is generated for each layer of iterative queries of the DNS server.
When the domain name resolution result contains multiple layers of CNAME records (alias records) and address records (A records), the forwarding of the multiple layers of CNAME records layer by layer always iterates the first layer of CNAME records, thereby generating a large amount of iterative flow and further increasing the flow burden of the DNS server. If the domain name resolution result is directly returned without forwarding the multilayer CNAME records layer by layer, although the iteration flow can be reduced, the real-time performance and the accuracy of the domain name resolution result cannot be guaranteed.
Therefore, it is desirable to provide a technical solution, which can provide an accurate resolution service for a specified domain name and provide a resolution service without layer-by-layer iterative query for other domain names with low requirements on real-time performance and accuracy, so as to reduce a large amount of iterative traffic generated when a domain name resolution result includes multiple layers of CNAME records while ensuring the accuracy of the domain name resolution result.
Disclosure of Invention
Aiming at the problems, the invention provides a DNS distribution analysis method, which can provide accurate analysis service for the specified domain name and provide analysis service without layer-by-layer iterative query for other domain names with lower requirements on real-time performance and accuracy, so as to reduce a large amount of iterative flow generated when forwarding multi-layer CNAME records.
In the technical scheme of the invention, the invention provides a DNS shunt analysis method, which comprises the following steps:
step S1, receiving the analysis request of the user;
step S2, if the target domain name in the resolution request matches the preset domain/domain name, executing step S3, if not, executing step S4;
step S3, according to the processing method selected for the domain/domain name, alternatively execute S31 or S32:
step S31, forwarding the target domain name to the dedicated server to obtain the resolution result of the dedicated server for the target domain name,
step S32, performing a first iterative query on the target domain name to obtain an analysis result of the first iterative query for the target domain name;
and step S4, forwarding the target domain name to the public server to obtain the resolution result of the public server for the target domain name.
In the technical scheme of the invention, the DNS distribution analysis method realizes the classification of the target domain name through the steps, namely different domain names are matched with different analysis paths and analysis modes, and the flow distribution of DNS domain name analysis is preliminarily realized. And according to the requirements of users, configuring a domain/domain name and an exclusive server, a first iterative query mode and a public server, and providing exclusive forwarding/iterative service for the target domain name of the matched domain/domain name, thereby ensuring the accuracy of the target domain name resolution result of the matched domain/domain name.
In the DNS split-flow resolution method in the technical solution of the present invention, if the resolution result for the target domain name includes a CNAME record, the following is performed:
in step S5, if the alias in the CNAME record matches the preset domain/domain name, step S3 is executed, and if not, step S32 is executed.
Through step S5, when the alias in the resolved CNAME record of the target domain name matches the preset domain name, the dedicated forwarding/iterative service can be provided for the alias in the CNAME record, so that when the domain name of the resolution request is not the specified domain name, but the alias is the specified domain name, the resolution request can also be forwarded to the dedicated server for resolution.
In the DNS split-flow resolution method in the technical solution of the present invention, when step S4 is executed, if the resolution result of the public server for the target domain name includes the CNAME record and the a record, then:
and step S6, if the alias in the CNAME record is matched with the preset domain name, executing step S3, and if the alias is not matched with the preset domain name, returning the CNAME record and the A record to the user according to the forwarding trust switch.
Through step S6, the accuracy of the alias resolution result matching the preset domain name is ensured, and the CNAME record and the a record are directly returned to the user through the forwarding trust switch, thereby reducing a large amount of iterative traffic generated by forwarding multiple layers of CNAME records to the public server. Further, in the DNS splitting resolution method in the technical solution of the present invention, in step S6, if the resolution result has multiple layers of CNAME records and aliases in the multiple layers of CNAME records do not match with the preset domain name,
when the forwarding trust switch is turned on, directly returning the CNAME record and the A record to the user;
and when the forwarding trust switch is closed, forwarding the multilayer CNAME records layer by layer, and returning the analysis results obtained by layer forwarding to the user after arranging the analysis results.
In step S6, the forwarding trust switch can be selected to turn on and off by itself. When the forwarding trust switch is turned on, a large amount of iterative flow generated by forwarding the multilayer CNAME records when the alias unmatched with the preset domain name is analyzed can be reduced; when the forwarding trust switch is closed, a more accurate analysis result can be provided. The server manager can select the on/off of the forwarding trust switch by self to adapt to different requirements.
In step S5 or step S6 of the DNS split-flow resolution method provided in the technical solution of the present invention, if there are multiple layers of CNAME records in the resolution result and any alias in the multiple layers of CNAME records matches a preset domain name, step S3 is executed according to the alias matching the preset domain name. Therefore, a large amount of iterative flow generated by forwarding the multilayer CNAME records can be reduced, and accurate and fine analysis can be further carried out on the alias matched with the preset domain name.
In the DNS split-flow resolution method in the technical solution of the present invention, if the resolution result for the target domain name or the alias thereof does not include the CNAME record and includes the a record, the a record is returned to the user. Thus, the user can directly obtain the domain name resolution result.
In the DNS split resolution method according to the technical solution of the present invention, the target domain name includes: the target domain name, the alias in the CNAME record corresponding to the target domain name, and the alias in the CNAME record corresponding to the alias. Each layer of domain name and alias in the domain name resolution process are judged, whether the domain name and alias are matched with the preset domain name or not is not influenced by the multi-layer CNAME record iteration, and the domain name and alias are forwarded to the exclusive server as long as the domain name and the alias are matched with the preset domain name, so that the domain name matched with the preset domain name is guaranteed to obtain a finer and more accurate resolution result to the greatest extent.
In the DNS split-flow resolution method in the technical solution of the present invention, in step S4, if there is no CNAME record or a record in the resolution result obtained by forwarding the target domain name to the public server, the process goes to step S32 to perform the first iterative query and report the result as an abnormal result. The above steps can prevent the obtained resolution result from being incomplete and accurate due to the lack of the corresponding entry of the target domain name or the alias thereof in the cache of the public server, and the further first iteration query can also prevent missing the judgment of whether the alias in the domain name iteration process forwarded to the public server is matched with the preset domain name.
In the DNS split-flow resolution method in the technical solution of the present invention, in step S31, if there is no CNAME record or no a record in the resolution result, a second iterative query is performed, and in the second iterative query process, the iterative query is continued until the a record is queried. In step S31, the target domain name is matched with the preset domain name, and if the dedicated server has no CNAME record or a record in the resolution result for the target domain name, a second iterative query is performed, that is, the alias in the iterative process does not need to judge whether the alias is matched with the preset domain name, and the iterative query is performed until an accurate resolution result is obtained, so as to ensure the accuracy of the resolution result of the target domain name matched with the preset domain name.
The present invention also provides a DNS server, comprising:
a processor;
a memory communicatively connected to the processor, the memory having stored therein a computer program, the DNS server being capable of performing the following steps by reading and executing the computer program:
step S1, receiving the analysis request of the user;
step S2, if the target domain name in the resolution request matches the preset domain/domain name, executing step S3, if not, executing step S4;
step S3, according to the processing method selected for the domain/domain name, alternatively execute S31 or S32:
step S31, forwarding the target domain name to the dedicated server to obtain the resolution result of the dedicated server for the target domain name,
step S32, performing a first iterative query on the target domain name to obtain an analysis result of the first iterative query for the target domain name;
and step S4, forwarding the target domain name to the public server to obtain the resolution result of the public server for the target domain name.
The DNS server provided by the invention can grade the target domain name and allocate the analysis path and the analysis mode of the target domain name according to the grade of the target domain name. The DNS server grades the target domain name by judging whether the domain name is matched with a preset domain name or not, and the grading of the domain name can be defined according to different requirements.
The invention also provides a computer readable storage medium, on which a computer program is stored, and when being executed by a processor, the computer program implements the steps of implementing the DNS split resolution method, thereby providing a domain name classification service and reducing a large amount of iterative traffic generated when forwarding a multi-layer CNAME record.
Drawings
Fig. 1 is a schematic flow chart of a DNS split resolution method according to an embodiment of the present invention;
FIG. 2 is a flow diagram of an iteration of a multi-layer CNAME when a relay switch is closed in the embodiment of FIG. 1;
FIG. 3 is a flow diagram illustrating the multi-layer CNAME iteration when the relay switch is turned on in the embodiment of FIG. 1;
fig. 4 is a schematic structural diagram of a DNS server provided in another embodiment of the present invention.
Reference numerals: 1-DNS server, 2-processor, 3-memory.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without any creative effort belong to the protection scope of the present invention.
DNS domain name resolution is the process of converting a domain name to an IP address. The IP address is a numerical address of the Internet identification site, and for the convenience of memory, a domain name is adopted to replace the IP address to identify the site address. The resolution of the domain name is done by a DNS server that can cache and resolve a variety of DNS resource records, including a records and CNAME records. The a record is also called a host record, and is the most widely used DNS record, and the basic function of the a record is to describe how many IP addresses correspond to a domain name, and to indicate the correspondence between the domain name and the IP addresses, which is specifically represented in the form of www.test.com a 1.1.1.1. The CNAME record, i.e., the alias record, can resolve a domain name into another domain name (alias), and represents a correspondence between the domain name and the alias, specifically represented by www1.test.com CNAME www2. test.com. When performing DNS domain name resolution, the IP address corresponding to the domain name may be directly obtained from the a record, or the alias corresponding to the domain name may be obtained from the CNAME record, and then the IP address corresponding to the alias is obtained from the a record of the alias.
In this embodiment, a DNS split-flow resolving method is provided, and a specific flow thereof is shown in fig. 1:
step S1, receiving the analysis request of the user;
step S2, determining whether the domain name policy is hit, specifically, if the target domain name in the resolution request matches with the preset domain/domain name, executing step S3, and if not, executing step S4;
in step S2 of the DNS split resolution method according to the present embodiment, it is determined whether the target domain name includes test.com. Com, if the target domain name contains test, matching with the preset domain name, and executing step S3; com, if the target domain name does not contain test, the target domain name does not match the preset domain name, and step S4 is executed. The preset domain/domain name matching method includes, but is not limited to, matching partial fields in the domain name, and the server user may adopt other methods such as domain definition according to the own needs, which is not limited herein.
Step S3, according to the processing method selected for the domain/domain name, alternatively execute S31 or S32:
step S31, forwarding the target domain name to the dedicated server to obtain the resolution result of the dedicated server for the target domain name,
step S32, performing first iteration query on the target domain name to obtain an analysis result aiming at the target domain name;
in step S3 of the DNS split-flow resolution method provided in this embodiment, there are two resolution modes for the target domain name matching the preset domain/domain name, and specifically, the target domain name may be selectively forwarded or iterated according to a preset forwarding/iteration rule. The dedicated server to be forwarded may be one or more different servers, which may be set by themselves, and the server performing the first iterative query may be a local server itself or another external server. By forwarding the resolution request containing the specified domain name to a set dedicated server or performing the first iterative query, a more precise and accurate resolution result can be provided for the target domain name matched with the preset domain/domain name.
Step S4, a bottom forwarding step, that is, forwarding the target domain name to the public server to obtain a resolution result of the public server for the target domain name.
In step S4 of the DNS split-resolution method provided in this embodiment, the target domain name that does not match the preset domain/domain name is forwarded to the common server, which may be one or more servers set by the user. The target domain name forwarded to the public server can omit part of iterative query steps due to different processing procedures executed with the specified domain name, so as to improve the efficiency of domain name resolution and reduce the iterative flow.
Through the steps S1-S4, the DNS splitting resolution method provided in this embodiment completes the classification of domain names, and sets different resolution paths and resolution methods for domain names of different classifications, thereby preliminarily realizing the traffic allocation for DNS domain name resolution.
In the DNS split-flow resolution method provided in this embodiment, if the resolution result for the target domain name includes a CNAME record, the following steps are performed:
in step S5, if the alias in the CNAME record matches the preset domain name, step S3 is executed, and if not, step S32 is executed.
In step S5 of the DNS split-flow resolution method provided in this embodiment, regardless of whether the target domain name matches the preset domain/domain name or whether the target domain name matches the preset domain/domain name and then selects a resolution path for forwarding or first iterative query, as long as the returned resolution result of the target domain name includes the CNAME record, it needs to be further determined whether the alias in the CNAME record matches the preset domain name. Through the method, the alias matched with the preset domain/domain name can be prevented from being missed, and a detailed and precise resolution result can be provided for the preset domain/domain name.
In the DNS split-resolution method according to this embodiment, when executing step S4, if the resolution result of the public server for the target domain name includes the CNAME record and the a record, the following steps are executed:
and step S6, if the alias in the CNAME record is matched with the preset domain name, executing step S3, and if the alias is not matched with the preset domain name, returning the CNAME record and the A record to the user according to the forwarding trust switch.
In the prior art, when a forwarded analysis result includes a CNAME record and an a record, a server defaults to distrust the a record, and iteratively queries the CNAME record until the analysis result does not include the CNAME record. In step S6 of the DNS split-flow resolution method provided in this embodiment, the CNAME record and the a record included in the resolution result corresponding to the target domain name that does not match the preset domain name may be selected to be directly returned to the user. Therefore, the CNAME record iteration step of the partial domain name is selectively omitted, and the iteration flow of the server is reduced. Further, in step S6 of the DNS splitting resolution method provided in this embodiment, if there are multiple layers of CNAME records in the resolution result, and all aliases in the multiple layers of CNAME records do not match with the preset domain name,
when the forwarding trust switch is turned on, directly returning the CNAME record and the A record to the user;
and when the forwarding trust switch is closed, forwarding the multilayer CNAME records layer by layer, and returning the analysis results obtained by layer forwarding to the user after arranging the analysis results.
In step S6 of the DNS split-flow resolving method provided in this embodiment, when a resolving result includes multiple layers of CNAME records and all aliases in the multiple layers of CNAME records are not matched with a preset domain name, a forwarding trust switch is configured, and the forwarding trust switch may be selectively turned on or off according to a requirement of a user. When the forwarding trust switch is turned off, the parsing flow is as shown in fig. 2. The user requests resolution of the target domain name www.1.com, and the result of resolution www.1.com contains three layers of CNAME records and A records, which are not trusted by default. The server continues to forward the three layers of CNAME records layer by layer, forwards the alias www.2.com in the first layer of CNAME record www.1.com CNAME www.2.com to the second external recursive server, and the result of resolving www.2.com contains two layers of CNAME records and A records, and the A record is not trusted by default. The server continues to forward alias www.3.com in the second level CNAME record www.2.com CNAME www.3.com to the external recursive server three, the result of the resolution www.3.com contains one level CNAME record and an A record, which is not trusted by default. The server continues to forward the alias www.4.com in the third layer CNAME record www.3.com CNAME www.4.com, and the result of resolving www.4.com contains no CNAME record and contains an a record from which the IP address 1.1.1.1 corresponding to the domain name www.4.com is obtained. And finally, integrating results of the layer-by-layer iterative query and returning the results to the user.
In the steps, the process of layer-by-layer iterative query is complicated, the query time is long, but the finally obtained analysis result is more precise and accurate, and the method is suitable for the condition that the requirement on the accuracy of the analysis result is high. When the forwarding trust switch is turned on, the flow is as shown in fig. 3. The user requests to analyze the target domain name www.1.com, the result of the analysis www.1.com comprises three layers of CNAME records and A records, the A record is directly selected and trusted through a forwarding trust switch, the IP address 1.1.1.1 corresponding to the domain name www.4.com is obtained, and the three layers of CNAME records and the A record are returned to the user. Through the steps, layer-by-layer iterative query of multilayer CNAME records is not needed, query steps are greatly simplified, and a large amount of iterative flow is reduced. But also has certain influence on the accuracy of the analysis result, and the overall query analysis efficiency can be greatly improved under the condition that the requirement on the accuracy of the analysis result is not too high. The user can combine the two analysis methods according to actual conditions, and effectively reduce the iterative flow of the server while considering the accuracy of the analysis result.
Further, in step S5 or step S6 of the DNS split-flow resolution method provided in this embodiment, if there are multiple layers of CNAME records in the resolution result and any alias in the multiple layers of CNAME records matches a preset domain name, step S3 is executed according to the alias matching the preset domain name.
As shown in fig. 2, in the prior art, when the parsing result has multiple layers of CNAME records, the above-mentioned step of forwarding each layer of CNAME record layer by layer is required. When any alias in the multi-layer CNAME record matches with the preset domain name, for example www.3.com matches with the preset domain name, the step of forwarding layer by layer may be skipped, and step S3 is performed directly on the alias matching with the preset domain name, that is, www.3.com. Through the steps, a large amount of iterative flow generated by forwarding the multilayer CNAME records layer by layer is reduced, and the accuracy of alias resolution results matched with the preset domain name is ensured.
In the DNS split-flow resolution method provided in this embodiment, no matter whether the target domain name is matched with the preset domain/domain name or not, and after the target domain name is matched with the preset domain/domain name, a resolution path for forwarding or first iterative query is selected, if a resolution result for the target domain name does not include the CNAME record and includes the a record, the a record is returned to the user. In the above steps, the resolution result does not include a CNAME record, i.e., does not have an alias that needs to be determined whether to match with the preset domain/domain name, but includes an a record, i.e., an IP address corresponding to the known target domain name. Thus, the A record can be returned directly to the user.
In the DNS split resolution method provided in this embodiment, the target domain name includes: the target domain name, the alias in the CNAME record corresponding to the target domain name, and the alias in the CNAME record corresponding to the alias. The target domain name needs to be judged whether to be matched with the preset domain/domain name, namely, in the resolution process of the target domain name, all the contained domain names and aliases are judged whether to be matched with the preset domain/domain name, so that the alias matched with the preset domain/domain name is prevented from being missed, and the resolution step of the alias is omitted, so that the accuracy of the resolution result is influenced.
In step S4 of the DNS split-flow analysis method provided in this embodiment, if there is no CNAME record or no a record in the analysis result, the process goes to step S32 and reports an abnormal result. In step S4, if the target domain name forwarded to the public server fails to obtain the corresponding resolution result, the first iterative query needs to be performed to supplement the query of the public server.
In addition, no CNAME record or A record in the analysis result is an abnormal analysis result, and if the abnormal analysis result is received in the whole domain name analysis process, an abnormal warning is reported while the next action is carried out so that the server caches and records abnormal information.
In step S31 of the DNS split-flow analysis method provided in this embodiment, if there is no CNAME record or no a record in the analysis result, a second iterative query is performed, and in the second iterative query process, the iterative query is continued until the a record is queried. In step S31, the forwarded target domain names are all matched with the preset domain/domain name, which indicates that the dedicated server lacks the corresponding entry of the target domain name or its alias, and therefore the iterative query is continued.
As shown in fig. 4, in an embodiment of the present invention, there is also provided a DNS server, including:
a processor;
a memory communicatively coupled to the processor, the memory having stored therein a computer program, the DNS server capable of performing the following steps by reading and executing the computer program:
step S1, receiving the analysis request of the user;
step S2, if the target domain name in the resolution request matches the preset domain/domain name, executing step S3, if not, executing step S4;
step S3, according to the processing method selected for the domain/domain name, alternatively execute S31 or S32:
step S31, forwarding the target domain name to the dedicated server to obtain the resolution result of the dedicated server for the target domain name,
step S32, performing a first iterative query on the target domain name to obtain an analysis result of the first iterative query for the target domain name;
and step S4, forwarding the target domain name to the public server to obtain the resolution result of the public server for the target domain name.
The DNS server implements classification of domain names through steps S1 to S4, and sets different resolution paths and resolution methods for domain names of different classifications, thereby implementing allocation of paths and resolution traffic for DNS domain name resolution. For the analysis request forwarded to the dedicated server, the good matching between the dedicated server and the domain name can be utilized for centralized processing, and the processing efficiency is improved; for the content forwarded to the public server, the iterative flow can be reduced and the analysis efficiency can be improved in a trust A record mode. In addition, in this embodiment, by the above processing method for the CNAME record, the analysis request with the specified domain name in the alias can be identified in the processing process, and forwarded to the dedicated server for centralized processing, so as to improve the processing efficiency.
The embodiment of the invention also provides a computer readable storage medium, and a computer program for executing the DNS split-flow resolution method is stored on the computer readable storage medium.
The DNS distribution analysis method can be applied to DNS servers of various levels or types, such as a local DNS server, a root domain name server, a top level domain name server, an authority domain name server, a cache domain name server and the like. Among them, it is preferably applied to a local DNS server.
So far, the technical scheme of the invention has been described with reference to the attached drawings. However, it will be readily appreciated by those skilled in the art that the scope of the present invention is obviously not limited to the specific embodiments described above. Without departing from the principle of the invention, one skilled in the art can make equivalent changes or substitutions on the related technical features, and the technical solutions after the changes or substitutions will fall into the protection scope of the invention.
Claims (11)
1. A DNS offload resolution method is characterized by comprising the following steps:
step S1, receiving the analysis request of the user;
step S2, if the target domain name in the resolution request matches the preset domain/domain name, executing step S3, if not, executing step S4;
step S3, according to the processing method selected for the domain/domain name, alternatively execute S31 or S32:
step S31, forwarding the target domain name to the exclusive server to obtain the resolution result of the exclusive server for the target domain name,
step S32, performing a first iterative query on the target domain name to obtain an analysis result of the first iterative query for the target domain name;
step S4, forwarding the target domain name to a public server to obtain an analysis result of the public server for the target domain name.
2. The DNS split-flow resolving method according to claim 1, wherein if the resolution result for the target domain name includes a CNAME record, the following is performed:
in step S5, if the alias in the CNAME record matches the preset domain name, step S3 is executed, and if the alias does not match the preset domain name, step S32 is executed.
3. The DNS split-resolution method according to claim 2, wherein when executing step S4, if the resolution result of the public server for the target domain name includes a CNAME record and an a record, then:
and step S6, if the alias in the CNAME record is matched with the preset domain name, executing step S3, and if the alias is not matched with the preset domain name, returning the CNAME record and the A record to the user according to the forwarding trust switch.
4. The DNS splitting resolution method according to claim 3, wherein in the step S6, if there are multiple layers of CNAME records in the resolution result and all aliases in the multiple layers of CNAME records do not match with a preset domain name,
when the forwarding trust switch is turned on, directly returning the CNAME record and the A record to the user;
and when the forwarding trust switch is closed, forwarding the multilayer CNAME records layer by layer, and returning analysis results obtained by layer forwarding to the user after arranging the analysis results.
5. The DNS split-resolution method according to claim 3, wherein in step S5 or step S6, if there are multiple layers of CNAME records in the resolution result and any alias in the multiple layers of CNAME records matches a preset domain name, step S3 is executed according to the alias matching the preset domain name.
6. The DNS split-resolution method according to claim 1, wherein if a resolution result for the target domain name or the alias thereof does not include a CNAME record and includes an a record, the a record is returned to the user.
7. The DNS split-resolution method according to claim 1, wherein the target domain name includes: the target domain name, the alias in the CNAME record corresponding to the target domain name and the alias in the CNAME record corresponding to the alias.
8. The DNS split-flow resolving method according to claim 1, wherein in the step S4, if there is no CNAME record or no a record in the resolving result, the process goes to step S32 and reports an abnormal result.
9. The DNS splitting resolution method according to claim 1, wherein in step S31, if there is no CNAME record or no a record in the resolution result, performing a second iterative query, and in the second iterative query process, continuing the iterative query until an a record is queried.
10. A DNS server, comprising:
a processor;
a memory communicatively coupled to the processor, the memory having stored therein a computer program that, upon reading and executing, is capable of performing the steps of:
step S1, receiving the analysis request of the user;
step S2, if the target domain name in the resolution request matches the preset domain/domain name, executing step S3, if not, executing step S4;
step S3, according to the processing method selected for the domain/domain name, alternatively execute S31 or S32:
step S31, forwarding the target domain name to the dedicated server to obtain the resolution result of the dedicated server for the target domain name,
step S32, performing a first iterative query on the target domain name to obtain an analysis result of the first iterative query for the target domain name;
step S4, forwarding the target domain name to a public server, so as to obtain an analysis result of the public server for the target domain name.
11. 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 DNS split resolution method according to any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011482918.6A CN112671866B (en) | 2020-12-15 | 2020-12-15 | DNS (Domain name Server) shunt analysis method, DNS server and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011482918.6A CN112671866B (en) | 2020-12-15 | 2020-12-15 | DNS (Domain name Server) shunt analysis method, DNS server and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112671866A true CN112671866A (en) | 2021-04-16 |
| CN112671866B CN112671866B (en) | 2022-11-25 |
Family
ID=75405275
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011482918.6A Active CN112671866B (en) | 2020-12-15 | 2020-12-15 | DNS (Domain name Server) shunt analysis method, DNS server and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112671866B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113596194A (en) * | 2021-08-02 | 2021-11-02 | 牙木科技股份有限公司 | Method for DNS traffic classification calibration and DNS server |
| CN113766046A (en) * | 2021-09-09 | 2021-12-07 | 牙木科技股份有限公司 | Iterative traffic tracking method, DNS server, and computer-readable storage medium |
Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7970878B1 (en) * | 2005-11-16 | 2011-06-28 | Cisco Technology, Inc. | Method and apparatus for limiting domain name server transaction bandwidth |
| US20120030274A1 (en) * | 2010-07-29 | 2012-02-02 | International Business Machines Corporation | Managing alias host and domain names on a dns server |
| CN103248725A (en) * | 2013-05-23 | 2013-08-14 | 中国科学院计算机网络信息中心 | Safe and reliable domain name resolution repairing method and system |
| CN104168340A (en) * | 2014-07-24 | 2014-11-26 | 深圳市腾讯计算机系统有限公司 | Domain name resolution method, server, terminal and system |
| CN104639672A (en) * | 2015-02-12 | 2015-05-20 | 广州华多网络科技有限公司 | Method and device for domain name resolution (DNS) |
| CN105357328A (en) * | 2015-09-28 | 2016-02-24 | 互联网域名系统北京市工程研究中心有限公司 | DNS method, DNS recursive server and DNS system |
| CN105681491A (en) * | 2016-04-08 | 2016-06-15 | 网宿科技股份有限公司 | DNS (Domain Name Resolution) acceleration method, system and device |
| CN106453692A (en) * | 2016-11-28 | 2017-02-22 | 腾讯科技（深圳）有限公司 | Domain name resolution method, device and system |
| CN106657432A (en) * | 2016-11-17 | 2017-05-10 | 中国移动通信集团江苏有限公司 | Domain name resolution method and device |
| CN107124483A (en) * | 2017-06-26 | 2017-09-01 | 广州市百果园信息技术有限公司 | Domain name analytic method and server |
| CN108900648A (en) * | 2018-06-13 | 2018-11-27 | 网宿科技股份有限公司 | A kind of method and apparatus controlling more CNAME flow proportionals |
| CN109327559A (en) * | 2018-11-08 | 2019-02-12 | 同盾控股有限公司 | A kind of domain name analytic method and device based on mixing cloud platform |
| CN109561167A (en) * | 2018-11-27 | 2019-04-02 | 杭州迪普科技股份有限公司 | A kind of domain name analytic method and device |
| CN109936632A (en) * | 2019-03-07 | 2019-06-25 | 杭州又拍云科技有限公司 | A kind of CNAME accelerated method applied to DNS authority server |
| CN111182059A (en) * | 2019-12-30 | 2020-05-19 | 互联网域名系统北京市工程研究中心有限公司 | Query analysis method for domain name cache updating |
| CN111541793A (en) * | 2020-04-03 | 2020-08-14 | 北京市天元网络技术股份有限公司 | Content distribution network scheduling process analysis method and device and electronic equipment |
| CN111711716A (en) * | 2020-08-20 | 2020-09-25 | 苏州浪潮智能科技有限公司 | Domain name resolution method, device and equipment and readable storage medium |
| CN111726428A (en) * | 2020-06-12 | 2020-09-29 | 网宿科技股份有限公司 | Method, device, equipment and storage medium for selecting authoritative server |
| CN111953802A (en) * | 2020-07-06 | 2020-11-17 | 网宿科技股份有限公司 | Domain name resolution method, system, equipment and storage medium |
-
2020
- 2020-12-15 CN CN202011482918.6A patent/CN112671866B/en active Active
Patent Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7970878B1 (en) * | 2005-11-16 | 2011-06-28 | Cisco Technology, Inc. | Method and apparatus for limiting domain name server transaction bandwidth |
| US20120030274A1 (en) * | 2010-07-29 | 2012-02-02 | International Business Machines Corporation | Managing alias host and domain names on a dns server |
| CN103248725A (en) * | 2013-05-23 | 2013-08-14 | 中国科学院计算机网络信息中心 | Safe and reliable domain name resolution repairing method and system |
| CN104168340A (en) * | 2014-07-24 | 2014-11-26 | 深圳市腾讯计算机系统有限公司 | Domain name resolution method, server, terminal and system |
| CN104639672A (en) * | 2015-02-12 | 2015-05-20 | 广州华多网络科技有限公司 | Method and device for domain name resolution (DNS) |
| CN105357328A (en) * | 2015-09-28 | 2016-02-24 | 互联网域名系统北京市工程研究中心有限公司 | DNS method, DNS recursive server and DNS system |
| CN105681491A (en) * | 2016-04-08 | 2016-06-15 | 网宿科技股份有限公司 | DNS (Domain Name Resolution) acceleration method, system and device |
| CN106657432A (en) * | 2016-11-17 | 2017-05-10 | 中国移动通信集团江苏有限公司 | Domain name resolution method and device |
| CN106453692A (en) * | 2016-11-28 | 2017-02-22 | 腾讯科技（深圳）有限公司 | Domain name resolution method, device and system |
| CN107124483A (en) * | 2017-06-26 | 2017-09-01 | 广州市百果园信息技术有限公司 | Domain name analytic method and server |
| CN108900648A (en) * | 2018-06-13 | 2018-11-27 | 网宿科技股份有限公司 | A kind of method and apparatus controlling more CNAME flow proportionals |
| CN109327559A (en) * | 2018-11-08 | 2019-02-12 | 同盾控股有限公司 | A kind of domain name analytic method and device based on mixing cloud platform |
| CN109561167A (en) * | 2018-11-27 | 2019-04-02 | 杭州迪普科技股份有限公司 | A kind of domain name analytic method and device |
| CN109936632A (en) * | 2019-03-07 | 2019-06-25 | 杭州又拍云科技有限公司 | A kind of CNAME accelerated method applied to DNS authority server |
| CN111182059A (en) * | 2019-12-30 | 2020-05-19 | 互联网域名系统北京市工程研究中心有限公司 | Query analysis method for domain name cache updating |
| CN111541793A (en) * | 2020-04-03 | 2020-08-14 | 北京市天元网络技术股份有限公司 | Content distribution network scheduling process analysis method and device and electronic equipment |
| CN111726428A (en) * | 2020-06-12 | 2020-09-29 | 网宿科技股份有限公司 | Method, device, equipment and storage medium for selecting authoritative server |
| CN111953802A (en) * | 2020-07-06 | 2020-11-17 | 网宿科技股份有限公司 | Domain name resolution method, system, equipment and storage medium |
| CN111711716A (en) * | 2020-08-20 | 2020-09-25 | 苏州浪潮智能科技有限公司 | Domain name resolution method, device and equipment and readable storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 张蹦: "智能DNS技术在金融行业的应用", 《中国金融电脑》 * |
| 郭亚杰等: "DNS服务器解析性能测试方案设计", 《广西大学学报(自然科学版)》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113596194A (en) * | 2021-08-02 | 2021-11-02 | 牙木科技股份有限公司 | Method for DNS traffic classification calibration and DNS server |
| CN113596194B (en) * | 2021-08-02 | 2023-07-21 | 牙木科技股份有限公司 | Method for classifying and calibrating DNS traffic and DNS server |
| CN113766046A (en) * | 2021-09-09 | 2021-12-07 | 牙木科技股份有限公司 | Iterative traffic tracking method, DNS server, and computer-readable storage medium |
| CN113766046B (en) * | 2021-09-09 | 2023-10-13 | 牙木科技股份有限公司 | Iterative traffic tracking method, DNS server and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112671866B (en) | 2022-11-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112671866B (en) | DNS (Domain name Server) shunt analysis method, DNS server and computer readable storage medium | |
| CN111541796B (en) | CDN access flow scheduling method, device, communication system and storage medium | |
| US7467230B2 (en) | Global names zone | |
| US10171318B2 (en) | System and method of identifying internet-facing assets | |
| AU2008343434B2 (en) | DNS wildcard beaconing to determine client location and resolver load for global traffic load balancing | |
| US7991910B2 (en) | Updating routing information based on client location | |
| US7343399B2 (en) | Apparatus and method for managing internet resource requests | |
| US20170041321A1 (en) | Method and system for providing root domain name resolution service | |
| CN104378452A (en) | Method, device and system for domain name resolution | |
| CN105376344A (en) | Method and system for analyzing recursive domain name server related to source address | |
| CN109495604B (en) | Method for analyzing generic root domain name | |
| CN107786678B (en) | Domain name resolution method, device and system | |
| CN114846462A (en) | Asset search discovery system using graph data structure | |
| CN114189494B (en) | Domain name resolution method, DNS server and readable storage medium | |
| CN112333299B (en) | Domain name resolution method, configuration method and equipment | |
| CN111726428B (en) | Authoritative server selection method, device, equipment and storage medium | |
| CN114205330A (en) | Domain name resolution method, domain name resolution device, server, and storage medium | |
| CN116319113B (en) | Domain name resolution abnormality detection method and electronic equipment | |
| CN111371914A (en) | IP library generation method, domain name resolution method, electronic device and readable storage medium | |
| KR100342107B1 (en) | Methods for deciding Internet address groups distinguished by assigned organizations or locations and for resolving the geographical information for each address group, which are intended to set up Internet address supplementary system and its applications | |
| CN114244805B (en) | Domain name configuration method and device | |
| CN104079681A (en) | Alias analysis method | |
| CN113766046A (en) | Iterative traffic tracking method, DNS server, and computer-readable storage medium | |
| CN114500456A (en) | DNS scheduling optimization method and device based on full-network sniffing and computing equipment | |
| CN105245626A (en) | Method for realizing website addressing by using shortcut domain name in private network |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 200233 Room 401, building 1, No. 180, Yizhou Road, Xuhui District, Shanghai Applicant after: Yamu Technology Co.,Ltd. Address before: Room 305, 1028 Panyu Road, Xuhui District, Shanghai 200030 Applicant before: SHANGHAI YAMU COMMUNICATION TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |