CN108712515B - Domain name resolution method and system - Google Patents
Domain name resolution method and system Download PDFInfo
- Publication number
- CN108712515B CN108712515B CN201810414510.1A CN201810414510A CN108712515B CN 108712515 B CN108712515 B CN 108712515B CN 201810414510 A CN201810414510 A CN 201810414510A CN 108712515 B CN108712515 B CN 108712515B
- Authority
- CN
- China
- Prior art keywords
- domain name
- target
- address
- client
- analyzed
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
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]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
According to the domain name resolution method and system, the IP address of the client is packaged into the source domain name to be resolved on the client, the target domain name to be resolved is obtained, the target domain name to be resolved is sent to the target intelligent domain name server, the target intelligent domain name server can determine the IP address of the client from the target domain name to be resolved, and then intelligent domain name resolution is achieved according to the IP address of the client.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a domain name resolution method and system.
Background
In an IP (Internet Protocol) network, a Domain Name System (DNS) is one of the most critical basic services of the Internet, and provides fundamental support for many network applications, and its main function is to convert a Domain Name (Domain Name) that is easy to be memorized by people and an IP address that can be recognized by the network. The translation between the domain name and the IP address is called domain name resolution, and the network host performing the domain name resolution may be called a DNS server. Through the query service of the domain name system DNS server, the entry of the required site or resource can be found, and then the site or resource is accessed.
However, in the domain name resolution process, how to obtain the IP address of the client by the intelligent DNS server for domain name resolution becomes a problem in realizing intelligent domain name resolution.
Disclosure of Invention
In order to solve the above technical problems, embodiments of the present application provide a domain name resolution method and system, so as to ensure that a target intelligent domain name server can determine an IP address of a client from a target domain name to be resolved, and further achieve an intelligent domain name resolution according to the IP address of the client, where the technical scheme is as follows:
a domain name resolution method is applied to a client, and comprises the following steps:
acquiring a domain name resolution request;
acquiring a domain name to be resolved from the domain name resolution request as a source domain name to be resolved;
determining the IP address of the client according to the domain name resolution request;
encapsulating the IP address of the client into the source domain name to be resolved to obtain a new domain name to be resolved as a target domain name to be resolved;
inquiring an intelligent domain name server corresponding to the target domain name to be analyzed as a target intelligent domain name server;
and sending the target domain name to be analyzed to a local domain name server so that the local domain name server sends the target domain name to be analyzed to the target intelligent domain name server so that the target intelligent domain name server analyzes the target domain name to be analyzed.
Preferably, the analyzing the target domain name to be analyzed by the target intelligent domain name server includes:
judging whether the suffix of the target domain name to be analyzed is a preset suffix or not;
if the suffix of the target domain name to be analyzed is a preset suffix, analyzing the source domain name to be analyzed and the IP address of the client from the target domain name to be analyzed;
determining geographical location information corresponding to the IP address of the client;
and determining a target application server according to the domain name to be analyzed of the source and the geographical position information corresponding to the IP address of the client, and returning the IP address of the target application server to the client.
Preferably, before determining the IP address of the client according to the domain name resolution request, the method further includes:
judging whether the type of a domain name resolution server corresponding to the source domain name to be resolved is an intelligent domain name server or not;
if yes, determining the IP address of the client according to the domain name resolution request;
if not, inquiring a common domain name server corresponding to the source domain name to be analyzed as a target common domain name server;
and sending the domain name to be analyzed of the source to the target ordinary domain name server so that the target ordinary domain name server analyzes the domain name to be analyzed of the source.
Preferably, the determining the geographical location information corresponding to the IP address of the client includes:
inquiring whether an IP address matched with the IP address of the client exists in an IP address and geographic position information mapping relation library;
and if so, taking the geographical location information corresponding to the IP address matched with the IP address of the client as the geographical location information corresponding to the IP address of the client.
Preferably, the determining a target application server according to the domain name to be resolved and the geographic location information corresponding to the IP address of the client includes:
inquiring whether a domain name and geographical position information matched with the domain name to be analyzed and the geographical position information corresponding to the IP address of the client exist in a strategy information base;
and if the domain name exists, taking the domain name matched with the domain name to be analyzed and the geographic position information corresponding to the IP address of the client as the target application server.
A domain name resolution system, comprising: the system comprises a client, a local domain name server and a target intelligent domain name server;
the client is used for:
acquiring a domain name resolution request;
acquiring a domain name to be resolved from the domain name resolution request as a source domain name to be resolved;
determining the IP address of the client according to the domain name resolution request;
encapsulating the IP address of the client into the source domain name to be resolved to obtain a new domain name to be resolved as a target domain name to be resolved;
inquiring an intelligent domain name server corresponding to the target domain name to be analyzed as a target intelligent domain name server;
sending the target domain name to be analyzed to a local domain name server so that the local domain name server sends the target domain name to be analyzed to the target intelligent domain name server so that the target intelligent domain name server analyzes the target domain name to be analyzed;
the local domain name server is used for sending the target domain name to be analyzed to the target intelligent domain name server;
and the target intelligent domain name server is used for analyzing the domain name to be analyzed of the target.
Preferably, the target intelligent domain name server is specifically configured to:
judging whether the suffix of the target domain name to be analyzed is a preset suffix or not;
if the suffix of the target domain name to be analyzed is a preset suffix, analyzing the source domain name to be analyzed and the IP address of the client from the target domain name to be analyzed;
determining geographical location information corresponding to the IP address of the client;
and determining a target application server according to the domain name to be analyzed of the source and the geographical position information corresponding to the IP address of the client, and returning the IP address of the target application server to the client.
Preferably, the client is further configured to:
before determining the IP address of the client according to the domain name resolution request, judging whether the type of a domain name resolution server corresponding to the source domain name to be resolved is an intelligent domain name server;
if yes, determining the IP address of the client according to the domain name resolution request;
if not, inquiring a common domain name server corresponding to the source domain name to be analyzed as a target common domain name server;
and sending the domain name to be analyzed of the source to the target ordinary domain name server so that the target ordinary domain name server analyzes the domain name to be analyzed of the source.
Preferably, the target intelligent domain name server is specifically configured to:
inquiring whether an IP address matched with the IP address of the client exists in an IP address and geographic position information mapping relation library;
and if so, taking the geographical location information corresponding to the IP address matched with the IP address of the client as the geographical location information corresponding to the IP address of the client.
Preferably, the target intelligent domain name server is specifically configured to:
inquiring whether a domain name and geographical position information matched with the domain name to be analyzed and the geographical position information corresponding to the IP address of the client exist in a strategy information base;
and if the domain name exists, taking the domain name matched with the domain name to be analyzed and the geographic position information corresponding to the IP address of the client as the target application server.
Compared with the prior art, the beneficial effect of this application is:
in the method, the IP address of the client is packaged into the source domain name to be analyzed on the client to obtain the target domain name to be analyzed, and the target domain name to be analyzed is sent to the target intelligent domain name server, so that the target intelligent domain name server can determine the IP address of the client from the target domain name to be analyzed, and then intelligent domain name analysis is realized according to the IP address of the client.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
Fig. 1 is a flowchart of a domain name resolution method provided in the present application;
FIG. 2 is a sub-flowchart of a domain name resolution method provided herein;
FIG. 3 is another sub-flow diagram of a domain name resolution method provided herein;
FIG. 4 is a further sub-flowchart of a domain name resolution method provided herein;
FIG. 5 is another flow chart of a domain name resolution method provided herein;
fig. 6 is a schematic diagram of a logical structure of a domain name resolution system provided in the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The embodiment of the application discloses a domain name resolution method, which is applied to a client and comprises the following steps: acquiring a domain name resolution request; acquiring a domain name to be resolved from the domain name resolution request as a source domain name to be resolved; determining the IP address of the client according to the domain name resolution request; encapsulating the IP address of the client into the source domain name to be resolved to obtain a new domain name to be resolved as a target domain name to be resolved; inquiring an intelligent domain name server corresponding to the target domain name to be analyzed as a target intelligent domain name server; and sending the target domain name to be analyzed to a local domain name server so that the local domain name server sends the target domain name to be analyzed to the target intelligent domain name server so that the target intelligent domain name server analyzes the target domain name to be analyzed.
Next, a domain name resolution method disclosed in the embodiment of the present application is introduced, please refer to fig. 1, which may include:
and step S11, acquiring a domain name resolution request.
Step S12, obtaining the domain name to be resolved from the domain name resolution request, and using the domain name to be resolved as the source domain name to be resolved.
And step S13, determining the IP address of the client according to the domain name resolution request.
Step S14, the IP address of the client is encapsulated into the source domain name to be resolved to obtain a new domain name to be resolved, which is used as the target domain name to be resolved.
In this embodiment, encapsulating the IP address of the client into the source domain name to be resolved may be understood as: and combining the IP address of the client with the source domain name to be analyzed, and adding a preset suffix. If the domain name to be resolved by the source is domain, such as www.test.com; assume that the IP address of the client is IP, such as 192.168.10.10; preset suffixes are postfix, such as dns. ipanel.cn; then, the IP address of the client is encapsulated into the source domain name to be resolved, and the obtained target domain name to be resolved may be represented as: ip.
Further, in order to save the length of the domain name, the ip address of the client may be 16, i.e. changed to C0a80A0A, and the domain name to be resolved by the target may be represented as: www.test.com.C0A80A0A.dns.ipanel.cn are provided.
And step S15, inquiring the intelligent domain name server corresponding to the target domain name to be analyzed as the target intelligent domain name server.
In this embodiment, the intelligent domain name server corresponding to the target domain name to be resolved may be queried in a recursive query or an iterative query manner.
The recursive query can be understood as: if the local domain name server inquired by the host does not know the IP address of the inquired domain name, the local domain name server continuously sends an inquiry request message to other root domain name servers according to the identity of the DNS client (namely continuously inquires for the host), but the host does not carry out the next inquiry. Therefore, the query result returned by the recursive query is either the IP address to be queried or an error, which indicates that the required IP address cannot be queried.
Iterative query, which can be understood as: when the root domain name server receives the iterative query request message sent by the local domain name server, the root domain name server either gives the IP address to be queried or tells the local server: "which domain name server you should query next". And then have the local server perform subsequent queries. The root domain name server usually informs the local domain name server of the IP address of the top-level domain name server known by itself, and the local domain name server queries the top-level domain name server. After receiving the query request of the local domain name server, the top-level domain name server either gives the IP address to be queried or tells the local server which authority domain name server should be queried next. Finally, knowing the IP address to be resolved or reporting an error, returns the result to the host that initiated the query.
Step S16, sending the target domain name to be resolved to a local domain name server, so that the local domain name server sends the target domain name to be resolved to the target intelligent domain name server, so that the target intelligent domain name server resolves the target domain name to be resolved.
It should be noted that the target intelligent domain name server may determine the incoming path of the client, perform some intelligent processing, and then return the IP address of the obtained application server to the user after the intelligent determination. For example, the intelligent DNS of the DNS pod automatically determines whether the internet line of the user is internet or telecommunications, and then intelligently returns the IP address of the internet or telecommunications application server.
The target intelligent domain name server analyzes the domain name to be analyzed, so that the analyzed target application server is ensured to be the application server within the geographic position range of the client, and the reliability of domain name analysis is further improved.
In the method, the IP address of the client is packaged into the source domain name to be analyzed on the client to obtain the target domain name to be analyzed, and the target domain name to be analyzed is sent to the target intelligent domain name server, so that the target intelligent domain name server can determine the IP address of the client from the target domain name to be analyzed, and then intelligent domain name analysis is realized according to the IP address of the client.
In another embodiment of the present application, the introduction of the target intelligent domain name server for resolving the target domain name to be resolved is described, please refer to fig. 2, which may include:
and step S21, judging whether the suffix of the target domain name to be analyzed is a preset suffix.
If yes, go to step S22.
Step S22, the source domain name to be resolved and the IP address of the client are resolved from the target domain name to be resolved.
And step S23, determining the geographic position information corresponding to the IP address of the client.
Step S24, according to the domain name to be resolved of the source and the geographical location information corresponding to the IP address of the client, determining a target application server, and returning the IP address of the target application server to the client.
And after the IP address of the target application server is returned to the client, the client can access the target application server through the IP address of the target application server, and the target application server provides application service for the client.
In another embodiment of the present application, the determining the geographic location information corresponding to the IP address of the client is described with reference to fig. 3, and the determining may include:
and step S31, inquiring whether an IP address matched with the IP address of the client exists in the mapping relation library of the IP address and the geographic position information.
If so, go to step S32.
It should be noted that the mapping relationship library of the IP address and the geographic location information includes a plurality of different mapping relationships, and each mapping relationship records a mapping relationship between the IP address and the geographic location information.
The mapping relationship between the IP address and the geographical location information can be expressed as: ip, location, e.g., ip-1, location-1, ip-2, location-1, ip-3, location-1, ip-4, location-2, ip-5, location-2, ip-6, location-2.
Generally, the IP addresses of different users are consecutive in the same region. Therefore, the format of the mapping relation between the IP address and the geographic position information can be improved, the geographic position information of each IP does not need to be recorded one by one, and the IP section description is carried out on each piece of geographic position information, namely, an IP starting address and an IP ending address.
The format of the improved mapping relationship between the IP address and the geographical location information may be: location, ip-begin, ip-end, e.g.
location-1,ip-begin-1,ip-end-1、location-2,ip-begin-2,ip-end-2、location-3,ip-begin-3,ip-end-3。
With such a recording, the process of mapping from an IP address to geographical location information may be different when performing domain name resolution.
IP segments of two records are not allowed to have overlapping, etc., containing, etc. relationships. I.e. the IP segments of the different records should be independent of each other. If viewed as a set, each location corresponds to an IP set. The segmented recording is used because in reality, the IPs in this IP set are generally consecutive, so that one segment can be represented by two IP addresses.
A geographic location may contain multiple segments. Because the goal of the IP repository is to have a unique geographic location for an IP, a geographic location containing multiple segments does not destroy the goal. This approach is more consistent with real-world scenarios. Typically, the IP of one cell is a contiguous segment, but is separated from the IP segment of another cell by a relatively large distance.
Meanwhile, the IP address and geographic position information mapping relation library can be applied to various use scenes, such as a public network, and provides general domain name resolution service; or, an enterprise intranet; or a network structure between the public network and the intranet.
It should be noted that the network result between the public network and the intranet is determined by the characteristics of the radio and television system. The radio and television industry, generally a province and a network, provides services across provinces, and does not exist at present. However, the number of users in a province is also quite large, so that the intelligent domain name resolution system is also needed. For example, for a system providing pictures, assuming that the domain name is image. The number and density of nodes are related to the number of users and the activity level of each city or region.
Step S32, using the geographical location information corresponding to the IP address matching with the IP address of the client as the geographical location information corresponding to the IP address of the client.
In this embodiment, the geographic location information corresponding to the IP address matched with the IP address of the client in the mapping relationship library of the IP address and the geographic location information is used as the geographic location information corresponding to the IP address of the client.
Based on the content of the foregoing embodiment, in another embodiment of the present application, introducing the determining of the target application server according to the domain name to be resolved and the geographic location information corresponding to the IP address of the client, please refer to fig. 4, which may include:
step S41, querying in a policy information base whether there is a domain name and geographic location information that match the domain name to be resolved and the geographic location information corresponding to the IP address of the client.
If so, go to step S42.
In this embodiment, the policy information base includes a plurality of different mapping relationships, and each mapping relationship records a mapping relationship between a domain name, geographical location information corresponding to an IP address of a client, and an application server.
Step S42, taking the domain name matched with the domain name to be resolved and the geographic location information corresponding to the IP address of the client and the application server corresponding to the geographic location information as the target application server.
Under the condition that the domain name and the geographic position information corresponding to the IP address of the client are known, the corresponding application server can be determined.
It should be noted that, in the same domain name, there may be a situation where multiple application servers provide services, so that it is possible to prevent a certain application server from being overloaded to cause abnormal services.
When the same domain name is served by a plurality of application servers, a plurality of domain names matched with the domain name to be analyzed and the geographic position information corresponding to the IP address of the client, namely a plurality of target application servers, and the application servers corresponding to the geographic position information can be determined in the strategy information base. When a plurality of target application servers exist, the process of returning the IP address of the target application server to the client may include:
randomly selecting a target application server from a plurality of different target application servers, and returning the IP address of the randomly selected target application server to the client;
or returning the IP addresses of different target application servers to the client.
In another embodiment of the present application, another domain name resolution method is provided, and referring to fig. 5, the method may include:
and step S51, acquiring a domain name resolution request.
Step S52, obtaining the domain name to be resolved from the domain name resolution request, and using the domain name to be resolved as the source domain name to be resolved.
Steps S51-S52 are the same as steps S11-S12 described in the previous embodiment, and the detailed procedures of steps S51-S52 can be referred to the related descriptions of steps S11-S12, and are not described again here.
Step S53, determining whether the type of the domain name resolution server corresponding to the source domain name to be resolved is an intelligent domain name server.
If so, go to step S54, otherwise, go to step S58.
And step S54, determining the IP address of the client according to the domain name resolution request.
Step S55, the IP address of the client is encapsulated into the source domain name to be resolved to obtain a new domain name to be resolved, which is used as the target domain name to be resolved.
And step S56, inquiring the intelligent domain name server corresponding to the target domain name to be analyzed as the target intelligent domain name server.
Step S57, sending the target domain name to be resolved to a local domain name server, so that the local domain name server sends the target domain name to be resolved to the target intelligent domain name server, so that the target intelligent domain name server resolves the target domain name to be resolved.
Steps S54-S57 are the same as steps S13-S16 in the previous embodiment, and the detailed procedures of steps S54-S57 can be referred to the related descriptions of steps S13-S16, and are not described herein again.
And step S58, inquiring the ordinary domain name server corresponding to the source domain name to be analyzed as the target ordinary domain name server.
The ordinary domain name server is different from the intelligent domain name server, and the ordinary domain name server can not carry out intelligent domain name resolution but carries out domain name resolution in a traditional mode.
Step S59, sending the source domain name to be resolved to the target ordinary domain name server, so that the target ordinary domain name server resolves the source domain name to be resolved.
The process of the target ordinary domain name server for analyzing the domain name to be analyzed of the source is the same as the traditional domain name analyzing process in the prior art, and the description is omitted here.
Next, a domain name resolution system provided in the present application is introduced, and the domain name resolution system described below and the domain name resolution method described above may be referred to in correspondence.
Referring to fig. 6, a schematic diagram of a logical structure of a domain name resolution system provided in the present application is shown, where the domain name resolution system includes: a client 11, a local domain name server 12 and a target intelligent domain name server 13.
The client 11 is configured to:
acquiring a domain name resolution request;
acquiring a domain name to be resolved from the domain name resolution request as a source domain name to be resolved;
determining the IP address of the client 11 according to the domain name resolution request;
encapsulating the IP address of the client 11 into the source domain name to be resolved to obtain a new domain name to be resolved as a target domain name to be resolved;
inquiring an intelligent domain name server corresponding to the target domain name to be analyzed to be used as a target intelligent domain name server 13;
and sending the target domain name to be analyzed to a local domain name server 12, so that the local domain name server 12 sends the target domain name to be analyzed to the target intelligent domain name server 13, and the target intelligent domain name server 13 analyzes the target domain name to be analyzed.
The local domain name server 12 is configured to send the target domain name to be resolved to the target intelligent domain name server 13.
The target intelligent domain name server 13 is configured to analyze the domain name to be analyzed of the target.
In this embodiment, the target intelligent domain name server 13 may specifically be configured to:
judging whether the suffix of the target domain name to be analyzed is a preset suffix or not;
if the suffix of the target domain name to be analyzed is a preset suffix, analyzing the source domain name to be analyzed and the IP address of the client 11 from the target domain name to be analyzed;
determining geographic position information corresponding to the IP address of the client 11;
and determining a target application server according to the domain name to be resolved of the source and the geographical position information corresponding to the IP address of the client 11, and returning the IP address of the target application server to the client 11.
In this embodiment, the client 11 may further be configured to:
before determining the IP address of the client 11 according to the domain name resolution request, determining whether the type of the domain name resolution server corresponding to the source domain name to be resolved is an intelligent domain name server;
if yes, determining the IP address of the client 11 according to the domain name resolution request.
If not, inquiring a common domain name server corresponding to the source domain name to be analyzed as a target common domain name server;
and sending the domain name to be analyzed of the source to the target ordinary domain name server so that the target ordinary domain name server analyzes the domain name to be analyzed of the source.
In this embodiment, the target intelligent domain name server 13 may specifically be configured to:
inquiring whether an IP address matched with the IP address of the client 11 exists in an IP address and geographic position information mapping relation library;
and if so, taking the geographical location information corresponding to the IP address matched with the IP address of the client 11 as the geographical location information corresponding to the IP address of the client 11.
Based on the foregoing, the target intelligent domain name server 13 may specifically be configured to:
inquiring whether a domain name and geographical position information matched with the domain name to be analyzed and the geographical position information corresponding to the IP address of the client 11 exist in a strategy information base;
and if the domain name exists, taking the application server corresponding to the domain name to be analyzed and the geographic position information corresponding to the IP address of the client 11 as the target application server.
It should be noted that, in the present specification, the embodiments are all described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other. For the device-like embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present application may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments of the present application.
The domain name resolution method and system provided by the present application are introduced in detail, and a specific example is applied in the description to explain the principle and the implementation of the present application, and the description of the above embodiment is only used to help understanding the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (8)
1. A domain name resolution method is applied to a client, and comprises the following steps:
acquiring a domain name resolution request;
acquiring a domain name to be resolved from the domain name resolution request as a source domain name to be resolved;
determining the IP address of the client according to the domain name resolution request;
encapsulating the IP address of the client into the source domain name to be resolved to obtain a new domain name to be resolved as a target domain name to be resolved;
inquiring an intelligent domain name server corresponding to the target domain name to be analyzed as a target intelligent domain name server;
sending the target domain name to be analyzed to a local domain name server so that the local domain name server sends the target domain name to be analyzed to the target intelligent domain name server so that the target intelligent domain name server analyzes the target domain name to be analyzed;
the target intelligent domain name server analyzes the target domain name to be analyzed, and the method comprises the following steps:
judging whether the suffix of the target domain name to be analyzed is a preset suffix or not;
if the suffix of the target domain name to be analyzed is a preset suffix, analyzing the source domain name to be analyzed and the IP address of the client from the target domain name to be analyzed;
determining geographical location information corresponding to the IP address of the client;
and determining a target application server according to the domain name to be analyzed of the source and the geographical position information corresponding to the IP address of the client, and returning the IP address of the target application server to the client.
2. The method according to claim 1, wherein before determining the IP address of the client according to the domain name resolution request, further comprising:
judging whether the type of a domain name resolution server corresponding to the source domain name to be resolved is an intelligent domain name server or not;
if yes, determining the IP address of the client according to the domain name resolution request;
if not, inquiring a common domain name server corresponding to the source domain name to be analyzed as a target common domain name server;
and sending the domain name to be analyzed of the source to the target ordinary domain name server so that the target ordinary domain name server analyzes the domain name to be analyzed of the source.
3. The method of claim 1, wherein the determining the geographical location information corresponding to the IP address of the client comprises:
inquiring whether an IP address matched with the IP address of the client exists in an IP address and geographic position information mapping relation library;
and if so, taking the geographical location information corresponding to the IP address matched with the IP address of the client as the geographical location information corresponding to the IP address of the client.
4. The method according to claim 3, wherein the determining a target application server according to the domain name to be resolved and the geographic location information corresponding to the IP address of the client comprises:
inquiring whether a domain name and geographical position information matched with the domain name to be analyzed and the geographical position information corresponding to the IP address of the client exist in a strategy information base;
and if the domain name exists, taking the domain name matched with the domain name to be analyzed and the geographic position information corresponding to the IP address of the client as the target application server.
5. A domain name resolution system, comprising: the system comprises a client, a local domain name server and a target intelligent domain name server;
the client is used for:
acquiring a domain name resolution request;
acquiring a domain name to be resolved from the domain name resolution request as a source domain name to be resolved;
determining the IP address of the client according to the domain name resolution request;
encapsulating the IP address of the client into the source domain name to be resolved to obtain a new domain name to be resolved as a target domain name to be resolved;
inquiring an intelligent domain name server corresponding to the target domain name to be analyzed as a target intelligent domain name server;
sending the target domain name to be analyzed to a local domain name server so that the local domain name server sends the target domain name to be analyzed to the target intelligent domain name server so that the target intelligent domain name server analyzes the target domain name to be analyzed;
the local domain name server is used for sending the target domain name to be analyzed to the target intelligent domain name server;
the target intelligent domain name server is used for analyzing the domain name to be analyzed of the target;
the target intelligent domain name server is specifically configured to:
judging whether the suffix of the target domain name to be analyzed is a preset suffix or not;
if the suffix of the target domain name to be analyzed is a preset suffix, analyzing the source domain name to be analyzed and the IP address of the client from the target domain name to be analyzed;
determining geographical location information corresponding to the IP address of the client;
and determining a target application server according to the domain name to be analyzed of the source and the geographical position information corresponding to the IP address of the client, and returning the IP address of the target application server to the client.
6. The system of claim 5, wherein the client is further configured to:
before determining the IP address of the client according to the domain name resolution request, judging whether the type of a domain name resolution server corresponding to the source domain name to be resolved is an intelligent domain name server;
if yes, determining the IP address of the client according to the domain name resolution request;
if not, inquiring a common domain name server corresponding to the source domain name to be analyzed as a target common domain name server;
and sending the domain name to be analyzed of the source to the target ordinary domain name server so that the target ordinary domain name server analyzes the domain name to be analyzed of the source.
7. The system of claim 5, wherein the target intelligent domain name server is specifically configured to:
inquiring whether an IP address matched with the IP address of the client exists in an IP address and geographic position information mapping relation library;
and if so, taking the geographical location information corresponding to the IP address matched with the IP address of the client as the geographical location information corresponding to the IP address of the client.
8. The system of claim 7, wherein the target intelligent domain name server is specifically configured to:
inquiring whether a domain name and geographical position information matched with the domain name to be analyzed and the geographical position information corresponding to the IP address of the client exist in a strategy information base;
and if the domain name exists, taking the domain name matched with the domain name to be analyzed and the geographic position information corresponding to the IP address of the client as the target application server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810414510.1A CN108712515B (en) | 2018-05-03 | 2018-05-03 | Domain name resolution method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810414510.1A CN108712515B (en) | 2018-05-03 | 2018-05-03 | Domain name resolution method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108712515A CN108712515A (en) | 2018-10-26 |
| CN108712515B true CN108712515B (en) | 2021-05-11 |
Family
ID=63867699
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810414510.1A Active CN108712515B (en) | 2018-05-03 | 2018-05-03 | Domain name resolution method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108712515B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110769080B (en) * | 2019-10-30 | 2021-12-14 | 腾讯科技（深圳）有限公司 | Domain name resolution method, related product and computer readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102035905A (en) * | 2010-12-17 | 2011-04-27 | 北京世纪互联工程技术服务有限公司 | Method for obtaining visitor Local DNS (Local Domain-Name Server) |
| CN104519146A (en) * | 2013-09-29 | 2015-04-15 | 中国电信股份有限公司 | Method and system for domain name service based on user position |
| CN106790530A (en) * | 2016-12-21 | 2017-05-31 | 北京云端智度科技有限公司 | The tracking of domain name service and polymerization |
| CN107438115A (en) * | 2017-09-11 | 2017-12-05 | 深圳市茁壮网络股份有限公司 | A kind of domain name analytic method, apparatus and system |
| CN107623755A (en) * | 2017-09-30 | 2018-01-23 | 杭州安恒信息技术有限公司 | Intelligent DNS implementation method, device and electronic equipment based on study |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101640684A (en) * | 2009-08-21 | 2010-02-03 | 中国电信股份有限公司 | Content delivering method, network system, GSLB device and domain name server |
| CN102611763A (en) * | 2011-01-25 | 2012-07-25 | 中国移动通信集团公司 | DNS (Domain Name Server) inquiring method and equipment |
| CN105162898B (en) * | 2015-09-18 | 2019-03-19 | 互联网域名系统北京市工程研究中心有限公司 | DNS and DHCP, IPAM realize the method and device of intelligently parsing |
-
2018
- 2018-05-03 CN CN201810414510.1A patent/CN108712515B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102035905A (en) * | 2010-12-17 | 2011-04-27 | 北京世纪互联工程技术服务有限公司 | Method for obtaining visitor Local DNS (Local Domain-Name Server) |
| CN104519146A (en) * | 2013-09-29 | 2015-04-15 | 中国电信股份有限公司 | Method and system for domain name service based on user position |
| CN106790530A (en) * | 2016-12-21 | 2017-05-31 | 北京云端智度科技有限公司 | The tracking of domain name service and polymerization |
| CN107438115A (en) * | 2017-09-11 | 2017-12-05 | 深圳市茁壮网络股份有限公司 | A kind of domain name analytic method, apparatus and system |
| CN107623755A (en) * | 2017-09-30 | 2018-01-23 | 杭州安恒信息技术有限公司 | Intelligent DNS implementation method, device and electronic equipment based on study |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108712515A (en) | 2018-10-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2021120969A1 (en) | Domain name resolution method, domain name resolution server, and terminal device | |
| US9935921B2 (en) | Correlating nameserver IPv6 and IPv4 addresses | |
| US9300623B1 (en) | Domain name system cache integrity check | |
| US7908379B2 (en) | Automatic mobile device detection | |
| US9231903B2 (en) | System and method for resolving a DNS request using metadata | |
| CN102859942B (en) | Using DNS reflection to measure network performance | |
| US10171318B2 (en) | System and method of identifying internet-facing assets | |
| CN108600412B (en) | Domain name resolution method and system | |
| CN106068639A (en) | The Transparent Proxy certification processed by DNS | |
| US20030009591A1 (en) | Apparatus and method for managing internet resource requests | |
| WO2021004528A1 (en) | Method, device and apparatus for address acquisition of application example and storage medium | |
| CN112583952B (en) | Redirection scheduling processing method, device and system, related equipment and storage medium | |
| JP2007124655A (en) | Method for selecting functional domain name server | |
| CN112333299B (en) | Domain name resolution method, configuration method and equipment | |
| CN109327559A (en) | A kind of domain name analytic method and device based on mixing cloud platform | |
| CN115037720A (en) | Method and device for processing domain name resolution request, electronic equipment and storage medium | |
| CN111371914A (en) | IP library generation method, domain name resolution method, electronic device and readable storage medium | |
| CN108712515B (en) | Domain name resolution method and system | |
| CN108650338A (en) | A kind of domain name analytic method and system | |
| CN114500456B (en) | DNS (Domain name System) scheduling optimization method and device based on whole network sniffing and computing equipment | |
| CN112738271B (en) | CDN quality detection method, system and domain name server | |
| WO2023014523A1 (en) | Application security posture identifier | |
| EP2647179B1 (en) | Service access apparatus, method, computer program and computer program product for selective initiation of communication | |
| CN111447297B (en) | IPv4 and IPv6 DNS unified access management method and system | |
| CN111491033A (en) | Connection establishing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |