CN111371911A - Domain name resolution system and method - Google Patents
Domain name resolution system and method Download PDFInfo
- Publication number
- CN111371911A CN111371911A CN201811603671.1A CN201811603671A CN111371911A CN 111371911 A CN111371911 A CN 111371911A CN 201811603671 A CN201811603671 A CN 201811603671A CN 111371911 A CN111371911 A CN 111371911A
- Authority
- CN
- China
- Prior art keywords
- domain name
- name resolution
- resolved
- request
- resolution request
- 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.)
- Pending
Links
Images
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/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- 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/09—Mapping addresses
- H04L61/10—Mapping addresses of different types
- H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
Abstract
The invention discloses a domain name resolution system and a domain name resolution method. Wherein, the method comprises the following steps: the target server receives a domain name resolution request which is generated by the client according to a domain name to be resolved and a preset request generation rule and corresponds to the domain name to be resolved; and returning a domain name resolution result corresponding to the domain name to be resolved to the client according to the domain name to be resolved contained in the domain name resolution request. Therefore, the client can generate the domain name resolution request containing the pre-configured identification information of the target server from the domain name to be resolved input by the user according to the preset request generation rule, so that the local DNS is bypassed, the target server is directly accessed to obtain the domain name resolution result, and the domain name hijacking phenomenon caused by malicious control of the local DNS is further prevented. In addition, the domain name resolution request in the method is based on the HTTP protocol, and has higher reliability compared with the UDP protocol, so that the safety is improved.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a domain name resolution system and a domain name resolution method.
Background
Domain name resolution is a service that directs domain names to a website space IP, allowing users to conveniently access the website through the registered domain names. The IP address is a digital address for identifying a station on the network, and a domain name is adopted to replace the IP address to identify the station address for the convenience of memory. Domain name resolution is the process of converting a domain name to an IP address.
Currently, in order to implement Domain Name resolution operation, a client typically sends a Domain Name resolution request to a local DNS (Domain Name System) server configured by an operator by default, and then the local DNS server directly returns a DNS resolution result, or the local DNS server returns a resolution result via an authorized DNS server. The domain name resolution request sent by the client is a request based on a DNS Protocol, and the request based on the DNS Protocol is implemented based on a UDP (user datagram Protocol) Protocol.
However, the inventor finds that the above mode in the prior art has at least the following defects in the process of implementing the invention: on one hand, the UDP is an unreliable transport protocol, and is prone to generating abnormal situations such as packet loss. On the other hand, the local DNS server is fixedly configured by the operator, and therefore, the local DNS server can control the domain name resolution operation, and even a domain name hijacking phenomenon may occur. For example, malicious replacement of the DNS resolution result IP1 corresponding to the domain name a with IP2 results in failure of access to the domain name a by the user, and even access to an unsafe site. Therefore, the existing domain name resolution mode has the risks of low safety and high possibility of being hijacked.
Disclosure of Invention
In view of the above, the present invention has been made to provide a domain name resolution system and method that overcomes or at least partially solves the above problems.
According to an aspect of the present invention, there is provided a domain name resolution system including:
the system comprises a client, a server and a server, wherein the client is suitable for generating a domain name resolution request corresponding to a domain name to be resolved according to the domain name to be resolved input by a user and a preset request generation rule; the domain name resolution request comprises a domain name to be resolved input by the user and identification information of a target server configured in advance according to the request generation rule;
the target server is suitable for receiving a domain name resolution request from the client according to the identification information of the preconfigured target server contained in the domain name resolution request, and returning a domain name resolution result corresponding to the domain name to be resolved to the client according to the domain name to be resolved contained in the domain name resolution request;
the target server is an HTTP server, and the domain name resolution request is a request based on an HTTP protocol.
According to another aspect of the present invention, there is provided a domain name resolution method, including:
the target server receives a domain name resolution request which is generated by a client according to a domain name to be resolved input by a user and a preset request generation rule and corresponds to the domain name to be resolved; the domain name resolution request comprises a domain name to be resolved input by the user and identification information of a target server configured in advance according to the request generation rule;
returning a domain name resolution result corresponding to the domain name to be resolved to the client according to the domain name to be resolved contained in the domain name resolution request;
the target server is an HTTP server, and the domain name resolution request is a request based on an HTTP protocol.
According to still another aspect of the present invention, there is provided an electronic apparatus including: the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is used for storing at least one executable instruction, and the executable instruction enables the processor to execute the operation corresponding to the domain name resolution method.
According to still another aspect of the present invention, there is provided a computer storage medium having at least one executable instruction stored therein, where the executable instruction causes a processor to perform operations corresponding to the domain name resolution method.
In the domain name resolution system and method disclosed by the invention, the client can generate the domain name resolution request corresponding to the domain name to be resolved according to the domain name to be resolved input by the user and the preset request generation rule, wherein the domain name resolution request comprises the domain name to be resolved input by the user and the identification information of the target server configured in advance according to the request generation rule. Correspondingly, the target server can receive the domain name resolution request from the client according to the pre-configured identification information of the target server contained in the domain name resolution request, and return a domain name resolution result corresponding to the domain name to be resolved to the client according to the domain name to be resolved contained in the domain name resolution request. Therefore, in the method, the client can generate the domain name resolution request containing the pre-configured identification information of the target server from the domain name to be resolved input by the user according to the preset request generation rule, so that the local DNS is bypassed, the target server is directly accessed to obtain the domain name resolution result, and the domain name hijacking phenomenon caused by malicious control of the local DNS is further prevented. In addition, the domain name resolution request in the method is based on the HTTP protocol, and has higher reliability compared with the UDP protocol, so that the safety is improved.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 shows a schematic structural diagram of a domain name resolution system according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a domain name resolution system according to another embodiment of the present invention;
fig. 3 is a flowchart illustrating a domain name resolution method according to another embodiment of the present invention;
fig. 4 shows a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Fig. 1 shows a schematic structural diagram of a domain name resolution system according to an embodiment of the present invention. As shown in fig. 1, the system includes: a client 10 and a target server 20. The client 10 is adapted to generate a domain name resolution request corresponding to a domain name to be resolved according to the domain name to be resolved input by a user and a preset request generation rule; the domain name resolution request comprises a domain name to be resolved input by a user and identification information of a target server configured in advance according to the request generation rule. The target server 20 is adapted to receive a domain name resolution request from the client according to the preconfigured identification information of the target server included in the domain name resolution request, and return a domain name resolution result corresponding to the domain name to be resolved to the client according to the domain name to be resolved included in the domain name resolution request. The target server is an HTTP server, and the domain name resolution request is a request based on an HTTP protocol.
It can be seen that, in the present embodiment, the client is a client device dedicated to implementing the anti-hijacking function. During specific implementation, an application program or browser software matched with the system can be pre-installed on the client device, so that the domain name to be resolved input by the user is generated into a corresponding domain name resolution request according to a preset request generation rule through the application program or browser software. The domain name resolution request is different from a conventional domain name resolution request. The conventional domain name resolution request only contains the domain name to be resolved, and the address of a receiver (such as a local DNS address) for receiving the conventional domain name resolution request is determined by the default configuration of the operator. The domain name resolution request in this embodiment includes the identifier information of the preconfigured target server, so that the address of the receiver receiving the domain name resolution request can be directly determined according to the identifier information of the preconfigured target server, and the domain name resolution request does not need to be sent to the local DNS according to the default configuration of the operator, so that the anti-hijacking effect can be achieved by bypassing the local DNS.
In addition, the target server in this embodiment is an HTTP server, also called an HTTP DNS server, and can implement the domain name resolution operation based on the HTTP protocol. In the specific analysis, the analysis can be performed in various ways. For example, a preset domain name comparison table may be configured inside the http dns server, where the domain name comparison table is used to store a correspondence between each domain name and each corresponding candidate resolution result, so as to determine the domain name resolution result based on the domain name comparison table. Alternatively, the domain name resolution result may be determined by the HTTP DNS server by further accessing an authorized DNS server, or the like. The present invention does not limit the specific analysis method of the target server.
Therefore, in the method, the client can generate the domain name resolution request containing the pre-configured identification information of the target server from the domain name to be resolved input by the user according to the preset request generation rule, so that the local DNS is bypassed, the target server is directly accessed to obtain the domain name resolution result, and the domain name hijacking phenomenon caused by malicious control of the local DNS is further prevented. In addition, the domain name resolution request in the method is based on the HTTP protocol, and has higher reliability compared with the UDP protocol, so that the safety is improved.
Fig. 2 is a schematic structural diagram of a domain name resolution system according to another embodiment of the present invention. As shown in fig. 2, the system includes: a client 10, a target server 20, and a configuration scheduling module 30.
The client 10 is adapted to generate a domain name resolution request corresponding to a domain name to be resolved according to the domain name to be resolved input by a user and a preset request generation rule; the domain name resolution request comprises a domain name to be resolved input by a user and identification information of a target server configured in advance according to the request generation rule.
Under a conventional condition, when a user needs to visit a certain site, a domain name to be resolved is directly input in an address bar of a browser. For example, a user enters a domain name of 360.cn/1.txt directly in the browser address bar, and the browser will generate a domain name resolution request containing the domain name directly. In this embodiment, in order to bypass the local DNS configured by the operator by default, the client 10 performs preset processing on the domain name to be resolved input by the user according to a preset request generation rule, so as to obtain a processed domain name resolution request.
In this embodiment, the processed domain name resolution request includes a first field, a second field, and a third field. Accordingly, the preset request generation rule includes: generating a first field contained in a domain name resolution request according to the pre-configured identification information of the target server; generating a second field contained in the domain name resolution request according to the domain name to be resolved input by the user; and generating a third field contained in the domain name resolution request according to the client identifier of the client. Specifically, the first field is located at the header of the domain name resolution request, and is generated according to the identification information of the preconfigured target server, where the preconfigured target server may be one or more, and the identification information of the target server may be an IP address of the target server. The second field is positioned in the middle of the domain name resolution request and is generated according to the domain name to be resolved input by the user so as to indicate the resource to be accessed by the user. The third field is located at the tail of the domain name resolution request and is generated according to the client identification (such as the client IP address) of the client. For example, taking the domain name of 360.cn/1.txt as an example, after processing, the corresponding domain name resolution request is as follows: http:// 1.1.1.1/domin? 3.3.3.4. The HTTP indicates that the request is a request based on an HTTP protocol,/1.1.1.1 is an IP address of the target server,/360. cn/1.txt is a domain name to be resolved, and 3.3.3.4 is an IP address of the client that generates the domain name resolution request. The IP address of the client, i.e. the third field, is an optional field, which may also be omitted in other embodiments of the present invention. In essence, the domain name resolution request is essentially an IP address, and therefore, does not need to be sent via the operator's default DNS configuration, but is sent directly to the target server corresponding to the IP address of/1.1.1.1. In addition, the processed domain name resolution request can also be understood as a URL request, and the URL request is directly sent to the corresponding target server according to the IP address/1.1.1.1 therein.
In addition, in this embodiment, the mapping relationship between the domain name to be resolved and the target server may also be configured in advance according to a preset request generation rule, so as to accurately determine the target server corresponding to the input domain name to be resolved. Specifically, the domain name to be resolved is divided into a plurality of groups in advance according to company information, region information and other related information corresponding to the domain name, and a corresponding target server is configured for the domain name to be resolved in each group. For example, the domain name to be resolved is divided into a first group domain name corresponding to a first company, a second group domain name corresponding to a second company, and a third group domain name corresponding to a third company in advance, and accordingly, the target server corresponding to the first group domain name is a first group target server, the target server corresponding to the second group domain name is a second group target server, and the target server corresponding to the third group domain name is a third group target server. There may be one or more target servers in each set, and there may be an intersection between target servers in each set. In a word, the domain name resolution request can be better prevented from being hijacked by an illegal server by presetting the mapping relation between the domain name to be resolved and the target server. In addition, when there are a plurality of target servers corresponding to a group in which a domain name is located, one target server may be selected from a plurality of candidate target servers according to various algorithms. For example, the domain name resolution requests may be sequentially sent to the target servers in the order of their numbers, or the client may maintain communication with the target servers to periodically obtain the load of each target server and select one target server as the receiver according to the load.
The target server 20 is configured to receive a domain name resolution request from the client according to the identifier information of the preconfigured target server included in the domain name resolution request, and return a domain name resolution result corresponding to the domain name to be resolved to the client according to the domain name to be resolved included in the domain name resolution request. The target server in this embodiment is an HTTP server, also called an HTTP DNS server. And when the domain name resolution request contains the client identifier of the client, the target server further returns a domain name resolution result corresponding to the domain name to be resolved to the client according to the client identifier contained in the domain name resolution request.
Specifically, each target server may determine the resolution result directly according to the locally stored domain name comparison table, or may determine the resolution result by further accessing an authorized DNS. In this embodiment, the system further includes a configuration scheduling module 30 connected to each target server, and accordingly, the target server further sends the domain name to be resolved and the client identifier included in the processed domain name resolution request to the configuration scheduling module, and receives a domain name resolution result corresponding to the domain name to be resolved, which is returned by the configuration scheduling module. The configuration scheduling module can determine a domain name resolution result corresponding to the domain name to be resolved from the target server according to a preset scheduling rule and provide the domain name resolution result to the target server. The preset scheduling rule may be a region-based rule, or a rule for implementing load balancing, or the like.
In an optional implementation manner, the presetting of the scheduling rule includes: determining region information corresponding to the client identifier according to the client identifier contained in the domain name resolution request; and determining a domain name resolution result corresponding to the domain name to be resolved contained in the domain name resolution request according to the region information corresponding to the client identifier and the candidate resolution result corresponding to the domain name to be resolved contained in the domain name resolution request. Specifically, the configuration scheduling module may determine, according to a client identifier included in the domain name resolution request, region information corresponding to the client identifier, so as to determine a region (e.g., beijing, shanghai, etc.) where the client that sent the domain name resolution request is located, and accordingly, select, from a plurality of candidate resolution results corresponding to the client identifier included in the domain name resolution request, one candidate resolution result that matches the region as the domain name resolution result corresponding to the client identifier included in the domain name resolution request. In specific implementation, the domain name resolution result corresponding to the device with the closest region interval can be selected according to the region proximity principle, so that the near access can be realized conveniently, and the access speed can be improved. For example, a region comparison table may be stored in the configuration scheduling module, where, for each domain name, a plurality of candidate resolution results corresponding to the domain name and a region of the host device corresponding to each candidate resolution result are stored.
In another optional implementation manner, the presetting of the scheduling rule includes: determining equipment scores corresponding to candidate resolution results corresponding to domain names to be resolved contained in the domain name resolution request according to a preset dynamic scheduling table; and determining the domain name resolution result corresponding to the domain name to be resolved contained in the domain name resolution request according to the equipment score corresponding to each candidate resolution result. Accordingly, the configuration scheduling module is further adapted to: and setting equipment weight for the equipment corresponding to each candidate analysis result according to the equipment score corresponding to each candidate analysis result, and determining the domain name analysis result corresponding to the domain name to be analyzed contained in the domain name analysis request according to the equipment weight.
In the latter implementation manner, the dynamic configuration center module dynamically obtains attribute information of the device corresponding to each candidate parsing result, and determines a corresponding device score according to the attribute information to generate a preset dynamic scheduling table. The dynamic scheduling table is used for storing the equipment scores of the equipment corresponding to the candidate analysis results. The dynamic configuration center module can be simultaneously connected with a plurality of configuration scheduling modules so as to provide a dynamic scheduling table for realizing dynamic scheduling for each configuration scheduling module.
Specifically, one candidate resolution result of each domain name corresponds to one host device, and in order to meet the requirement of simultaneous access of a large number of users, a plurality of candidate resolution results are generally configured for one domain name, and accordingly, the plurality of candidate resolution results correspond to a plurality of host devices, and information such as device load of each host device dynamically changes over time. In order to make the scheduling more reasonable, in this embodiment, a dynamic configuration center module that can be shared by multiple configuration scheduling modules is specially provided, and the dynamic configuration center module is configured to periodically obtain attribute information of each host device corresponding to each candidate resolution result of each domain name, so as to analyze the load, performance, and other conditions of the host device, thereby providing a basis for scheduling. Wherein the attribute information of the device includes at least one of: CPU information, disk input/output (I/O) information, network card traffic information, and link number information. In specific implementation, an acquisition program for acquiring attribute information may be directly deployed on each host device, and the acquisition program periodically reports the attribute information of the host device. Or, some collection nodes may be additionally deployed, each collection node is connected to the dynamic configuration center module and further connected to at least one host device, and the collection programs installed on the collection nodes and used for collecting the attribute information periodically acquire and report the attribute information of each host device. The CPU information is used for indicating the occupancy rate of the CPU and other related information, the lower the CPU occupancy rate is, the better the performance is, and the higher the equipment score is. The disk I/O information can reflect the utilization rate of the disk, and the higher the disk utilization rate is, the worse the performance is, and the lower the equipment score is. The network card traffic information and the link number information are used to reflect the load condition of the device, and specifically, the device score may be determined by combining a difference or a ratio between the maximum network card traffic information of the host device and the current network card traffic information, and a difference or a ratio between the maximum link number of the host device and the current link number. In summary, the higher the device idleness, the higher the performance score. Thus, the current performance of the host device can be reflected by the device score.
When the scheduling module is configured to perform specific scheduling, scheduling can be performed directly according to the device scores of the host devices. Or, in order to make the scheduling process more convenient, the configuration scheduling module may further set an equipment weight for the equipment corresponding to each candidate resolution result according to the equipment score corresponding to each candidate resolution result, and determine the domain name resolution result corresponding to the domain name to be resolved included in the domain name resolution request according to the equipment weight. The device weight is generally in direct proportion to the device score, and the device weight is directly associated with the candidate resolution results of each domain name and stored in a preset domain name comparison table (the domain name comparison table is used for storing the corresponding relation between each domain name and each corresponding candidate resolution result), so that the time delay of acquiring the candidate resolution results through the domain name comparison table and further inquiring the dynamic scheduling table according to the candidate resolution results is saved, and the processing speed is improved.
Therefore, the analysis system in this embodiment mainly includes an access layer formed by the target server and a scheduling layer formed by the configuration scheduling module, and the whole system is divided into two layers, so that corresponding processing rules can be conveniently set in each layer, and a flexible processing effect is achieved. The target server is located at the front end and used for analyzing and processing the domain name resolution request, so that the configuration scheduling module does not need to care about the specific type of the domain name resolution request, the specific information of a sender and the like, and the processing logic of the configuration scheduling module is simplified. The configuration scheduling module is located at the rear end and used for determining a domain name resolution result corresponding to the domain name to be resolved according to a preset scheduling rule. The configuration scheduling module and the target server are independent from each other, so that corresponding scheduling rules can be flexibly configured according to actual service scenes. For example, a region-based scheduling rule, a scheduling rule based on a dynamic score of each device, or the like may be configured. In a word, the independent configuration scheduling module is arranged, so that the required scheduling rule can be flexibly configured according to the actual situation.
To sum up, in this embodiment, the client can generate a domain name resolution request including the pre-configured identification information of the target server from the domain name to be resolved input by the user according to the preset request generation rule, thereby bypassing the local DNS and directly accessing the target server to obtain a domain name resolution result, thereby preventing the domain name hijacking phenomenon caused by malicious control of the local DNS. In addition, the domain name resolution request in the method is based on the HTTP protocol, and has higher reliability compared with the UDP protocol, so that the safety is improved. By the method in the embodiment, the local DNS can be bypassed. Moreover, the expandability can be improved by independently setting the configuration scheduling module, so that different scheduling rules can be flexibly set in the configuration scheduling module according to the actual application scene. The method can ensure that the domain name resolution request is directly scheduled by the configuration scheduling module without passing through the local DNS server so as to obtain corresponding configuration information. In addition, the configuration scheduling module can flexibly configure various self-defined scheduling rules according to the actual scene, and has strong expandability.
Fig. 3 is a flowchart illustrating a domain name resolution method according to another embodiment of the present invention. The method is implemented based on the domain name resolution system shown in fig. 1 or fig. 2. As shown in fig. 3, the method includes:
step S310: the target server receives a domain name resolution request which is generated by the client according to a domain name to be resolved and a preset request generation rule and corresponds to the domain name to be resolved; the domain name resolution request comprises a domain name to be resolved input by a user and identification information of a target server configured in advance according to a request generation rule.
Step S320: returning a domain name resolution result corresponding to the domain name to be resolved to the client according to the domain name to be resolved contained in the domain name resolution request; the target server is an HTTP server, and the domain name resolution request is a request based on an HTTP protocol.
Optionally, the domain name resolution request further includes a client identifier of the client;
then, the returning a domain name resolution result corresponding to the domain name to be resolved to the client according to the domain name to be resolved contained in the domain name resolution request further includes: and returning a domain name resolution result corresponding to the domain name to be resolved to the client according to the client identifier contained in the domain name resolution request.
Optionally, the domain name resolution request includes: a first field, a second field, and a third field; the preset request generation rule includes:
generating a first field contained in the domain name resolution request according to the pre-configured identification information of the target server;
generating a second field contained in the domain name resolution request according to a domain name to be resolved input by a user;
and generating a third field contained in the domain name resolution request according to the client identifier of the client.
Optionally, the domain name resolution request is a URL request.
Optionally, the returning a domain name resolution result corresponding to the domain name to be resolved to the client according to the domain name to be resolved contained in the domain name resolution request further includes:
sending the domain name to be analyzed contained in the domain name analysis request to a configuration scheduling module, and receiving a domain name analysis result which is returned by the configuration scheduling module and corresponds to the domain name to be analyzed;
the configuration scheduling module can determine a domain name resolution result corresponding to the domain name to be resolved from the target server according to a preset scheduling rule, and provide the domain name resolution result to the target server.
Optionally, the preset scheduling rule includes: determining region information corresponding to the client identifier according to the client identifier contained in the domain name resolution request;
and determining a domain name resolution result corresponding to the domain name to be resolved contained in the domain name resolution request according to the region information corresponding to the client identifier and the candidate resolution result corresponding to the domain name to be resolved contained in the domain name resolution request.
Optionally, the preset scheduling rule further includes: determining equipment scores corresponding to candidate resolution results corresponding to domain names to be resolved contained in the domain name resolution request according to a preset dynamic scheduling table;
and determining a domain name resolution result corresponding to the domain name to be resolved contained in the domain name resolution request according to the equipment score corresponding to each candidate resolution result.
The specific implementation principle and details of each step in the method may refer to the description of the corresponding part in the system embodiment, and are not described herein again.
The embodiment of the application provides a non-volatile computer storage medium, wherein at least one executable instruction is stored in the computer storage medium, and the computer executable instruction can execute the domain name resolution method in any method embodiment.
Fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present invention, and the specific embodiment of the present invention does not limit the specific implementation of the electronic device.
As shown in fig. 4, the electronic device may include: a processor (processor)402, a communication Interface (Communication I/Ons Interface)404, a memory (memory)406, and a communication bus 408.
Wherein:
the processor 402, communication interface 404, and memory 406 communicate with each other via a communication bus 408.
A communication interface 404 for communicating with network elements of other devices, such as clients or other servers.
The processor 402 is configured to execute the program 410, and may specifically perform relevant steps in the above embodiments of the domain name resolution method.
In particular, program 410 may include program code comprising computer operating instructions.
The processor 402 may be a central processing unit CPU, or an application specific Integrated Circuit ASIC (application I/on specific Integrated Circuit), or one or more Integrated circuits configured to implement an embodiment of the invention. The electronic device comprises one or more processors, which can be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.
And a memory 406 for storing a program 410. Memory 406 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
The program 410 may be specifically configured to cause the processor 402 to perform the operations in the above-described method embodiments.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components in a domain name resolution arrangement according to embodiments of the present invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
The invention also discloses A1. a domain name resolution system, comprising:
the system comprises a client, a server and a server, wherein the client is suitable for generating a domain name resolution request corresponding to a domain name to be resolved according to the domain name to be resolved input by a user and a preset request generation rule; the domain name resolution request comprises a domain name to be resolved input by the user and identification information of a target server configured in advance according to the request generation rule;
the target server is suitable for receiving a domain name resolution request from the client according to the identification information of the preconfigured target server contained in the domain name resolution request, and returning a domain name resolution result corresponding to the domain name to be resolved to the client according to the domain name to be resolved contained in the domain name resolution request;
the target server is an HTTP server, and the domain name resolution request is a request based on an HTTP protocol.
A2. The system according to claim a1, wherein the domain name resolution request further includes a client identification of the client;
the target server is further adapted to: and returning a domain name resolution result corresponding to the domain name to be resolved to the client according to the client identifier contained in the domain name resolution request.
A3. The system of claim a2, wherein the domain name resolution request includes: a first field, a second field, and a third field; the preset request generation rule includes:
generating a first field contained in the domain name resolution request according to the pre-configured identification information of the target server;
generating a second field contained in the domain name resolution request according to a domain name to be resolved input by a user;
and generating a third field contained in the domain name resolution request according to the client identifier of the client.
A4. The system of claim a3, wherein the domain name resolution request is a URL request.
A5. The system of any of claims a1-4, wherein the system further comprises: a scheduling module is configured;
the target server is further adapted to: sending the domain name to be analyzed contained in the domain name analysis request to the configuration scheduling module, and receiving a domain name analysis result which is returned by the configuration scheduling module and corresponds to the domain name to be analyzed;
the configuration scheduling module is suitable for determining a domain name resolution result corresponding to the domain name to be resolved from the target server according to a preset scheduling rule and providing the domain name resolution result to the target server.
A6. The system of claim a5, wherein the target server is further adapted to: sending the client identifier contained in the domain name resolution request to the configuration scheduling module;
the preset scheduling rule includes: determining region information corresponding to the client identifier according to the client identifier contained in the domain name resolution request;
and determining a domain name resolution result corresponding to the domain name to be resolved contained in the domain name resolution request according to the region information corresponding to the client identifier and the candidate resolution result corresponding to the domain name to be resolved contained in the domain name resolution request.
A7. The system of any of claims a5-6, wherein the preset scheduling rule further comprises: determining equipment scores corresponding to candidate resolution results corresponding to domain names to be resolved contained in the domain name resolution request according to a preset dynamic scheduling table;
and determining a domain name resolution result corresponding to the domain name to be resolved contained in the domain name resolution request according to the equipment score corresponding to each candidate resolution result.
A8. The system of claim a7, wherein the configuration scheduling module is further adapted to: and setting equipment weight for the equipment corresponding to each candidate analysis result according to the equipment score corresponding to each candidate analysis result, and determining the domain name analysis result corresponding to the domain name to be analyzed contained in the domain name analysis request according to the equipment weight.
A9. The system of any of claims a5-8, wherein the system further comprises: the dynamic configuration center module is connected with the configuration scheduling module; wherein the content of the first and second substances,
and the dynamic configuration center module is used for dynamically acquiring attribute information of equipment corresponding to each candidate analysis result, and determining a corresponding equipment score according to the attribute information so as to generate the preset dynamic scheduling table.
A10. The system of claim a9, wherein the device's attribute information includes at least one of: CPU information, disk I/O information, network card traffic information, and link number information.
B11. A domain name resolution method based on the domain name resolution system of any of claims a1-10, comprising:
the target server receives a domain name resolution request which is generated by a client according to a domain name to be resolved input by a user and a preset request generation rule and corresponds to the domain name to be resolved; the domain name resolution request comprises a domain name to be resolved input by the user and identification information of a target server configured in advance according to the request generation rule;
returning a domain name resolution result corresponding to the domain name to be resolved to the client according to the domain name to be resolved contained in the domain name resolution request;
the target server is an HTTP server, and the domain name resolution request is a request based on an HTTP protocol.
B12. The method of claim B11, wherein the domain name resolution request further includes a client identification of the client;
then, the returning a domain name resolution result corresponding to the domain name to be resolved to the client according to the domain name to be resolved contained in the domain name resolution request further includes: and returning a domain name resolution result corresponding to the domain name to be resolved to the client according to the client identifier contained in the domain name resolution request.
B13. The method of claim B12, wherein the domain name resolution request includes: a first field, a second field, and a third field; the preset request generation rule includes:
generating a first field contained in the domain name resolution request according to the pre-configured identification information of the target server;
generating a second field contained in the domain name resolution request according to a domain name to be resolved input by a user;
and generating a third field contained in the domain name resolution request according to the client identifier of the client.
B14. The method of claim B13, wherein the domain name resolution request is a URL request.
B15. The method according to any of claims B11-14, wherein the returning a domain name resolution result corresponding to the domain name to be resolved to the client according to the domain name to be resolved contained in the domain name resolution request further comprises:
sending the domain name to be analyzed contained in the domain name analysis request to a configuration scheduling module, and receiving a domain name analysis result which is returned by the configuration scheduling module and corresponds to the domain name to be analyzed;
the configuration scheduling module can determine a domain name resolution result corresponding to the domain name to be resolved from the target server according to a preset scheduling rule, and provide the domain name resolution result to the target server.
B16. The method of claim B15, wherein the preset scheduling rules include: determining region information corresponding to the client identifier according to the client identifier contained in the domain name resolution request;
and determining a domain name resolution result corresponding to the domain name to be resolved contained in the domain name resolution request according to the region information corresponding to the client identifier and the candidate resolution result corresponding to the domain name to be resolved contained in the domain name resolution request.
B17. The method of any of claims B15-16, wherein the preset scheduling rule further comprises: determining equipment scores corresponding to candidate resolution results corresponding to domain names to be resolved contained in the domain name resolution request according to a preset dynamic scheduling table;
and determining a domain name resolution result corresponding to the domain name to be resolved contained in the domain name resolution request according to the equipment score corresponding to each candidate resolution result.
C18. An electronic device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is configured to store at least one executable instruction that causes the processor to perform operations corresponding to domain name resolution according to any of claims B11-17.
D19. A computer storage medium having stored therein at least one executable instruction that causes a processor to perform operations corresponding to domain name resolution as recited in any of claims B11-17.
Claims (10)
1. A domain name resolution system, comprising:
the system comprises a client, a server and a server, wherein the client is suitable for generating a domain name resolution request corresponding to a domain name to be resolved according to the domain name to be resolved input by a user and a preset request generation rule; the domain name resolution request comprises a domain name to be resolved input by the user and identification information of a target server configured in advance according to the request generation rule;
the target server is suitable for receiving a domain name resolution request from the client according to the identification information of the preconfigured target server contained in the domain name resolution request, and returning a domain name resolution result corresponding to the domain name to be resolved to the client according to the domain name to be resolved contained in the domain name resolution request;
the target server is an HTTP server, and the domain name resolution request is a request based on an HTTP protocol.
2. The system of claim 1, wherein the domain name resolution request further includes a client identifier of the client;
the target server is further adapted to: and returning a domain name resolution result corresponding to the domain name to be resolved to the client according to the client identifier contained in the domain name resolution request.
3. The system of claim 2, wherein the domain name resolution request comprises: a first field, a second field, and a third field; the preset request generation rule includes:
generating a first field contained in the domain name resolution request according to the pre-configured identification information of the target server;
generating a second field contained in the domain name resolution request according to a domain name to be resolved input by a user;
and generating a third field contained in the domain name resolution request according to the client identifier of the client.
4. The system of claim 3, wherein the domain name resolution request is a URL request.
5. The system of any of claims 1-4, wherein the system further comprises: a scheduling module is configured;
the target server is further adapted to: sending the domain name to be analyzed contained in the domain name analysis request to the configuration scheduling module, and receiving a domain name analysis result which is returned by the configuration scheduling module and corresponds to the domain name to be analyzed;
the configuration scheduling module is suitable for determining a domain name resolution result corresponding to the domain name to be resolved from the target server according to a preset scheduling rule and providing the domain name resolution result to the target server.
6. The system of claim 5, wherein the target server is further adapted to: sending the client identifier contained in the domain name resolution request to the configuration scheduling module;
the preset scheduling rule includes: determining region information corresponding to the client identifier according to the client identifier contained in the domain name resolution request;
and determining a domain name resolution result corresponding to the domain name to be resolved contained in the domain name resolution request according to the region information corresponding to the client identifier and the candidate resolution result corresponding to the domain name to be resolved contained in the domain name resolution request.
7. The system of any of claims 5-6, wherein the preset scheduling rule further comprises: determining equipment scores corresponding to candidate resolution results corresponding to domain names to be resolved contained in the domain name resolution request according to a preset dynamic scheduling table;
and determining a domain name resolution result corresponding to the domain name to be resolved contained in the domain name resolution request according to the equipment score corresponding to each candidate resolution result.
8. A domain name resolution method based on the domain name resolution system according to any one of claims 1 to 7, comprising:
the target server receives a domain name resolution request which is generated by a client according to a domain name to be resolved input by a user and a preset request generation rule and corresponds to the domain name to be resolved; the domain name resolution request comprises a domain name to be resolved input by the user and identification information of a target server configured in advance according to the request generation rule;
returning a domain name resolution result corresponding to the domain name to be resolved to the client according to the domain name to be resolved contained in the domain name resolution request;
the target server is an HTTP server, and the domain name resolution request is a request based on an HTTP protocol.
9. An electronic device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is configured to store at least one executable instruction that causes the processor to perform operations corresponding to domain name resolution according to any of claim 8.
10. A computer storage medium having stored therein at least one executable instruction that causes a processor to perform operations corresponding to domain name resolution as claimed in any of claims 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811603671.1A CN111371911A (en) | 2018-12-26 | 2018-12-26 | Domain name resolution system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811603671.1A CN111371911A (en) | 2018-12-26 | 2018-12-26 | Domain name resolution system and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111371911A true CN111371911A (en) | 2020-07-03 |
Family
ID=71206286
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811603671.1A Pending CN111371911A (en) | 2018-12-26 | 2018-12-26 | Domain name resolution system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111371911A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112491910A (en) * | 2020-12-01 | 2021-03-12 | 北京鸿腾智能科技有限公司 | Traffic identification method, device, equipment and storage medium based on DOT protocol |
| CN112887451A (en) * | 2021-02-25 | 2021-06-01 | 上海哔哩哔哩科技有限公司 | Domain name resolution method and device and computer equipment |
| CN116938877A (en) * | 2023-09-15 | 2023-10-24 | 阿里云计算有限公司 | Domain name resolution data configuration method, domain name resolution method and related device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104104610A (en) * | 2013-04-09 | 2014-10-15 | 江苏天联信息科技发展有限公司 | Flow scheduling method and apparatus based on domain name system, and domain name system |
| CN106953945A (en) * | 2017-05-26 | 2017-07-14 | 北京奇虎科技有限公司 | Domain name intelligently parsing method and device, server based on SDN realizations |
| CN107147751A (en) * | 2017-05-11 | 2017-09-08 | 上海红阵信息科技有限公司 | Domain name analytic method and device |
| CN107204873A (en) * | 2017-05-04 | 2017-09-26 | 网宿科技股份有限公司 | A kind of method and relevant device for switching target domain name resolution server |
| CN107528862A (en) * | 2017-10-23 | 2017-12-29 | 北京京东金融科技控股有限公司 | The method and device of domain name mapping |
| CN108737582A (en) * | 2017-04-18 | 2018-11-02 | 艺龙网信息技术（北京）有限公司 | The method and device of domain name mapping |
-
2018
- 2018-12-26 CN CN201811603671.1A patent/CN111371911A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104104610A (en) * | 2013-04-09 | 2014-10-15 | 江苏天联信息科技发展有限公司 | Flow scheduling method and apparatus based on domain name system, and domain name system |
| CN108737582A (en) * | 2017-04-18 | 2018-11-02 | 艺龙网信息技术（北京）有限公司 | The method and device of domain name mapping |
| CN107204873A (en) * | 2017-05-04 | 2017-09-26 | 网宿科技股份有限公司 | A kind of method and relevant device for switching target domain name resolution server |
| CN107147751A (en) * | 2017-05-11 | 2017-09-08 | 上海红阵信息科技有限公司 | Domain name analytic method and device |
| CN106953945A (en) * | 2017-05-26 | 2017-07-14 | 北京奇虎科技有限公司 | Domain name intelligently parsing method and device, server based on SDN realizations |
| CN107528862A (en) * | 2017-10-23 | 2017-12-29 | 北京京东金融科技控股有限公司 | The method and device of domain name mapping |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112491910A (en) * | 2020-12-01 | 2021-03-12 | 北京鸿腾智能科技有限公司 | Traffic identification method, device, equipment and storage medium based on DOT protocol |
| CN112491910B (en) * | 2020-12-01 | 2023-09-05 | 三六零数字安全科技集团有限公司 | DOT protocol-based flow identification method, DOT protocol-based flow identification device, DOT protocol-based flow identification equipment and storage medium |
| CN112887451A (en) * | 2021-02-25 | 2021-06-01 | 上海哔哩哔哩科技有限公司 | Domain name resolution method and device and computer equipment |
| CN116938877A (en) * | 2023-09-15 | 2023-10-24 | 阿里云计算有限公司 | Domain name resolution data configuration method, domain name resolution method and related device |
| CN116938877B (en) * | 2023-09-15 | 2024-01-05 | 阿里云计算有限公司 | Domain name resolution data configuration method, domain name resolution method and related device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111866064B (en) | Load balancing method, device and system | |
| CN108881448B (en) | API request processing method and device | |
| CN111460460B (en) | Task access method, device, proxy server and machine-readable storage medium | |
| CN107302604B (en) | Kubernetes-based PaaS platform domain name configuration method and device and electronic equipment | |
| WO2017097123A1 (en) | Access request conversion method and device | |
| CN108494891A (en) | A kind of domain name analytic method, server and system | |
| CN111371911A (en) | Domain name resolution system and method | |
| CN109660578B (en) | CDN back-to-source processing method, device and system | |
| US9910687B2 (en) | Data flow affinity for heterogenous virtual machines | |
| CN109818934B (en) | Method and device for automatically processing logs and computing equipment | |
| CN111885123B (en) | Construction method and device of cross-K8 s target service access channel | |
| CN109657434B (en) | Application access method and device | |
| CN110224943B (en) | Flow service current limiting method based on URL, electronic equipment and computer storage medium | |
| US20170171147A1 (en) | Method and electronic device for implementing domain name system | |
| US10536425B2 (en) | Cross-domain HTTP requests using DNS rebinding | |
| CN106790593B (en) | Page processing method and device | |
| WO2017166524A1 (en) | Domain name parsing method and apparatus | |
| CN110365517B (en) | Data processing method, data processing device, storage medium and computer equipment | |
| CN111787129A (en) | Method and system for configuring local DNS server for client | |
| CN107911499A (en) | Multi-line domain name analytic method and device | |
| CN111628878A (en) | Fault positioning method, device and system based on multi-stage network nodes | |
| US20210243248A1 (en) | Cloud service load balancing | |
| CN115150358A (en) | Domain name acquisition method, electronic device and system | |
| CN113382093B (en) | Domain name resolution method, electronic device and system | |
| CN111371910B (en) | DNS-based scheduling system and method |
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 |