WO2012010084A1 - 一种域名解析方法及装置 - Google Patents

一种域名解析方法及装置 Download PDF

Info

Publication number
WO2012010084A1
WO2012010084A1 PCT/CN2011/077344 CN2011077344W WO2012010084A1 WO 2012010084 A1 WO2012010084 A1 WO 2012010084A1 CN 2011077344 W CN2011077344 W CN 2011077344W WO 2012010084 A1 WO2012010084 A1 WO 2012010084A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain name
name information
name resolution
level
level domain
Prior art date
Application number
PCT/CN2011/077344
Other languages
English (en)
French (fr)
Inventor
曹振
Original Assignee
中国移动通信集团公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中国移动通信集团公司 filed Critical 中国移动通信集团公司
Publication of WO2012010084A1 publication Critical patent/WO2012010084A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping
    • H04L61/4505Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a domain name resolution method and apparatus. Background technique
  • the Domain Name System is the basis for realizing the Internet service.
  • the main function of the DNS is to resolve the address of the server where the Internet resource requested by the host is located according to the request of the host to access the Internet resource, and then feed the address back to the host.
  • the host communicates with the server through this address to obtain Internet resources. For example, when the host needs to access the website with the domain name www.chinamobile.com, it first sends a domain name resolution request (or DNS query request) containing the domain name information to the DNS server, and the DNS server determines the corresponding destination of www.chinamobile.com through recursive query.
  • the server address (such as 218.206.191.72), and the server address is provided to the host, and the host connects to the corresponding server through the server address for subsequent communication.
  • FIG. 1 is a schematic diagram of a process for a DNS server to resolve an address according to a domain name resolution request of a host. As shown in FIG. 1 , the parsing process mainly includes the following steps:
  • Step 101 The host sends a domain name resolution request to the DNS server, where the domain name resolution request includes domain name information to be resolved, for example, www.chinamobile.com;
  • Step 102 After receiving the domain name resolution request sent by the host, the DNS server sends a domain name resolution request to the root domain name resolution server (Root server) to request the root server to determine the top-level domain name information (.com) in the domain name information to be resolved.
  • Step 103 The root server queries the top-level domain name resolution server (.com server) address corresponding to the top-level domain name information (.com), and returns the top-level domain name resolution server address to the DNS server.
  • .com server top-level domain name resolution server
  • Step 104 The DNS server parses the server address according to the top-level domain name, and sends a domain name resolution request to the top-level domain name resolution server corresponding to the address, to request the top-level domain name resolution server to determine the non-top-level domain name in the domain name information to be resolved (.chinamobile. Com) corresponding non-top-level domain name resolution server (.chinamobile.com server) address;
  • Step 105 The top-level domain name resolution server queries the non-top-level domain name resolution server (.chinamobile.com server) address corresponding to the non-top-level domain name information (.chinamobile.com), and returns the non-top-level domain name resolution server address to the DNS server;
  • Step 107 The non-top-level domain name resolution server queries the server address corresponding to the domain name to be resolved, and returns the server address to the DNS server.
  • Step 108 The DNS server returns the server address to the host.
  • the DNS server needs to interact with the address resolution server corresponding to the domain name information at multiple levels to determine the server address corresponding to the domain name information to be resolved. It can be seen that the delay of the host accessing the Internet mainly comes from the time taken by the DNS server to resolve the server address.
  • some DNS servers provide a temporary caching mechanism. After the DNS server resolves the server address corresponding to the domain name information included in the domain name resolution request sent by the host, the domain name information is cached. If the domain name information is included in the domain name resolution request sent by the host again, the server address corresponding to the domain name information may be directly provided to the host according to the corresponding relationship of the cache.
  • the delay of the host requesting access to the domain name information of the cache record can be reduced.
  • the DNS server determines the server address corresponding to the domain name information through multiple queries.
  • the cache mechanism provided by the prior art can only reduce the delay of obtaining the server address corresponding to the domain name information when the host accesses part of the domain name of the cache record, and the DNS server usually needs to resolve various domain names from many hosts.
  • the request is parsed. Therefore, using the above caching mechanism, the processing efficiency of the domain name resolution request of the host served by the DNS server is still not improved overall.
  • the embodiment of the present invention provides a domain name parsing method and apparatus, which can improve the processing efficiency of a domain name resolution request for a host as a whole.
  • a domain name resolution method including:
  • a domain name resolution apparatus including:
  • a receiving unit configured to receive a domain name resolution request, where the domain name resolution request includes domain name information to be parsed;
  • the first correspondence relationship holding unit is configured to save a correspondence between the top-level domain name information and the top-level domain name resolution server address;
  • a first address determining unit configured to determine, according to the correspondence between the top-level domain name information and the top-level domain name resolution server address saved by the first correspondence relationship holding unit, the domain name to be resolved included in the domain name resolution request received by the receiving unit
  • the top-level domain name resolution server address corresponding to the top-level domain name information in the information
  • the second address determining unit is configured to obtain the server address corresponding to the domain name information to be resolved according to the top-level domain name resolution server address determined by the first address determining unit.
  • the correspondence between the saved top-level domain name information and the top-level domain name resolution server address may be directly determined.
  • the top-level domain name resolution server address corresponding to the top-level domain name information of the domain name compared with the prior art, saves various domain name resolution requests from each host, and saves the interaction with the root domain name resolution server to determine the top-level domain name resolution server corresponding to the top-level domain name information.
  • the time of the address therefore, the technical solution can improve the processing efficiency of the domain name resolution request of the served host as a whole.
  • 1 is a flowchart of a DNS server parsing address provided by the background art of the present invention
  • FIG. 2 is a flowchart of a correspondence between a top-level domain name and an address stored by a DNS server according to Embodiment 1 of the present invention
  • FIG. 3 is a flowchart of a domain name parsing method according to Embodiment 1 of the present invention.
  • FIG. 4 is a flowchart of determining an address corresponding to a top-level domain name of a domain name included in a domain name resolution request according to Embodiment 1 of the present invention
  • FIG. 5 is a flowchart of storing a correspondence between a well-known domain name and an address by a DNS server according to Embodiment 2 of the present invention
  • FIG. 6 is a flowchart of a domain name parsing method according to Embodiment 2 of the present invention.
  • FIG. 7 is a flowchart of a domain name parsing method according to Embodiment 3 of the present invention.
  • FIG. 8 is a first schematic diagram of a domain name resolution apparatus according to an embodiment of the present invention.
  • FIG. 9 is a second schematic diagram of a domain name resolution apparatus according to an embodiment of the present disclosure.
  • FIG. 10 is a third schematic diagram of a domain name resolution apparatus according to an embodiment of the present invention. detailed description
  • the embodiment of the present invention provides a domain name resolution method and apparatus.
  • the preferred embodiment of the present invention will be described below with reference to the accompanying drawings.
  • the preferred embodiments described herein are for illustrative purposes only and are not intended to limit the invention. And in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.
  • the address of the top-level domain name resolution server corresponding to each top-level domain name information is first obtained, and the correspondence between the top-level domain name information and the corresponding top-level domain name resolution server address is saved in the DNS server.
  • the DNS server can determine the domain name information to be resolved included in the received domain name resolution request by searching the correspondence between the top-level domain name information and the corresponding top-level domain name resolution server address each time the domain name resolution request sent by the host is received.
  • the top-level domain name resolution server address corresponding to the top-level domain name information does not need to send a domain name resolution request for parsing the top-level domain name resolution server address corresponding to the top-level domain name information to the root domain name resolution server.
  • FIG. 2 is a schematic flowchart of the correspondence between the top-level domain name information and the top-level domain name resolution server address of the DNS server. As shown in FIG. 2, the process mainly includes the following steps:
  • Step 201 The DNS server sends a top-level domain name resolution request to the root domain name resolution server, where the top-level domain name resolution request includes the top-level domain name information to be resolved.
  • Step 202 After receiving the top-level domain name resolution request sent by the DNS server, the root domain name resolution server queries the top-level domain name resolution server address corresponding to the top-level domain name information included in the top-level domain name resolution request.
  • Step 203 The root domain name resolution server feeds back the queried top-level domain name resolution server address to the DNS server.
  • the DNS server receives the top-level domain name resolution server address fed back by the root domain name resolution server, and saves the top-level domain name information and the top-level domain name resolution. The correspondence of server addresses.
  • the top-level domain name resolution server address corresponding to each top-level domain name may be obtained in advance, and the correspondence between the top-level domain name information and the corresponding top-level domain name resolution server address is saved, where the address corresponding to the top-level domain name information is corresponding to the top-level domain name information.
  • the address of the top-level domain name resolution server which is used to provide the address of the non-top-level domain name resolution server corresponding to the non-top-level domain name under the top-level domain name.
  • the correspondence between the saved top-level domain name information and the top-level domain name resolution server address may be differentiated according to different types of top-level domain name information, that is, according to the type of the top-level domain name information included in the received top-level domain name resolution request,
  • the mapping between the top-level domain name information and the top-level domain name resolution server address included in the top-level domain name resolution request to further improve the search speed of the top-level domain name resolution server address corresponding to the top-level domain name information during domain name resolution for example, the top-level domain name type can be organized by The domain, country domain, and special domain are divided.
  • the top-level domain of the organization domain type includes: .edu, .gov, .com.
  • the country domain type top-level domain name can include The country domain in IS03 166, for example: .cn, .us, .jp, etc.;
  • the top-level domain name of the special domain type may include a top-level domain name for address-to-name conversion, such as .arpa, the top-level domain name of the special domain type generally includes High-frequency access to top-level domains.
  • mapping between the top-level domain name information and the top-level domain name resolution server address can be continuously expanded according to actual business needs and user access requirements.
  • the correspondence between the saved top-level domain name information and the top-level domain name resolution server address may be updated periodically, for example, the saved correspondence relationship is updated according to the set period.
  • a timer is set for each group of the top-level domain name information and the top-level domain name resolution server address.
  • the domain name resolution server sends a domain name resolution request including the set top-level domain name information, and is used to re-acquire the address of the top-level domain name resolution server corresponding to the set top-level domain name, and update the saved top level according to the address fed back by the root domain name resolution server.
  • the correspondence between domain name information and addresses is used to re-acquire the address of the top-level domain name resolution server corresponding to the set top-level domain name, and update the saved top level according to the address fed back by the root domain name resolution server.
  • a timer can be set for the correspondence between the top-level domain name information and the address established at the same time.
  • the DNS server can determine the domain name information to be resolved according to the saved correspondence relationship, based on the mapping between the top-level domain name information and the top-level domain name resolution server address.
  • the top-level domain name corresponding to the top-level domain name resolves the server address, and the address of the top-level domain name resolution server determined by the M is obtained, and the server address corresponding to the domain name information to be resolved is obtained.
  • the process of obtaining the server address corresponding to the domain name information to be resolved according to the determined top-level domain name resolution server address includes: sending the domain name resolution request to the determined top-level domain name resolution server corresponding to the determined top-level domain name resolution server address, and receiving The top-level domain name resolution server queries and feeds back the non-top-level domain name resolution server address corresponding to the non-top-level domain name information in the domain name information to be resolved according to the domain name information to be resolved included in the domain name resolution request, and further according to the non-top level
  • the domain name resolution server address is obtained, and the server address corresponding to the domain name information to be resolved is obtained.
  • the process of obtaining the server address corresponding to the domain name information to be resolved according to the determined non-top-level domain name resolution server address that is, the process of performing subsequent domain name resolution by the non-top-level domain name resolution server
  • the non-top-level domain name information One or more non-top-level domain name resolution servers may be corresponding to each other. If the non-top-level domain name information corresponds to a non-top-level domain name resolution server, the non-top-level domain name resolution server may be directly parsed and obtained.
  • the server address corresponding to the domain name information is parsed; if the non-top domain name information corresponds to multiple non-top-level domain name resolution servers, for example, the non-top-level domain name information may be divided into multiple sub-top-level domain names corresponding to different priorities, and each of the child non-top-level domain names respectively corresponds to one
  • the non-top-level domain name resolution server can determine the server address corresponding to the domain name information to be resolved by accessing the non-top-level domain name resolution server corresponding to each of the child non-top-level domain names.
  • FIG. 3 is a schematic flowchart of a domain name resolution method according to Embodiment 1 of the present invention. As shown in FIG. 3, the process mainly includes the following steps:
  • Step 301 The DNS server receives a domain name resolution request sent by the host, where the domain name resolution request includes domain name information to be resolved.
  • Step 302 Determine, according to the correspondence between the saved top-level domain name information and the top-level domain name resolution server address, the top-level domain name resolution server address corresponding to the top-level domain name information in the domain name information included in the received domain name resolution request, and determine the address
  • the corresponding top-level domain name resolution server sends a domain name resolution request, where the domain name resolution request includes the domain name information to be resolved.
  • Step 303 Receive, by the top-level domain name resolution server, the non-top-level domain name resolution server address corresponding to the non-top-level domain name information in the domain name information to be parsed according to the domain name information to be resolved included in the domain name resolution request, and The non-top-level domain name resolution server corresponding to the address sends a domain name resolution request, where the domain name resolution request includes domain name information to be resolved;
  • Step 304 Receive, by the non-top-level domain name resolution server, the server address corresponding to the domain name information to be parsed according to the domain name information included in the domain name resolution request, and feed back the received server address to the host.
  • the server address corresponding to the domain name information to be resolved included in the domain name resolution request sent by the host may be determined. After determining the server address through the foregoing process, the DNS server feeds back the address to the host.
  • the technical solution provided in the first embodiment optimizes the process of querying the address of the DNS server after the active storage of the correspondence between the top-level domain name information and the top-level domain name resolution server address, and the DNS server is compared with the traditional domain name resolution process shown in FIG. It is not necessary to perform the steps 102 to 103, and only the top-level domain name resolution server corresponding to the top-level domain name information in the domain name information to be resolved included in the domain name resolution request sent by the host is determined according to the mapping relationship between the locally stored top-level domain name information and the address. address.
  • the top-level domain name resolution server address query process corresponding to the top-level domain name information is actively acquired and stored, because all non-top-level domain names are under the jurisdiction of the top-level domain name, and the number of top-level domain names is small, so The cache efficiency is high, which is important for reducing the delay of the host to obtain the address.
  • the present application further proposes an optimization scheme for the foregoing embodiment, that is, in order to reduce the burden of the DNS server storing the correspondence between the top-level domain name and the top-level domain name resolution server address, the top-level domain name with low access frequency may not be saved.
  • the DNS determines, according to the received domain name resolution request, a process of determining the top-level domain name resolution server address corresponding to the top-level domain name information in the domain name information included in the request, as shown in FIG. 4 . Including the following steps:
  • Step 401 The DNS server receives a domain name resolution request sent by the host, where the domain name resolution request includes domain name information to be resolved.
  • Step 402 Search for a correspondence between the saved top-level domain name information and the top-level domain name resolution server address according to the top-level domain name information of the domain name information to be resolved according to the domain name resolution request.
  • Step 403 Determine whether the corresponding relationship between the top-level domain name information and the top-level domain name resolution server address in the domain name to be resolved included in the received domain name resolution request is found, and if yes, go to step 404, if no, go to step 405;
  • Step 404 Determine, according to the found correspondence, the address of the top-level domain name resolution server corresponding to the top-level domain name information, and the process ends.
  • Step 405 Obtain a top-level domain name resolution server address corresponding to the top-level domain name information from the root domain name resolution server.
  • the top-level domain name and the top-level domain name resolution server of the domain name included in the domain name resolution request sent by the host are reduced on the basis of reducing the burden of the DNS server storing the correspondence between the top-level domain name and the top-level domain name resolution server address. If the corresponding relationship exists, the delay of obtaining the address by the host can be reduced.
  • the DNS server may perform domain name resolution on a well-known domain name (for example, a domain name with a high access frequency), and save the correspondence between the well-known domain name and the resolved server address in the DNS server.
  • the DNS server can find the correspondence between the domain name information and the server address included in the domain name resolution request according to the corresponding relationship, and if the DNS server obtains the domain name resolution request, the DNS server can directly obtain the domain name.
  • the server address corresponding to the information if not present, can perform the method as described in the first embodiment.
  • the process of the DNS server storing the correspondence between the well-known domain name information and the server address mainly includes the following steps:
  • Step 501 The DNS server collects the number of times the same domain name is set in the domain name resolution request sent by the host.
  • Step 502 Determine whether the number of times reaches the set threshold. If yes, go to step 503. If no, go back to step 501;
  • Step 503 Parse the server address corresponding to the set domain name information, and save the correspondence between the set domain name information and the parsed server address.
  • the domain name provided by the second embodiment is based on the corresponding relationship between the well-known domain name information and the server address.
  • the parsing method, as shown in Figure 6, includes the following steps:
  • Step 601 The DNS server receives the domain name resolution request sent by the host, where the domain name resolution request includes the domain name information to be resolved.
  • Step 602 Search for a correspondence between the saved well-known domain name information and the server address according to the domain name information to be resolved included in the domain name resolution request.
  • Step 603 Determine whether the received domain name resolution request includes the correspondence between the domain name information to be resolved and the server address, and if yes, go to step 604, if no, go to step 605;
  • Step 604 Determine, according to the found correspondence, a server address corresponding to the domain name information to be parsed, and the process ends.
  • Step 605 Determine, according to the technical solution provided in FIG. 3 of the first embodiment, the server address corresponding to the domain name information to be parsed (that is, perform steps 302 to 304 of the corresponding process in FIG. 3 in the first embodiment), and the process ends.
  • the address query process of the well-known domain name is actively acquired and stored, because the well-known domain name query concentrates most of the DNS queries of the host, which plays an important role in reducing the delay of the host obtaining the address.
  • the DNS server when the DNS server receives a domain name resolution request for a website corresponding to a domain name (for example, www.163.com), it also has a domain name resolution request for another domain name, for example, www.youdao.conu www. 126.com, img2.163.com and other domain names, there is a high degree of correlation between these domains, that is, each time the host initiates a domain name resolution request for www.163.com, it may also include www.youdao.com
  • the domain name resolution request of the domain name such as www.126.com and img2.163.com. Therefore, in the domain name resolution method provided in the third embodiment, the associated domain name information associated with the set domain name information is first determined, and then respectively obtained.
  • the server address corresponding to the domain name information and the associated domain name information of the associated relationship is set, and the correspondence between the set domain name information and the associated domain name information and the server address is stored in the DNS server, and the DNS server receives the host
  • the domain name information to be resolved (referred to as the associated domain name) and the domain name resolution request of the associated domain name having the associated relationship are sent, the corresponding Lines is determined to be resolved domain name server address information and its associated domain name information included in the domain name resolution request respectively corresponding to.
  • the domain name may be a domain name with a high access frequency, that is, the DNS server collects the number of times the domain name resolution request sent by the host includes the same domain name, and when the number reaches the set threshold, it is determined.
  • the correspondence between the set domain name and its associated domain name and the server address needs to be established in advance.
  • the associated domain name that is associated with the set domain name may be determined by the following two methods:
  • the associated domain name corresponding to the domain name is determined.
  • the source code database includes the associated domain name corresponding to the page corresponding to the set domain name.
  • the image or video in the page corresponding to the set domain name may need to be linked to another domain name to make the image or
  • the video is displayed under the page corresponding to the set domain name, and the domain name used to identify the image or video source is the set domain.
  • the corresponding associated domain name is the domain name used to identify the image or video source.
  • the domain name is determined to be the associated domain name of the set domain name.
  • the correspondence between the saved associated domain name information and the associated domain name information and the server address may be updated periodically, specifically, the correspondence between each group of associated domain name information and the associated domain name information and the server address respectively.
  • Setting a timer separately when the timer set for the correspondence between the associated domain name information and the associated domain name information and the server address respectively times out, re-determining the associated domain name corresponding to the set domain name, and obtaining the set domain name and its association The address corresponding to the domain name, and the updated correspondence between the set domain name information and the associated domain name information and the address respectively.
  • a timer may be set for the correspondence between the set domain name and its associated domain name established at the same time and the address respectively.
  • Step 701 The DNS server receives the domain name resolution request sent by the host, where the domain name resolution request includes the domain name information to be resolved and the associated domain name information corresponding to the domain name to be resolved.
  • Step 702 Search for the corresponding relationship between the saved associated domain name information and the associated domain name information and the server address according to the domain name information and the associated domain name information included in the received domain name resolution request.
  • Step 703 Determine whether the domain name information to be resolved included in the domain name resolution request and the corresponding relationship between the domain name information and the server address are included in the domain name resolution request, and if yes, go to step 704. If no, go to step 705; Step 704, according to the search The corresponding relationship is determined, and the server address corresponding to the domain name information to be resolved and the associated domain name information included in the domain name resolution request are determined, and the process ends.
  • Step 705 Determine, by using the method provided in the first embodiment, a server address corresponding to each domain name information in which the corresponding relationship is not found, and the process ends.
  • step 705 that is, for each domain name where the address is not found:
  • Steps 302 to 304 of the corresponding flow in FIG. 3 in the first embodiment are not mentioned here.
  • the server address corresponding to the domain name information and the associated domain name information is actively acquired and stored.
  • the relationship with the set domain name is associated.
  • the address corresponding to the associated domain name information is stored in the DNS server, which reduces the time for the web page to be presented, and improves the efficiency of the host to obtain the address; on the other hand, improves the user's other domain triggered for the set domain name.
  • the resolution efficiency of the name domain name resolution request is actively acquired and stored.
  • Embodiment 4 of the present invention combines the foregoing Embodiment 1 and Embodiment 3 to implement domain name resolution, that is,
  • the server address corresponding to the domain name to be resolved included in the domain name resolution request may be determined by using the first correspondence relationship (refer to the first embodiment for the specific determination process); and determining the domain name resolution request.
  • the server address corresponding to the associated domain name included in the domain name resolution request is determined by the second correspondence.
  • the parsing device includes:
  • the receiving unit 801 is configured to receive a domain name resolution request, where the domain name resolution request includes domain name information to be parsed;
  • the first correspondence relationship holding unit 804 is configured to save a correspondence relationship between the top-level domain name information and the top-level domain name resolution server address;
  • the first address determining unit 802 is configured to determine, according to the correspondence between the top-level domain name information and the top-level domain name resolution server address saved by the first correspondence relationship holding unit 804, the top-level domain name in the domain name information included in the domain name resolution request received by the receiving unit 801.
  • the top-level domain name resolution server address corresponding to the information;
  • the second address determining unit 803 is configured to obtain the server address corresponding to the domain name information to be resolved according to the top-level domain name resolution server address determined by the first address determining unit 802.
  • the apparatus shown in FIG. 8 includes a second address determining unit.
  • the top-level domain name resolution server corresponding to the address determined by the first address determining unit 802 sends a domain name resolution request
  • the non-top-level domain name resolution server Receiving, by the top-level domain name resolution server, the non-top-level domain name resolution server address corresponding to the non-top-level domain name information in the domain name information to be resolved according to the domain name information to be resolved included in the domain name resolution request;
  • the server address corresponding to the domain name information to be resolved is obtained according to the non-top-level domain name resolution server address.
  • the apparatus shown in FIG. 8 includes a second address determining unit 803, specifically configured to: Sending a domain name resolution request to the non-top-level domain name resolution server corresponding to the determined non-top-level domain name resolution server address, and receiving the domain name information included in the domain name resolution request by the non-top-level domain name resolution server, and querying and feeding back the domain name information to be resolved Server address.
  • the apparatus shown in FIG. 8 includes a first correspondence storage unit 804, specifically configured to:
  • the server address stores the correspondence between the top-level domain information included in the top-level domain name resolution request and the received top-level domain name resolution server address.
  • the apparatus shown in FIG. 8 includes a first correspondence storage unit 804, specifically configured to:
  • the category stores the top-level domain name information included in the top-level domain name resolution request and the correspondence between the top-level domain name resolution server address according to the type of the top-level domain name information included in the received top-level domain name resolution request.
  • the apparatus shown in FIG. 8 includes a first correspondence relationship holding unit 804, which is further configured to:
  • the saved correspondence relationship is updated according to the set period.
  • the apparatus shown in FIG. 8 may further include:
  • the first address determining unit 802 is specifically configured to: when the determination result of the first determining unit 806 is negative, determine the correspondence between the saved top-level domain name information and the top-level domain name resolution server address, and determine the domain name information to be resolved.
  • the top-level domain name resolution server address corresponding to the top-level domain information
  • the third address determining unit 807 is configured to determine, when the determination result of the first determining unit 806 is YES, the server address corresponding to the domain name information to be resolved according to the existing corresponding relationship.
  • the apparatus shown in FIG. 9 includes a second correspondence storage unit 805, specifically configured to:
  • the apparatus shown in FIG. 8 includes a receiving unit 801, specifically configured to:
  • domain name resolution request includes the domain name information to be resolved and the associated domain name information associated with the domain name information to be resolved;
  • the apparatus shown in FIG. 8 may further include:
  • the second determining unit 809 is configured to determine, according to the correspondence between the domain name information saved by the third correspondence relationship holding unit 808 and the associated domain name information of the associated relationship and the server address, whether there is a to-be-resolved included in the received domain name resolution request.
  • the correspondence between the domain name information and the associated domain name information in which the relationship exists is respectively associated with the server address;
  • the fourth address determining unit 810 is configured to: when the determination result of the second determining unit 809 is YES, determine, according to the existing correspondence, the domain name information to be resolved included in the domain name resolution request and the associated domain name information in which the association relationship exists respectively Server address;
  • the first address determining unit 802 is specifically configured to determine, when the determination result of the second determining unit 809 is YES, the top-level domain name resolution server address corresponding to the top-level domain name information in the domain name information to be resolved, and determine the associated domain name information respectively.
  • the apparatus shown in FIG. 10 includes a third correspondence storage unit 808, specifically configured to:
  • the units included in the above domain name resolution device are only logically divided according to the functions implemented by the device. In actual applications, the superposition or splitting of the above units may be performed.
  • the function implemented by the domain name resolution device provided by the embodiment corresponds to the flow of the domain name resolution method provided by the foregoing embodiment, and the more detailed processing flow implemented by the device is described in detail in the foregoing method embodiment. , will not be described in detail here.
  • the correspondence between the saved top-level domain name information and the top-level domain name resolution server address may be directly determined.
  • the top-level domain name resolution server address corresponding to the top-level domain name information of the domain name compared with the prior art, saves various domain name resolution requests from each host, and saves the interaction with the root domain name resolution server to determine the top-level domain name resolution server corresponding to the top-level domain name information.
  • the time of the address therefore, the adoption of this technical solution can improve the overall service The processing efficiency of the host's domain name resolution request.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.
  • a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Transfer Between Computers (AREA)

Description

一种域名解析方法及装置 本申请要求在 2010年 7月 22日提交中国专利局、 申请号为 201010236357.1、发明名称 为 "一种域名解析方法及装置" 的中国专利申请的优先权, 其全部内容通过引用结合在本 申请中。
技术领域
本发明涉及通信技术领域, 尤其涉及一种域名解析方法及装置。 背景技术
域名系统(Domain Name System, DNS )是实现互联网业务的基础, DNS的主要作用 在于根据主机访问互联网资源的请求, 解析出主机请求访问的互联网资源所在服务器的地 址, 然后将该地址反馈给主机, 主机通过该地址与服务器进行通信, 获取互联网资源。 例 如, 主机需要访问域名为 www.chinamobile.com的网站时, 首先发送包含该域名信息的域 名解析请求(或称为 DNS 查询请求)到 DNS 服务器, DNS服务器通过递归查询确定 www.chinamobile.com对应的服务器地址(如 218.206.191.72 ), 并将该服务器地址提供给 主机, 主机则通过该服务器地址连接相应的服务器进行后续通信。
图 1示出了 DNS服务器根据主机的域名解析请求解析地址的流程示意图, 如图 1所 示, 该解析过程主要包括如下步骤:
步骤 101、主机向 DNS服务器发送域名解析请求, 该域名解析请求中包括待解析的域 名信息, 例如, www.chinamobile.com;
步骤 102、 DNS服务器接收主机发送的域名解析请求后, 向根域名解析服务器(Root 服务器)发送域名解析请求,以请求 Root服务器确定该待解析的域名信息中的顶级域名信 息 ( .com )对应的顶级域名解析服务器(.com服务器)地址;
步骤 103、 Root服务器查询该顶级域名信息( .com )对应的顶级域名解析服务器( .com 服务器)地址, 并向 DNS服务器返回该顶级域名解析服务器地址;
步骤 104、 DNS服务器根据该顶级域名解析服务器地址, 向该地址对应的顶级域名解 析服务器发送域名解析请求, 以请求该顶级域名解析服务器确定该待解析的域名信息中的 非顶级域名 ( .chinamobile.com )对应的非顶级域名解析服务器( .chinamobile.com服务器) 地址;
步骤 105、 顶级域名解析服务器查询该非顶级域名信息(.chinamobile.com )对应的非 顶级域名解析服务器( .chinamobile.com服务器)地址, 并向 DNS服务器返回该非顶级域 名解析服务器地址; 步骤 106、 DNS服务器根据该非顶级域名解析服务器地址, 向该地址对应的非顶级域 名解析服务器发送域名解析请求, 以请求该非顶级域名解析服务器确定待解析域名 ( www.chinamobile.com )对应的月艮务器地址;
步骤 107、 非顶级域名解析服务器查询该待解析域名对应的服务器地址, 并向 DNS服 务器返回该服务器地址;
步骤 108、 DNS服务器将该服务器地址返回给主机。
至此, DNS服务器对主机发送的域名解析请求进行解析的流程结束。
根据上述流程, 在 DNS服务器对主机发送的域名解析请求进行解析的过程中, DNS 服务器需要多次与各级域名信息对应的地址解析服务器交互以确定出待解析的域名信息 对应的服务器地址, 由此可见, 主机访问互联网的延迟主要来自 DNS服务器解析服务器 地址的过程所耗费的时间。
针对上述问题, 为了降低 DNS服务器查询地址的延迟, 一些 DNS服务器提供了临时 的緩存机制, DNS服务器在解析出主机发送的域名解析请求中包括的域名信息对应的服务 器地址后, 緩存该域名信息与该服务器地址的对应关系, 在主机再次发送的域名解析请求 中包括该域名信息时, 则可以直接根据緩存的该对应关系, 将该域名信息对应的服务器地 址提供给主机。
基于上述緩存技术, 只能减少主机请求访问存在緩存记录的域名信息时的延迟, 实际 应用中, 互联网系统存在成百上千万的域名, 对于 DNS服务器而言, 由于存储能力的限 制,只能提供针对主机访问的特定域名信息的临时緩存机制,并且在緩存有效时间到达后, 删除保存的緩存记录, 因此, 如果主机访问的互联网的域名信息与服务器地址的对应关系 未被緩存, 则仍然需要 DNS服务器通过多次查询以确定该域名信息对应的服务器地址。
综上所述, 现有技术提供的緩存机制, 只能减少主机访问存在緩存记录的部分域名时 获得该域名信息对应的服务器地址的延迟, 而 DNS服务器通常需要对来自众多主机的各种 域名解析请求进行解析, 因此, 釆用上述緩存机制, DNS服务器对所服务的主机的域名解 析请求的处理效率仍然得不到整体提高。 发明内容
有鉴于此, 本发明实施例提供一种域名解析方法及装置, 采用该技术方案, 能够整体 提高对主机的域名解析请求的处理效率。
本发明实施例通过如下技术方案实现:
根据本发明实施例的一个方面, 提供了一种域名解析方法, 包括:
接收域名解析请求, 所述域名解析请求中包括待解析的域名信息;
根据保存的顶级域名信息与顶级域名解析服务器地址的对应关系, 确定所述待解析的 域名信息中的顶级域名信息对应的顶级域名解析服务器地址;
根据确定出的所述顶级域名解析服务器地址, 获取所述待解析的域名信息对应的服务 器地址。
根据本发明实施例的另一个方面, 还提供了一种域名解析装置, 包括:
接收单元, 用于接收域名解析请求, 所述域名解析请求中包括待解析的域名信息; 第一对应关系保存单元, 用于保存顶级域名信息与顶级域名解析服务器地址的对应关 系;
第一地址确定单元, 用于才 据所述第一对应关系保存单元保存的顶级域名信息与顶级 域名解析服务器地址的对应关系, 确定所述接收单元接收的域名解析请求中包括的待解析 的域名信息中的顶级域名信息对应的顶级域名解析服务器地址;
第二地址确定单元, 用于根据所述第一地址确定单元确定出的所述顶级域名解析服务 器地址, 获取所述待解析的域名信息对应的服务器地址。
通过本发明实施例提供的上述至少一个技术方案, 在接收包括待解析的域名信息的域 名解析请求后, 可根据保存的顶级域名信息与顶级域名解析服务器地址的对应关系, 直接 确定出该待解析域名的顶级域名信息对应的顶级域名解析服务器地址, 与现有技术相比, 针对来自各主机的各种域名解析请求, 节省了与根域名解析服务器交互以确定顶级域名信 息对应的顶级域名解析服务器地址的时间, 因此, 采用该技术方案能够整体提高对所服务 的主机的域名解析请求的处理效率。
本发明的其它特征和优点将在随后的说明书中阐述, 并且, 部分地从说明书中变得显 而易见, 或者通过实施本发明而了解。 本发明的目的和其他优点可通过在所写的说明书、 权利要求书、 以及附图中所特别指出的结构来实现和获得。 附图说明
附图用来提供对本发明的进一步理解, 并且构成说明书的一部分, 与本发明实施例一 起用于解释本发明, 并不构成对本发明的限制。 在附图中:
图 1为本发明背景技术提供的 DNS服务器解析地址的流程图;
图 2为本发明实施例一提供的 DNS服务器保存各顶级域名与地址的对应关系的流程 图;
图 3为本发明实施例一提供的域名解析方法流程图;
图 4为本发明实施例一提供的确定域名解析请求中包括的域名的顶级域名对应的地址 的流程图;
图 5为本发明实施例二提供的 DNS服务器保存各知名域名与地址的对应关系的流程 图; 图 6为本发明实施例二提供的域名解析方法流程图;
图 7为本发明实施例三提供的域名解析方法流程图;
图 8为本发明实施例提供的域名解析装置示意图一;
图 9为本发明实施例提供的域名解析装置示意图二;
图 10为本发明实施例提供的域名解析装置示意图三。 具体实施方式
为了给出整体提高对主机的域名解析请求的处理效率的实现方案, 本发明实施例提供 了一种域名解析方法及装置, 以下结合说明书附图对本发明的优选实施例进行说明, 应当 理解, 此处所描述的优选实施例仅用于说明和解释本发明, 并不用于限定本发明。 并且在 不冲突的情况下, 本申请中的实施例及实施例中的特征可以相互组合。
实施例一
根据本发明实施例一提供的域名解析方法, 首先获取各顶级域名信息对应的顶级域名 解析服务器的地址, 并将各顶级域名信息与对应的顶级域名解析服务器地址的对应关系保 存在 DNS服务器中, DNS服务器在每次接收到主机发送的域名解析请求时, 可通过查找 该顶级域名信息与对应的顶级域名解析服务器地址的对应关系, 确定出接收的域名解析请 求中包括的待解析的域名信息的顶级域名信息对应的顶级域名解析服务器地址, 从而无需 向根域名解析服务器发送用于解析该顶级域名信息对应的顶级域名解析服务器地址的域 名解析请求。
图 2示出了 DNS服务器保存顶级域名信息与顶级域名解析服务器地址的对应关系的 流程示意图, 如图 2所示, 该过程主要包括如下步驟:
步骤 201、 DNS服务器向根域名解析服务器发送顶级域名解析请求, 该顶级域名解析 请求中包括待解析的顶级域名信息;
步骤 202、根域名解析服务器接收 DNS服务器发送的顶级域名解析请求后, 查询该顶 级域名解析请求中包括的顶级域名信息对应的顶级域名解析服务器地址;
步骤 203、根域名解析服务器将查询到的顶级域名解析服务器地址反馈给 DNS服务器; 步骤 204、 DNS服务器接收根域名解析服务器反馈的顶级域名解析服务器地址, 并保 存该顶级域名信息以及该顶级域名解析服务器地址的对应关系。
至此, 保存顶级域名信息与顶级域名解析服务器地址的对应关系的流程结束。
根据上述过程, 可以预先获取各个顶级域名对应的顶级域名解析服务器地址, 并保存 顶级域名信息与对应的顶级域名解析服务器地址的对应关系, 其中, 顶级域名信息对应的 地址为与该顶级域名信息相应的顶级域名解析服务器的地址, 该顶级域名解析服务器用于 提供在该顶级域名下的非顶级域名对应的非顶级域名解析服务器的地址。 其中, 根据本发 明实施例, 保存的顶级域名信息与顶级域名解析服务器地址的对应关系, 可以根据不同的 顶级域名信息的类型进行区分, 即根据接收的顶级域名解析请求中包括的顶级域名信息的 类型, 分类保存该顶级域名解析请求中包括的顶级域名信息以及顶级域名解析服务器地址 的对应关系, 以进一步提高域名解析时对顶级域名信息对应的顶级域名解析服务器地址的 查找速度, 例如, 顶级域名类型可以通过组织域、 国家域以及特殊域进行划分, 其中, 组 织域类型的顶级域名包括: .edu、 .gov、 .com. .mil、 .int、 .org, .net 等; 国家域类型的顶 级域名可以包括 IS03 166中的国家域, 例如: .cn、 .us、 .jp等; 特殊域类型的顶级域名可 以包括用于地址到名字转换的顶级域名, 如. arpa, 该特殊域类型的顶级域名一般包括访问 频率高的顶级域名。
实际应用中, 顶级域名信息与顶级域名解析服务器地址的对应关系可以根据实际业务 需求以及用户的访问需求不断扩充, 此处不再一一列举。
根据本申请实施例, 保存的顶级域名信息与顶级域名解析服务器地址的对应关系可以 定时更新, 例如, 根据设定周期更新保存的对应关系。 具体地, 为每组顶级域名信息与顶 级域名解析服务器地址的对应关系分别设置定时器, 当为设定顶级域名信息与顶级域名解 析服务器地址的对应关系设置的定时器超时后, DNS服务器向根域名解析服务器发送包括 该设定顶级域名信息的域名解析请求, 用于重新获取该设定顶级域名对应的顶级域名解析 服务器的地址, 并根据根域名解析服务器反馈的地址更新保存的该设定顶级域名信息与地 址的对应关系。
实际应用中, 为了减少系统开销, 对于同一时间建立的顶级域名信息与地址的对应关 系可以设置一个定时器。
基于上述流程建立的顶级域名信息与顶级域名解析服务器地址的对应关系, DNS服务 器接收到包括待解析的域名信息的域名解析请求后, 能够根据保存的对应关系, 确定该待 解析的域名信息中的顶级域名信息对应的顶级域名解析服务器地址, 并才 M居确定出的该顶 级域名解析服务器地址, 获取待解析的域名信息对应的服务器地址。 其中, 根据确定出的 顶级域名解析服务器地址, 获取待解析的域名信息对应的服务器地址的过程, 包括: 向确 定出的顶级域名解析服务器地址对应的顶级域名解析服务器发送该域名解析请求, 并接收 该顶级域名解析服务器根据该域名解析请求中包括的待解析的域名信息, 查询并反馈的与 该待解析的域名信息中的非顶级域名信息对应的非顶级域名解析服务器地址, 进而根据该 非顶级域名解析服务器地址, 获取该待解析的域名信息对应的服务器地址。
实际应用中, 根据确定出的非顶级域名解析服务器地址, 获取待解析的域名信息对应 的服务器地址的过程, 即通过非顶级域名解析服务器进行后续域名解析的过程, 一般情况 下, 非顶级域名信息可以对应一个或多个非顶级域名解析服务器, 若非顶级域名信息对应 一个非顶级域名解析服务器, 则可以直接由所对应的该非顶级域名解析服务器解析得到待 解析域名信息对应的服务器地址; 若非顶级域名信息对应多个非顶级域名解析服务器, 例 如, 非顶级域名信息可以被划分为对应不同优先级的多个子非顶级域名, 各子非顶级域名 分别对应一个非顶级域名解析服务器, 可以通过逐级访问各子非顶级域名分别对应的非顶 级域名解析服务器, 确定出待解析域名信息对应的服务器地址。
图 3示出了本发明实施例一提供的一种域名解析方法的流程示意图, 如图 3所示, 该 过程主要包括如下步骤:
步骤 301、 DNS服务器接收主机发送的域名解析请求, 该域名解析请求中包括待解析 的域名信息;
步骤 302、 根据保存的顶级域名信息与顶级域名解析服务器地址的对应关系, 确定接 收的域名解析请求中包括的域名信息中的顶级域名信息对应的顶级域名解析服务器地址, 并向确定出的该地址对应的顶级域名解析服务器发送域名解析请求, 该域名解析请求中包 括上述待解析的域名信息;
步骤 303、 接收顶级域名解析服务器根据域名解析请求中包括的待解析的域名信息, 查询并反馈的与该待解析的域名信息中的非顶级域名信息对应的非顶级域名解析服务器 地址, 并向该地址对应的非顶级域名解析服务器发送域名解析请求, 该域名解析请求中包 括待解析的域名信息;
步骤 304、 接收非顶级域名解析服务器根据域名解析请求中包括的域名信息, 查询并 反馈的与该待解析的域名信息对应的服务器地址, 并将接收到的服务器地址反馈给主机。
至此, DNS服务器对域名解析请求进行解析的流程结束。
通过上述流程, 即可以确定主机发送的域名解析请求中包括的待解析的域名信息对应 的服务器地址, DNS服务器在通过上述流程确定该服务器地址后, 将该地址反馈给主机。
该实施例一提供的技术方案, 经过对顶级域名信息与顶级域名解析服务器地址的对应 关系的主动保存, 优化了 DNS服务器查询地址的过程, 相对于图 1所示的传统域名解析 流程, DNS服务器无需执行步骤 102〜步骤 103 , 而仅需根据本地保存的顶级域名信息与地 址的对应关系确定主机发送的域名解析请求中包括的待解析的域名信息中的顶级域名信 息对应的顶级域名解析服务器的地址。
根据本实施例, 主要针对顶级域名信息对应的顶级域名解析服务器地址查询过程进行 了主动获取及存储, 因为所有的非顶级域名都在顶级域名的管辖之下, 并且顶级域名的数 量较少, 因此緩存效率高, 对于降低主机获取地址的延迟有重要作用。
在以上实施例的基础上, 本申请进一步提出了针对上述实施例的优化方案, 即为了减 少 DNS服务器保存顶级域名与顶级域名解析服务器地址的对应关系的负担, 可以不保存 访问频率低的顶级域名, 相应于该优化方案, DNS根据接收的域名解析请求, 确定该请求 中包括的域名信息中的顶级域名信息对应的顶级域名解析服务器地址的过程,如图 4所示, 包括如下步骤:
步骤 401、 DNS服务器接收主机发送的域名解析请求, 该域名解析请求中包括待解析 的域名信息;
步骤 402、 根据域名解析请求中包括待解析的域名信息的顶级域名信息, 查找保存的 顶级域名信息与顶级域名解析服务器地址的对应关系;
步骤 403、 判断是否查找到接收的域名解析请求中包括的待解析的域名中的顶级域名 信息与顶级域名解析服务器地址的对应关系, 若是, 则执行步骤 404, 若否, 则执行步骤 405;
步骤 404、 根据查找到的对应关系, 确定该顶级域名信息对应的顶级域名解析服务器 地址, 至此流程结束;
步骤 405、 从根域名解析服务器中获取该顶级域名信息对应的顶级域名解析服务器地 址。
至此流程结束。
根据上述图 4所述的流程, 在减少 DNS服务器保存顶级域名与顶级域名解析服务器 地址的对应关系的负担的基础上, 若主机发送的域名解析请求中包括的域名的顶级域名与 顶级域名解析服务器地址的对应关系存在, 则可以降低该主机获取地址的时延。
实施例二
根据本发明实施例二提供的域名解析方法, DNS服务器可以预先对知名域名 (例如, 访问频率高的域名 )进行域名解析, 并将该知名域名与解析得到的服务器地址的对应关系 保存在 DNS服务器中, DNS服务器在每次接收到主机的域名解析请求时, 可根据该对应 关系,查找该域名解析请求中包括的域名信息与服务器地址的对应关系是否存在,若存在, 则可以直接获取该域名信息对应的服务器地址, 若不存在, 则可以执行如实施例一所述的 方法。
如图 5所示, DNS服务器保存各知名域名信息与服务器地址的对应关系的过程, 主要 包括如下步骤:
步骤 501、 DNS服务器统计主机发送的域名解析请求中包括同一设定域名的次数; 步骤 502、 判断该次数是否达到设定阈值, 若是, 则执行步骤 503 , 若否, 则返回步 骤 501 ;
步骤 503、 解析该设定域名信息对应的服务器地址, 并保存该设定域名信息以及解析 出的服务器地址的对应关系。
其中, 上述步驟 503中, 解析域名对应的地址的过程, 具体参见本发明背景技术中图 1所提供的流程。
基于上述流程建立的知名域名信息与服务器地址的对应关系, 该实施例二提供的域名 解析方法, 如图 6所示, 包括如下步驟:
步骤 601、 DNS服务器接收主机发送的域名解析请求, 该域名解析请求中包括待解析 域名信息;
步骤 602、 根据域名解析请求中包括的待解析域名信息, 查找保存的知名域名信息与 服务器地址的对应关系;
步骤 603、 判断是否查找到接收的域名解析请求中包括待解析的域名信息与服务器地 址的对应关系, 若是, 则执行步骤 604, 若否, 则执行步驟 605;
步骤 604、 根据查找到的对应关系, 确定该待解析的域名信息对应的服务器地址, 至 此流程结束。
步骤 605、 根据实施例一中图 3提供的技术方案, 确定该待解析的域名信息对应的服 务器地址(即执行上述实施例一中图 3对应流程的步骤 302〜步骤 304 ), 至此流程结束。
根据本实施例, 主要针对知名域名的地址查询过程进行了主动获取及存储, 因为知名 域名查询集中了主机的大部分 DNS查询, 对于降低主机获取地址的延迟有重要作用。
实施例三
实际应用中, DNS服务器在收到对设定域名 (例如, www.163.com )对应的网站的域 名解析请求时,还对应有其他域名的域名解析请求,例如, www.youdao.conu www.126.com、 img2.163.com等域名,这些域名之间有高度的相关性,即在主机每次发起的对 www.163.com 的域名解析请求中, 可能还包括对 www.youdao.com、 www.126.com、 img2.163.com等域名 的域名解析请求, 因此, 该实施例三提供的域名解析方法中, 首先确定与设定域名信息存 在关联关系的关联域名信息, 然后分别获取该设定域名信息及其存在关联关系的关联域名 信息对应的服务器地址, 并将该设定域名信息及其关联域名信息分别与服务器地址的对应 关系保存在 DNS服务器中, DNS服务器在接收到主机发送的包括待解析的域名信息(称 为被关联域名)及存在关联关系的关联域名的域名解析请求时, 可根据该对应关系, 确定 出域名解析请求中包括的待解析的域名信息及其关联域名信息分别对应的服务器地址。
其中, 本发明优选实施例中, 设定域名可以为访问频率高的域名, 即 DNS服务器统 计主机发送的域名解析请求中包括同一设定域名的次数, 当该次数达到设定阈值时, 则确 定需要预先建立该设定域名及其关联域名分别与服务器地址的对应关系。 具体地, 针对设 定域名 , 确定与该设定域名存在关联关系的关联域名 , 可以优选地通过如下两种方式: 方式一:
通过分析该设定域名对应的页面内容的源代码数据库, 确定与该域名对应的关联域 名。 一般情况下, 源代码数据库中都会包括该设定域名对应的页面在显示时对应的关联域 名, 例如, 该设定域名对应的页面中的图片或视频可能需要链接到其他域名以使该图片或 视频显示在该设定域名对应的页面下, 则该用于标识图片或视频来源的域名即为该设定域 名对应的关联域名。
方式二:
根据主机的域名解析请求确定与该设定域名对应的关联域名 , 即统计主机发送的包括 该设定域名的域名解析请求中还包括其他域名的次数, 当某域名被包括在该设定域名的域 名解析请求中的次数达到设定阈值时, 则确定该域名为该设定域名的关联域名。
应当理解, 以上两种确定与设定域名存在关联关系的关联域名的方式仅为方便理解本 发明实施例而提出的两种优选实施方式, 实际应用中, 可以根据实际需要确定域名之间的 关联关系, 此处不再——列举。
根据本发明实施例, 保存的被关联域名信息及关联域名信息分别与服务器地址的对应 关系, 可以定时进行更新, 具体地, 为每组被关联域名信息及关联域名信息分别与服务器 地址的对应关系分别设置定时器, 当为被关联域名信息及关联域名信息分别与服务器地址 的对应关系设定的定时器超时后, 重新确定该设定域名对应的关联域名, 并获取该设定域 名及其关联域名对应的地址, 更新保存的该设定域名信息及其关联域名信息分别与地址的 对应关系。 具体地, 对于同一时间建立的设定域名及其关联域名分别与地址的对应关系可 以设置一个定时器。
基于上述流程建立的设定域名及其关联域名分别与服务器地址的对应关系, 该实施例 三提供的域名解析方法, 如图 7所示, 包括如下步骤:
步骤 701、 DNS服务器接收主机发送的域名解析请求, 该域名解析请求中包括待解析 域名信息以及该待解析域名对应的关联域名信息;
步骤 702、 根据接收到的域名解析请求中包括的域名信息和关联域名信息, 查找保存 的被关联域名信息以及关联域名信息分别与服务器地址的对应关系;
步骤 703、 判断是否查找到域名解析请求中包括的待解析的域名信息以及关联域名信 息分别与服务器地址的对应关系, 若是, 则执行步骤 704, 若否, 则执行步骤 705 ; 步骤 704、 根据查找到的对应关系, 确定该域名解析请求中包括的待解析的域名信息 以及关联域名信息分别对应的服务器地址, 至此流程结束。
步骤 705、 采用实施例一提供的方法, 确定未查找到对应关系的每个域名信息对应的 服务器地址, 至此流程结束。
上述步骤 705中, 即针对未查找到地址的每个域名执行:
上述实施例一中图 3对应流程的步骤 302〜步骤 304, 此处不再赞述。
根据本实施例, 主要针对域名信息及其关联域名信息分别对应的服务器地址进行了主 动获取及存储 , 当用户访问设定域名时 , 例如访问 www.163 com时, 与该设定域名存在关 联关系的关联域名信息对应的地址都保存在 DNS服务器中, 一方面减小了网页呈现的时 间, 提高了主机获取地址的效率; 另一方面, 提高了用户针对该设定域名触发的对其他域 名的域名地址解析请求的解析效率。
实施例四
本发明实施例四, 通过将上述实施例一以及实施例三结合以实现对域名解析, 即在
DNS服务器中保存:
各顶级域名与服务器地址的对应关系 (第一对应关系); 以及
被关联域名信息以及关联域名信息分别与服务器地址的对应关系 (第二对应关系)。 在接收到主机的域名解析请求时, 可通过第一对应关系, 确定该域名解析请求中包括 的待解析域名对应的服务器地址(具体确定过程参见实施例一); 并且, 在确定该域名解 析请求中还包括该待解析域名对应的关联域名时, 通过第二对应关系, 确定该域名解析请 求中包括的关联域名对应的服务器地址。
实施例五
相应地, 与上述方法实施对应, 本发明实施例五提供了一种域名解析装置, 如图 8所 示, 该解析装置包括:
接收单元 801、 第一地址确定单元 802、 第二地址确定单元 803以及第一对应关系保 存单元 804;
其巾:
接收单元 801 , 用于接收域名解析请求, 该域名解析请求中包括待解析的域名信息; 第一对应关系保存单元 804, 用于保存顶级域名信息与顶级域名解析服务器地址的对 应关系;
第一地址确定单元 802 , 用于根据第一对应关系保存单元 804保存的顶级域名信息与 顶级域名解析服务器地址的对应关系, 确定接收单元 801接收的域名解析请求中包括的域 名信息中的顶级域名信息对应的顶级域名解析服务器地址;
第二地址确定单元 803 , 用于根据第一地址确定单元 802确定出的顶级域名解析服务 器地址, 获取待解析的域名信息对应的服务器地址。
本发明实施例五提供的一个优选实施例中, 图 8所示的装置包括的第二地址确定单元
803 , 具体用于:
向第一地址确定单元 802确定出的地址对应的顶级域名解析服务器发送域名解析请 求;
接收该顶级域名解析服务器根据域名解析请求中包括的待解析的域名信息, 查询并反 馈的与待解析的域名信息中的非顶级域名信息对应的非顶级域名解析服务器地址;
根据非顶级域名解析服务器地址, 获取待解析的域名信息对应的服务器地址。
本发明实施例五提供的一个优选实施例中, 图 8所示的装置包括的第二地址确定单元 803 , 具体用于: 向确定出的非顶级域名解析服务器地址对应的非顶级域名解析服务器发送域名解析 请求, 并接收非顶级域名解析服务器根据域名解析请求中包括的域名信息, 查询并反馈的 与待解析的域名信息对应的服务器地址。
本发明实施例五提供的一个优选实施例中, 图 8所示的装置包括的第一对应关系保存 单元 804 , 具体用于:
向根域名解析服务器发送包括待解析的顶级域名信息的顶级域名解析请求, 并接收根 域名解析服务器根据顶级域名解析请求中包括的顶级域名信息, 查询并反馈的与顶级域名 信息对应的顶级域名解析服务器地址, 保存顶级域名解析请求中包括的顶级域名信息以及 接收的顶级域名解析服务器地址的对应关系。
本发明实施例五提供的一个优选实施例中, 图 8所示的装置包括的第一对应关系保存 单元 804 , 具体用于:
根据接收的顶级域名解析请求中包括的顶级域名信息的类型, 分类保存顶级域名解析 请求中包括的顶级域名信息以及顶级域名解析服务器地址的对应关系。
本发明实施例五提供的一个优选实施例中, 图 8所示的装置包括的第一对应关系保存 单元 804 , 还用于:
在保存顶级域名解析请求中包括的顶级域名信息以及接收的顶级域名解析服务器地 址的对应关系后, 根据设定周期更新保存的对应关系。
如图 9所示, 本发明实施例五提供的一个优选实施例中, 图 8所示的装置还可以进一 步包括:
第二对应关系保存单元 805、 第一判断单元 806以及第三地址确定单元 807; 其中: 第二对应关系保存单元 805 , 用于保存域名信息与服务器地址的对应关系; 第一判断单元 806 , 用于根据第二对应关系保存单元 805保存的域名信息与服务器地 址的对应关系, 确定是否存在接收的域名解析请求中包括的待解析的域名信息与服务器地 址的对应关系;
第一地址确定单元 802 , 具体用于: 在第一判断单元 806的判断结果为否时, 才艮据保 存的顶级域名信息与顶级域名解析服务器地址的对应关系, 确定待解析的域名信息中的顶 级域名信息对应的顶级域名解析服务器地址;
第三地址确定单元 807 , 用于在第一判断单元 806的判断结果为是时, 根据存在的对 应关系, 确定与待解析的域名信息对应的服务器地址。
本发明实施例五提供的一个优选实施例中, 图 9所示的装置包括的第二对应关系保存 单元 805 , 具体用于:
确定接收的域名解析请求中包括设定域名的次数, 当次数达到设定阈值时, 获取设定 域名对应的服务器地址, 并保存该设定域名信息与获取的服务器地址的对应关系。 本发明实施例五提供的又一优选实施例中, 图 8所示的装置包括的接收单元 801 , 具 体用于:
接收域名解析请求, 该域名解析请求中包括待解析的域名信息以及与该待解析的域名 信息存在关联关系的关联域名信息;
相应地, 如图 10所示, 图 8所示的装置还可以进一步包括:
第三对应关系保存单元 808、 第二判断单元 809以及第四地址确定单元 810; 其中: 第三对应关系保存单元 808 , 用于保存域名信息以及存在关联关系的关联域名信息分 别与服务器地址的对应关系;
第二判断单元 809 , 用于根据第三对应关系保存单元 808保存的域名信息以及存在关 联关系的关联域名信息分别与服务器地址的对应关系, 确定是否存在接收的域名解析请求 中包括的待解析的域名信息以及存在关联关系的关联域名信息分别与服务器地址的对应 关系;
第四地址确定单元 810 , 用于在第二判断单元 809的确定结果为是时, 根据存在的对 应关系, 确定域名解析请求中包括的待解析的域名信息以及存在关联关系的关联域名信息 分别对应的服务器地址;
第一地址确定单元 802 , 具体用于在第二判断单元 809的确定结果为是时, 确定该待 解析的域名信息中的顶级域名信息对应的顶级域名解析服务器地址, 以及分别确定关联域 名信息中的顶级域名信息对应的顶级域名解析服务器地址。
本发明实施例五提供的一个优选实施例中, 图 10所示装置包括的第三对应关系保存 单元 808 , 具体用于:
确定与待保存的域名信息存在关联关系的关联域名信息;
获取待保存的域名信息以及存在关联关系的关联域名信息分别对应的服务器地址; 并 保存待保存的域名信息以及存在关联关系的关联域名信息分别与获取的服务器地址 的对应关系。
应当理解, 以上域名解析装置包括的单元仅为根据该装置实现的功能进行的逻辑划 分, 实际应用中, 可以进行上述单元的叠加或拆分。 并且该实施例提供的域名解析装置所 实现的功能与上述实施例提供的域名解析方法流程——对应, 对于该装置所实现的更为详 细的处理流程, 在上述方法实施例中已做详细描述, 此处不再详细描述。
通过本发明实施例提供的上述至少一个技术方案, 在接收包括待解析的域名信息的域 名解析请求后, 可根据保存的顶级域名信息与顶级域名解析服务器地址的对应关系, 直接 确定出该待解析域名的顶级域名信息对应的顶级域名解析服务器地址, 与现有技术相比, 针对来自各主机的各种域名解析请求, 节省了与根域名解析服务器交互以确定顶级域名信 息对应的顶级域名解析服务器地址的时间, 因此, 采用该技术方案能够整体提高对所服务 的主机的域名解析请求的处理效率。
本领域内的技术人员应明白, 本发明的实施例可提供为方法、 系统、 或计算机程序产 品。 因此, 本发明可采用完全硬件实施例、 完全软件实施例、 或结合软件和硬件方面的实 施例的形式。 而且, 本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机 可用存储介质(包括但不限于磁盘存储器、 CD-ROM、 光学存储器等)上实施的计算机程 序产品的形式。
本发明是参照根据本发明实施例的方法、 设备(系统)、 和计算机程序产品的流程图 和 /或方框图来描述的。 应理解可由计算机程序指令实现流程图和 /或方框图中的每一流 程和 /或方框、 以及流程图和 /或方框图中的流程和 /或方框的结合。 可提供这些计算机 程序指令到通用计算机、 专用计算机、 嵌入式处理机或其他可编程数据处理设备的处理器 以产生一个机器, 使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用 于实现在流程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功能的 装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方 式工作的计算机可读存储器中, 使得存储在该计算机可读存储器中的指令产生包括指令装 置的制造品, 该指令装置实现在流程图一个流程或多个流程和 /或方框图一个方框或多个 方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上, 使得在计算机 或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理, 从而在计算机或其他 可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和 /或方框图一个 方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例, 但本领域内的技术人员一旦得知了基本创造性概 念, 则可对这些实施例作出另外的变更和修改。 所以, 所附权利要求意欲解释为包括优选 实施例以及落入本发明范围的所有变更和修改。
显然, 本领域的技术人员可以对本发明实施例进行各种改动和变型而不脱离本发明实 施例的精神和范围。 这样, 倘若本发明实施例的这些修改和变型属于本发明权利要求及其 等同技术的范围之内, 则本发明也意图包含这些改动和变型在内。

Claims

权 利 要 求
1、 一种域名解析方法, 其特征在于, 包括:
接收域名解析请求, 所述域名解析请求中包括待解析的域名信息;
根据保存的顶级域名信息与顶级域名解析服务器地址的对应关系, 确定所述待解析的 域名信息中的顶级域名信息对应的顶级域名解析服务器地址;
根据确定出的所述顶级域名解析服务器地址, 获取所述待解析的域名信息对应的服务 器地址。
2、 如权利要求 1 所述的方法, 其特征在于, 根据确定出的所述顶级域名解析服务器 地址, 获取所述待解析的域名信息对应的服务器地址, 包括:
向确定出的所述顶级域名解析服务器地址对应的顶级域名解析服务器发送所述域名 解析请求;
接收所述顶级域名解析服务器根据所述域名解析请求中包括的待解析的域名信息, 查 询并反馈的与所述待解析的域名信息中的非顶级域名信息对应的非顶级域名解析服务器 地址;
根据所述非顶级域名解析服务器地址, 获取所述待解析的域名信息对应的服务器地 址。
3、 如权利要求 2所述的方法, 其特征在于, 根据所述非顶级域名解析服务器地址, 获取所述待解析的域名信息对应的服务器地址, 包括:
向所述非顶级域名解析服务器地址对应的非顶级域名解析服务器发送所述域名解析 请求;
接收所述非顶级域名解析服务器根据所述域名解析请求中包括的域名信息, 查询并反 馈的与所述待解析的域名信息对应的服务器地址。
4、 如权利要求 1 所述的方法, 其特征在于, 保存顶级域名信息与顶级域名解析服务 器地址的对应关系的方式, 包括:
向根域名解析服务器发送包括待解析的顶级域名信息的顶级域名解析请求; 接收所述根域名解析服务器根据所述顶级域名解析请求中包括的顶级域名信息, 查询 并反馈的与所述顶级域名信息对应的顶级域名解析服务器地址;
保存所述顶级域名解析请求中包括的顶级域名信息以及接收的所述顶级域名解析服 务器地址的对应关系。
5、 如权利要求 4所述的方法, 其特征在于, 保存所述顶级域名解析请求中包括的顶 级域名信息以及接收的所述顶级域名解析服务器地址的对应关系, 包括:
根据接收的所述顶级域名解析请求中包括的顶级域名信息的类型, 分类保存所述顶级 域名解析请求中包括的顶级域名信息以及所述顶级域名解析服务器地址的对应关系。
6、 如权利要求 4所述的方法, 其特征在于, 保存所述顶级域名解析请求中包括的顶 级域名信息以及接收的所述顶级域名解析服务器地址的对应关系后, 还包括:
根据设定周期更新保存的所述对应关系。
7、 如权利要求 1 所述的方法, 其特征在于, 在确定所述待解析的域名信息中的顶级 域名信息对应的顶级域名解析服务器地址之前, 还包括:
根据保存的域名信息与服务器地址的对应关系, 确定是否存在接收的所述域名解析请 求中包括的待解析的域名信息与服务器地址的对应关系;
在确定结果为否时, 执行所述确定所述待解析的域名信息中的顶级域名信息对应的顶 级域名解析服务器地址的步骤;
在确定结果为是时, 根据存在的所述对应关系, 确定与所述待解析的域名信息对应的 服务器地址。
8、 如权利要求 Ί所述的方法, 其特征在于, 保存域名信息与服务器地址的对应关系 的方式, 包括:
确定接收的域名解析请求中包括设定域名的次数;
当所述次数达到设定阈值时, 获取所述设定域名对应的服务器地址, 并保存所述设定 域名信息与获取的所述服务器地址的对应关系。
9、 如权利要求 1 所述的方法, 其特征在于, 所述域名解析请求中还包括与所述待解 析的域名信息存在关联关系的关联域名信息;
在确定所述待解析的域名信息中的顶级域名信息对应的顶级域名解析服务器地址之 前, 还包括:
根据保存的域名信息以及存在关联关系的关联域名信息分别与服务器地址的对应关 系, 确定是否存在接收的所述域名解析请求中包括的待解析的域名信息以及存在关联关系 的关联域名信息分别与服务器地址的对应关系;
在确定结果为是时, 根据存在的所述对应关系, 确定所述域名解析请求中包括的待解 析的域名信息以及存在关联关系的关联域名信息分别对应的服务器地址;
在确定结果为否时, 执行所述确定所述待解析的域名信息中的顶级域名信息对应的顶 级域名解析服务器地址的步骤; 并针对每个与所述待解析的域名信息存在关联关系的关联 域名信息, 执行:
根据保存的顶级域名信息与顶级域名解析服务器地址的对应关系, 确定所述关联域名 信息中的顶级域名信息对应的顶级域名解析服务器地址;
根据确定出的所述顶级域名解析服务器地址, 获取所述关联域名信息对应的服务器地 址。
10、 如权利要求 9所述的方法, 其特征在于, 保存域名信息以及存在关联关系的关联 域名信息分别与服务器地址的对应关系的方式, 包括:
确定与待保存的域名信息存在关联关系的关联域名信息;
获取所述待保存的域名信息以及存在关联关系的关联域名信息分别对应的服务器地 址; 并
保存所述待保存的域名信息以及存在关联关系的关联域名信息分别与获取的服务器 地址的对应关系。
11、 一种域名解析装置, 其特征在于, 包括:
接收单元, 用于接收域名解析请求, 所述域名解析请求中包括待解析的域名信息; 第一对应关系保存单元, 用于保存顶级域名信息与顶级域名解析服务器地址的对应关 系;
第一地址确定单元, 用于才 M居所述第一对应关系保存单元保存的顶级域名信息与顶级 域名解析服务器地址的对应关系, 确定所述接收单元接收的域名解析请求中包括的待解析 的域名信息中的顶级域名信息对应的顶级域名解析服务器地址;
第二地址确定单元, 用于根据所述第一地址确定单元确定出的所述顶级域名解析服务 器地址, 获取所述待解析的域名信息对应的服务器地址。
12、 如权利要求 11所述的装置, 其特征在于, 所述第二地址确定单元, 具体用于: 向所述第一地址确定单元确定出的地址对应的顶级域名解析服务器发送所述域名解 析请求;
接收所述顶级域名解析服务器根据所述域名解析请求中包括的待解析的域名信息, 查 询并反馈的与所述待解析的域名信息中的非顶级域名信息对应的非顶级域名解析服务器 地址;
根据所述非顶级域名解析服务器地址, 获取所述待解析的域名信息对应的服务器地 址。
13、 如权利要求 12所述的装置, 其特征在于, 所述第二地址确定单元, 具体用于: 向确定出的非顶级域名解析服务器地址对应的非顶级域名解析服务器发送所述域名 解析请求, 并接收所述非顶级域名解析服务器根据所述域名解析请求中包括的域名信息, 查询并反馈的与所述待解析的域名信息对应的服务器地址。
14、如权利要求 11所述的装置,其特征在于,所述第一对应关系保存单元,具体用于: 向根域名解析服务器发送包括待解析的顶级域名信息的顶级域名解析请求, 并接收所 述根域名解析服务器根据所述顶级域名解析请求中包括的顶级域名信息, 查询并反馈的与 所述顶级域名信息对应的顶级域名解析服务器地址, 保存所述顶级域名解析请求中包括的 顶级域名信息以及接收的所述顶级域名解析服务器地址的对应关系。
15、 如权利要求 14所述的装置, 其特征在于, 所述第一对应关系保存单元, 具体用 于:
根据接收的所述顶级域名解析请求中包括的顶级域名信息的类型, 分类保存所述顶级 域名解析请求中包括的顶级域名信息以及所述顶级域名解析服务器地址的对应关系。
16、 如权利要求 14所述的装置, 其特征在于, 所述第一对应关系保存单元, 还用于: 在保存所述顶级域名解析请求中包括的顶级域名信息以及接收的所述顶级域名解析 服务器地址的对应关系后, 根据设定周期更新保存的所述对应关系。
17、 如权利要求 11所述的装置, 其特征在于, 还包括: 第二对应关系保存单元、 第一 判断单元以及第三地址确定单元;
所述第二对应关系保存单元, 用于保存域名信息与服务器地址的对应关系; 所述第一判断单元, 用于根据所述第二对应关系保存单元保存的域名信息与服务器地 址的对应关系, 确定是否存在接收的所述域名解析请求中包括的待解析的域名信息与服务 器地址的对应关系;
所述第一地址确定单元, 具体用于在所述第一判断单元的判断结果为否时, 才 据保存 的顶级域名信息与顶级域名解析服务器地址的对应关系, 确定所述待解析的域名信息中的 顶级域名信息对应的顶级域名解析服务器地址;
所述第三地址确定单元, 用于在所述第一判断单元的判断结果为是时, 根据存在的所 述对应关系, 确定与所述待解析的域名信息对应的服务器地址。
18、 如权利要求 17所述的装置, 其特征在于, 所述第二对应关系保存单元, 具体用 于:
确定接收的域名解析请求中包括设定域名的次数;
当所述次数达到设定阈值时, 获取所述设定域名对应的服务器地址, 并保存所述设定 域名信息与获取的所述服务器地址的对应关系。
19、 如权利要求 11所述的装置, 其特征在于, 所述接收单元, 具体用于: 接收域名解析请求, 所述域名解析请求中包括待解析的域名信息以及与所述待解析的 域名信息存在关联关系的关联域名信息;
所述装置还包括: 第三对应关系保存单元、 第二判断单元以及第四地址确定单元; 所述第三对应关系保存单元, 用于保存域名信息以及存在关联关系的关联域名信息分 别与服务器地址的对应关系;
所述第二判断单元, 用于才艮据所述第三对应关系保存单元保存的域名信息以及存在关 联关系的关联域名信息分别与服务器地址的对应关系, 确定是否存在接收的所述域名解析 请求中包括的待解析的域名信息以及存在关联关系的关联域名信息分别与服务器地址的 对应关系; 所述第四地址确定单元, 用于在所述第二判断单元的确定结果为是时, 根据存在的所 述对应关系, 确定所述域名解析请求中包括的待解析的域名信息以及存在关联关系的关联 域名信息分别对应的服务器地址;
所述第一地址确定单元, 具体用于在所述第二判断单元的确定结果为是时, 确定所述 待解析的域名信息中的顶级域名信息对应的顶级域名解析服务器地址, 以及分别确定所述 关联域名信息中的顶级域名信息对应的顶级域名解析服务器地址。
20、 如权利要求 19所述的装置, 其特征在于, 所述第三对应关系保存单元, 具体用 于:
确定与待保存的域名信息存在关联关系的关联域名信息;
获取所述待保存的域名信息以及存在关联关系的关联域名信息分别对应的服务器地 址; 并
保存所述待保存的域名信息以及存在关联关系的关联域名信息分别与获取的服务器 地址的对应关系。
PCT/CN2011/077344 2010-07-22 2011-07-20 一种域名解析方法及装置 WO2012010084A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010236357.1 2010-07-22
CN201010236357.1A CN102340549B (zh) 2010-07-22 2010-07-22 一种域名解析方法及装置

Publications (1)

Publication Number Publication Date
WO2012010084A1 true WO2012010084A1 (zh) 2012-01-26

Family

ID=45496518

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/077344 WO2012010084A1 (zh) 2010-07-22 2011-07-20 一种域名解析方法及装置

Country Status (2)

Country Link
CN (1) CN102340549B (zh)
WO (1) WO2012010084A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105791461A (zh) * 2016-03-09 2016-07-20 浪潮通信信息系统有限公司 一种基于错误域名流量的经营方法
WO2018081963A1 (zh) * 2016-11-02 2018-05-11 达闼科技(北京)有限公司 一种dns解析方法、装置及网络系统
CN111079019A (zh) * 2019-12-19 2020-04-28 国网冀北电力有限公司信息通信分公司 一种基于物联网的信息查询方法及装置
CN112738296A (zh) * 2021-03-02 2021-04-30 中国建设银行股份有限公司 一种域名解析方法和域名解析系统
CN112954049A (zh) * 2021-02-08 2021-06-11 上海石锤网络科技有限公司 一种域名解析的方法及装置

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105224250B (zh) * 2015-09-28 2021-06-01 域创科技(浙江)有限公司 高性能域名解析处理方法和装置
CN105872125B (zh) * 2016-03-30 2019-01-22 中国联合网络通信集团有限公司 一种域名解析的方法及装置
CN106385469B (zh) * 2016-08-25 2019-08-13 厦门易名科技股份有限公司 基于并发处理的whois查询方法及装置
CN106657321A (zh) * 2016-12-16 2017-05-10 上海斐讯数据通信技术有限公司 无线ap中本地dns缓存方法、网站访问方法及无线ap
CN108449442A (zh) * 2018-03-10 2018-08-24 北京酷我科技有限公司 一种iOS网络优化策略
CN110784553B (zh) * 2019-11-05 2021-12-21 南京亚信智网科技有限公司 报文封装方法、设备及域名解析系统
CN115118700B (zh) * 2022-06-27 2024-03-15 北京天融信网络安全技术有限公司 一种通信方法及通信系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1540543A (zh) * 2003-10-31 2004-10-27 浙江大学 一种内容服务器系统及其处理过程
CN1852332A (zh) * 2006-04-10 2006-10-25 王立俊 一种服务器端域名解析错误控制方法及系统
CN101087253A (zh) * 2007-04-04 2007-12-12 华为技术有限公司 保存域名系统记录的方法、装置、域名解析方法及装置
CN101431539A (zh) * 2008-12-11 2009-05-13 华为技术有限公司 一种域名解析方法、系统及装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101170585B (zh) * 2007-11-13 2011-08-24 中兴通讯股份有限公司 一种域名查询方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1540543A (zh) * 2003-10-31 2004-10-27 浙江大学 一种内容服务器系统及其处理过程
CN1852332A (zh) * 2006-04-10 2006-10-25 王立俊 一种服务器端域名解析错误控制方法及系统
CN101087253A (zh) * 2007-04-04 2007-12-12 华为技术有限公司 保存域名系统记录的方法、装置、域名解析方法及装置
CN101431539A (zh) * 2008-12-11 2009-05-13 华为技术有限公司 一种域名解析方法、系统及装置

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105791461A (zh) * 2016-03-09 2016-07-20 浪潮通信信息系统有限公司 一种基于错误域名流量的经营方法
WO2018081963A1 (zh) * 2016-11-02 2018-05-11 达闼科技(北京)有限公司 一种dns解析方法、装置及网络系统
CN111079019A (zh) * 2019-12-19 2020-04-28 国网冀北电力有限公司信息通信分公司 一种基于物联网的信息查询方法及装置
CN112954049A (zh) * 2021-02-08 2021-06-11 上海石锤网络科技有限公司 一种域名解析的方法及装置
CN112738296A (zh) * 2021-03-02 2021-04-30 中国建设银行股份有限公司 一种域名解析方法和域名解析系统

Also Published As

Publication number Publication date
CN102340549A (zh) 2012-02-01
CN102340549B (zh) 2014-03-26

Similar Documents

Publication Publication Date Title
WO2012010084A1 (zh) 一种域名解析方法及装置
US11909639B2 (en) Request routing based on class
US9866523B2 (en) Method and system for increasing speed of domain name system resolution within a computing device
US8375125B1 (en) Mechanism for handling persistent requests from stateless clients
US8606996B2 (en) Cache optimization
US20050240574A1 (en) Pre-fetching resources based on a resource lookup query
CN112217916B (zh) 一种新型的工业互联网标识解析递归服务器的缓存方法和系统
CN102984286B (zh) 一种dns服务器的缓存更新方法、装置及系统
US20130044754A1 (en) Method, apparatus and system for acquiring media access control address
JP5974079B2 (ja) 変更ホストネームを使用するグローバル・トラフィック管理
AU2012242421B2 (en) Data acquisition method, device and system
US9954815B2 (en) Domain name collaboration service using domain name dependency server
CN102882791A (zh) 一种dns业务处理的方法及装置
WO2011140842A1 (zh) 多媒体文件发布方法和装置
WO2012022142A1 (zh) 一种服务器迭代查询方法、系统以及一种服务器
TW201824031A (zh) 搜索緩存更新方法及裝置
WO2016177276A1 (zh) 一种域名解析的同步方法和设备
WO2017166524A1 (zh) 域名解析方法及装置
CN116996578B (zh) 基于内容分发网络的资源处理方法和装置
WO2013082791A1 (zh) Dns客户端地址、rr ttl更新的方法、装置及系统
CN112532766A (zh) Dns应答结果的缓存方法、dns服务器及计算机可读存储介质
WO2019019382A1 (zh) 缓存处理方法、装置、计算机设备和存储介质
KR20150046675A (ko) Ip 네트워크를 통해 웹사이트에 접속하는 단말기 및 단말기의 웹사이트 접속 시간 단축 방법
CN116866429A (zh) 一种数据访问方法及相关装置
CN114513554A (zh) 网络访问方法、装置、设备、计算机可读存储介质及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11809272

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11809272

Country of ref document: EP

Kind code of ref document: A1