WO2018148984A1 - 域名解析系统、域名解析服务器和域名解析方法 - Google Patents

域名解析系统、域名解析服务器和域名解析方法 Download PDF

Info

Publication number
WO2018148984A1
WO2018148984A1 PCT/CN2017/075002 CN2017075002W WO2018148984A1 WO 2018148984 A1 WO2018148984 A1 WO 2018148984A1 CN 2017075002 W CN2017075002 W CN 2017075002W WO 2018148984 A1 WO2018148984 A1 WO 2018148984A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain name
client
server
requested
parsing
Prior art date
Application number
PCT/CN2017/075002
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 网宿科技股份有限公司
Priority to US15/748,757 priority Critical patent/US20190036870A1/en
Priority to EP17875072.5A priority patent/EP3389244B1/en
Publication of WO2018148984A1 publication Critical patent/WO2018148984A1/zh

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
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/30—Types of network names

Definitions

  • the present invention relates to the field of computer technologies, and in particular, to a domain name resolution system, a domain name resolution server, and a domain name resolution method.
  • the domain name requested by the client is aliased (CNAME) to the CDN domain name.
  • the domain name requested by each client corresponds to a CDN domain name.
  • the CDN domain name is referred to in the following text. For the entry domain name.
  • the same server group is used by many clients at the same time. If each portal domain name directly resolves the IP of a server group, once the server group cannot provide services, there will be a large number of domain names to be switched, that is, The record of the IP address of the server group corresponding to the entry domain name, that is, the A record of the entry domain name, is generated for a long time, and the time for deploying these A records is also long. Therefore, in the prior art, the first-level domain name CNAME of the same server group is generally used to the same second-level domain name, so that if a server group cannot provide services, the second-level domain name corresponding to the server group can be quickly resolved to Another IP address.
  • the domain name resolution query requires at least two layers of alias resolution, that is, the domain name CNAME requested by the client is to the portal domain name, and then the entry domain name CNAME to the second-level domain name, and the two-layer alias resolution increases the parsing time, and Two-tier alias resolution leads to an increase in the resolution failure rate.
  • the domain name resolution query requires at least two layers of alias resolution, that is, the domain name CNAME requested by the client is to the portal domain name, and then the entry domain name CNAME to the second-level domain name, and the two-layer alias resolution increases the parsing time, and Two-tier alias resolution leads to an increase in the resolution failure rate.
  • the domain name resolution query requires at least two layers of alias resolution, that is, the domain name CNAME requested by the client is to the portal domain name, and then the entry domain name CNAME to the second-level domain name
  • the two-layer alias resolution increases the parsing time
  • the embodiment of the present invention provides a domain name resolution system, a server, and a domain name resolution method, so as to solve the problem that the analysis time of the two-layer alias analysis in the prior art is too long, the analysis failure rate is high, and Trace back the problem of the client being attacked.
  • An embodiment of the present invention provides a domain name resolution method, including the following steps:
  • the ingress domain name is parsed, and the parsing result is returned to the client as the parsing result of the domain name requested by the client.
  • the ingress domain name is composed of a domain name requested by the client as a prefix and a suffix of the pan-domain name as a suffix.
  • step of parsing the ingress domain name and returning the parsing result to the client as the parsing result of the domain name requested by the client includes:
  • the A-record of the entry domain name is found, the A-record with the exact match is returned to the client as the parsing result; otherwise, the A-record of the generic domain name corresponding to the entry domain name is returned to the client as the parsing result.
  • the exact matching A record of the ingress domain name includes the network protocol address of the source station server corresponding to the domain name requested by the client, and when the domain name requested by the client needs to be returned to the source, the network protocol address of the source station is returned to the client as the parsing result. end.
  • the A matching record of the entry domain name includes the network protocol address of the custom server corresponding to the domain name requested by the client.
  • the network protocol address of the customized server is returned to the client as the parsing result. end.
  • the same server group includes multiple server clusters, each server cluster having a unique network protocol address, and the portal domain name using the same pan-domain name is parsed out of the network protocol address corresponding to the same server group.
  • domain name resolution method further includes:
  • the embodiment of the present invention provides a domain name resolution server, including:
  • a setting module for setting the same pan-domain name for the portal domain name using the same server group
  • the transceiver module is connected to the setting module, and is configured to receive an analysis request of the portal domain name, where the domain name requested by the client is resolved to the portal domain name by using an alias;
  • the parsing module is connected to the transceiver module for parsing the domain name of the portal and parsing the result
  • the parsing result of the domain name requested by the client is returned to the client.
  • parsing module includes:
  • the search module is configured to find whether the entry domain name has an exact matching A record, and if yes, return the exact matching A record to the client as the parsing result;
  • the generic domain name parsing module is connected to the locating module, and is configured to return the A record of the generic domain name corresponding to the portal domain name to the client as the parsing result when the locating module does not find the exact matching A record corresponding to the portal domain name.
  • the domain name resolution server further includes:
  • the scheduling module is separately connected to the setting module and the parsing module, and is configured to re-parse the generic domain name of the corresponding server group to another network protocol address when a server cluster in the server group fails.
  • the setting module is further configured to set an exact matching A record of the entry domain name, and the exact matching A record of the entry domain name includes the network protocol address corresponding to the source station server requested by the client, and the domain name requested by the client needs to be returned.
  • the search module returns the network protocol address of the source station to the client as a result of the parsing.
  • the setting module is further configured to set an exact matching A record of the entry domain name, and the A matching record of the entry domain name includes the network protocol address of the customized server corresponding to the domain name requested by the client, and the customized server is required when the domain name requested by the client is used.
  • the lookup module returns the network protocol address of the custom server to the client as a result of the parsing.
  • the embodiment of the invention further provides a domain name resolution system, including:
  • the client DNS server resolves the domain name requested by the client to the entry domain name of the content distribution network through an alias
  • the domain name resolution server includes the same general domain name for the ingress domain name of the same server group, and receives the parsing request of the ingress domain name, and parses the ingress domain name, and returns the parsing result to the client as the parsing result of the domain name requested by the client.
  • the domain name resolution server parses the ingress domain name, and returns the parsing result as the parsing result of the domain name requested by the client to the client, which specifically includes: searching whether the ingress domain name has an exact matching A record, and if yes, matching exactly The A record is returned to the public network DNS server as the result of the analysis; otherwise, the A record of the generic domain name corresponding to the entry domain name is returned to the client as the parsing result.
  • the domain name alias requested by the client is set to the portal domain name in the client DNS server.
  • the ingress domain name is composed of the domain name requested by the client as a prefix and the suffix of the pan-domain name as a suffix.
  • the technical solution provided by the embodiment of the present invention has the beneficial effects that the present invention provides a layered alias recording method based on a pan-domain name, which reduces the resolution of an alias record of a system domain name compared with the existing method, and can shorten the system.
  • the domain name resolution time reduces the failure rate of the system domain name resolution.
  • the server scheduling time based on the system domain name is shortened and the configuration amount is reduced.
  • the present invention does not need to modify the pan-domain name or the second-level domain name, and only needs to add a minimum amount of configuration to support a special back-source configuration or other special configuration.
  • the present invention adopts a layer of alias method, when a domain name is attacked, it is easy to accurately discover the attacked specific customers through a layer of aliases, and realize attack tracing.
  • FIG. 1 is a flowchart of an implementation manner of a domain name resolution method provided by the present invention
  • FIG. 2 is a flowchart of another embodiment of a domain name resolution method provided by the present invention.
  • FIG. 3 is a flowchart of another embodiment of a domain name resolution method provided by the present invention.
  • FIG. 4 is a structural diagram of an embodiment of a domain name resolution server provided by the present invention.
  • FIG. 5 is a structural diagram of another embodiment of a domain name resolution server provided by the present invention.
  • FIG. 6 is a structural diagram of another embodiment of a domain name resolution server provided by the present invention.
  • FIG. 7 is a structural diagram of an embodiment of a domain name resolution system provided by the present invention.
  • the present invention provides an implementation manner of a domain name resolution method, as shown in FIG. 1 , including the following steps:
  • Step S101 setting the same pan-domain name for using the portal domain name of the same server group.
  • the configuration of the ingress domain name to the pan domain name is set on the DNS server of the content distribution network, wherein the portal domain name is composed of the domain name requested by the client as a prefix and the suffix of the pan domain name as a suffix.
  • the domain name requested by the client is www.163.com
  • the domain name is *.bbb.aaa.com
  • the domain name of the portal is www.163.com.bbb.aaa.com.
  • the same server group includes multiple server clusters, each of which has a unique network protocol address (IP), and the ingress domain name of the same pan-domain name is resolved to the network protocol address corresponding to the same server group.
  • IP network protocol address
  • the portal domain uses a server group with a network protocol address of 192.168.100.100 in the content distribution network.
  • These portal domains are all set to the same generic domain name *.bbb.aaa.com. Therefore, the setting rules between the domain name, the ingress domain name, and the pan-domain name requested by the client are related to each other.
  • Step S102 The domain name requested by the client is resolved to the entry domain name of the content distribution network by using an alias.
  • the client DNS server receives the domain name resolution request from www.163.com sent by the client, and resolves the access domain name of the content distribution network by www.163.com to the content distribution network www.163.com.bbb.aaa.com .
  • the domain name sent by other clients to request resolution is the same, and the present invention will not be described again. This type of portal domain name is only obtained once for the domain name alias resolved by the client request.
  • step S103 the ingress domain name is parsed, and the parsing result is returned to the client as the parsing result of the domain name requested by the client.
  • the client DNS server resolves the domain name requested by the client to the portal domain name of the content distribution network
  • the client requests the DNS server of the content distribution network to parse the portal domain name
  • the DNS server of the content distribution network receives the resolution.
  • the request and the domain name www.163.com.bbb.aaa.com are parsed, and the parsing result is returned to the client as the parsing result of the domain name requested by the client.
  • the configuration is set in the DNS server of the content distribution network, that is, the same pan-domain name is set by using the portal domain name of the same server group, so the specific process of parsing the portal domain name may be performed by searching for the exact domain name of the portal domain.
  • the A record and the A-record of the generic domain name corresponding to the entry domain name are parsed.
  • the specific resolution process refer to the corresponding implementation manner in FIG. 2 .
  • This kind of alias recording method based on the pan-domain name can shorten the domain name system parsing time and reduce the domain name system parsing failure rate.
  • the attacked domain name may only be accurate.
  • a domain name such as an entry domain name or a domain name that the client requests to resolve, is easy to accurately discover the specific client being attacked through a layer of aliases, such as when the portal domain name www.163.com.bbb.aaa.com is attacked, due to www .163.com.bbb.aaa.com is obtained through the alias analysis of www.163.com, that is, it can be known that the specific attacked domain name is www.163.com, and the attack traceability is realized.
  • step S103 specifically includes the following steps:
  • step S1031 it is found whether the entry domain name has an exact matching A record.
  • the accurately matched A record of the entry domain name includes the network protocol address of the source station server corresponding to the domain name requested by the client and the network protocol address of the custom server corresponding to the domain name requested by the client. If the entry domain name has an exact matching A record, then step S1032 is performed, otherwise step S1033 is performed.
  • step S1032 the accurately matched A record is returned to the client as an analysis result.
  • the network protocol address of the source station is returned to the client as the parsing result. For example, if the domain name requested by the client www.163.com needs to be returned in the Beijing Telecom area, then only the A record of the Beijing Telecom area should be set on the DNS server of the content distribution network. If the content distribution network receives a request from Beijing Telecom, it will preferentially match the configured A record to the source.
  • the network protocol address of the customized server is returned to the client as a result of the parsing. If the domain name requested by the client www.163.com needs to use a special server in Xinjiang Telecom, then only need to configure the server separately in the Xinjiang Telecom area for the www.163.com on the DNS server of the content distribution network, if the content distribution network Upon receiving a request from Xinjiang Telecom, it will be matched to a separately configured server.
  • step S1033 the A record of the pan-domain name corresponding to the entry domain name is returned to the client as an analysis result. If the inbound domain name does not have the exact matching A record, the generic domain name corresponding to the portal domain name is searched, and the A domain record of the generic domain name is returned to the client as the parsing result of parsing the ingress domain name.
  • the invention does not need to modify the pan-domain name or the second-level domain name, and only needs to add a minimum amount of configuration to support a special back-source configuration or other special configuration, the added configuration is small, and easy to implement, and can meet the special requirements of domain name resolution. .
  • the domain name resolution method further includes: Step S304: When a certain server cluster in the server group fails, re-parsing the generic domain name of the corresponding server group to another network protocol address.
  • www.163.com.bbb.aaa.com, news.163.com.bbb.aaa.com, and music.163.com.bbb.aaa.com all use a server group with a network protocol address of 192.168.100.100.
  • server group (192.168.100.100) used by the three entry domains fails, only one domain name system configuration needs to be generated in the DNS server of the content distribution network, and the three domain names of the three entry domains in the content distribution network are *.
  • Bbb.aaa.com reconfigured from the original server group's network protocol address 192.168.100.100 to a new server group network protocol address such as 192.168.100.110, which is the generic domain name *.bbb corresponding to the three entry domain names.
  • Aaa.com re-parses to 192.168.100.110, which means that all three portal domains can be transferred to the new server cluster all at once in the content distribution network, without changing www.163.com.bbb.aaa.com, news
  • the configuration of .163.com.bbb.aaa.com and music.163.com.bbb.aaa.com shortens server scheduling time and reduces configuration.
  • the present invention further provides an implementation of the domain name resolution server 400.
  • the present invention includes a setting module 401, a transceiver module 402, and a parsing module 403.
  • the setting module 401 is configured to set the same universal domain name for the portal domain name of the same server group;
  • the transceiver module 402 is connected to the universal domain name setting module 401, and is configured to receive the resolution request of the portal domain name, where the domain name requested by the client is resolved to the content by using the alias.
  • the ingress domain name of the distribution network is connected to the transceiver module 402, and is configured to parse the ingress domain name, and return the parsing result to the client as the parsing result of the domain name requested by the client.
  • the working process of the entire domain name resolution server 400 is as follows: For example, in the content distribution network, three entry domain names use a server group with a network protocol address of 1.1.1.1, and the three entry domain names are respectively www.163.com.bbb.aaa. Com, news.163.com.bbb.aaa.com and music.163.com.bbb.aaa.com.
  • the domain name setting module 401 sets the same pan-domain name *.bbb.aaa.com for the three entry domain names.
  • the client DNS server receives the resolution request from the domain name www.163.com sent by the client, the client DNS server resolves the domain name alias to the portal domain name www.163.com.bbb.aaa.com , and then the client
  • the domain name resolution server 400 is requested to parse the portal domain name www.163.com.bbb.aaa.com, and the transceiver module 402 receives the parsing request of the portal domain name www.163.com.bbb.aaa.com, and then parses
  • the module 403 parses the entry domain name www.163.com.bbb.aaa.com, and returns the parsing result to the client as the parsing result of the domain name www.163.com requested by the client.
  • This type of aliasing based on a generic domain name can shorten the domain name system resolution time and reduce the domain name system resolution failure rate.
  • a domain name is attacked, it is easy to accurately identify the specific client being attacked by a layer of aliases, such as the content distribution network portal domain name www.163.com.bbb.aaa.com when attacked, due to www.163. Com.bbb.aaa.com is obtained through the alias analysis of www.163.com, that is, it can be known that the specific attacked domain name is www.163.com, which realizes attack tracing.
  • the domain name resolution server 400 further includes a scheduling module 404.
  • the scheduling module 404 is connected to the pan-domain name setting module 401 and the parsing module 403 respectively, and is configured to re-parse the generic domain name of the corresponding server group to another network protocol address when a certain server cluster in the server group fails.
  • the parsing module 403 includes a lookup module 4031 and a pan-domain name parsing module 4032.
  • the search module 4031 is configured to search whether the entry domain name has an exact match A record. If the entry domain name has an exact match A record, the exact match A record is returned to the client as a parsing result, and if not, the pan domain name parsing module 4032 Analyze.
  • the exact matching A record of the entry domain name includes the network protocol address of the source server corresponding to the domain name requested by the client and the network protocol address of the custom server corresponding to the domain name requested by the client, and the configuration is set by the setting module 401.
  • the lookup module 4031 searches and returns the network protocol address of the source station to the client as the parsing result.
  • the domain name requested by the client www.163.com needs to be returned in the Beijing Telecom area, then only need to set Www.163.com.bbb.aaa.com A record in the Beijing Telecom area, if the content distribution network receives the Beijing Telecom's www.163.com resolution request, the search module 4031 will use the source station's network protocol address as the analysis result. And returned to the client through the transceiver module 401.
  • the lookup module 4031 searches and returns the network protocol address of the customized server to the client as the parsing result. If the domain name requested by the client www.163.com needs to use a special server in Xinjiang Telecom, then only need to configure the server separately in the Xinjiang Telecom area for www.163.com, if the content distribution network receives the Xinjiang Telecom sent by the client. The www.163.com parses the request, and the lookup module 4031 returns the network protocol address of the custom server as the parsing result to the client through the transceiver module 401.
  • the generic domain name parsing module 4032 is configured to return the A record of the generic domain name corresponding to the portal domain name to the client as the parsing result of parsing the portal domain name when the search module 4031 does not find the exact matching A record corresponding to the portal domain name. If the domain name requested by the client www.163.com does not require any special configuration in Hunan Xinjiang Telecom, when the content distribution network receives the resolution request from Hunan Telecom's www.163.com sent by the client, the search module 4031 does not find it after searching.
  • Www.163.com.bbb.aaa.com Accurately matching A records, the A domain record corresponding to the generic domain name *.bbb.aaa.com by the pan-domain name resolution module 4032 as the entry domain name www.163.com.bbb.
  • the analysis result of the analysis by aaa.com is returned to the client through the transceiver module 401.
  • the invention does not need to modify the pan-domain name or the second-level domain name, and only needs to add a minimum amount of configuration to support a special back-source configuration or other special configuration.
  • the present invention further provides a domain name resolution system, which can implement the domain name resolution method in the embodiment shown in FIG.
  • the domain name resolution system provided by the embodiment of the present invention includes: a client DNS server 702 and a domain name resolution server 703 corresponding to any of the foregoing embodiments of FIG. 4 to FIG. 6.
  • the domain name alias requested by the client 701 is set to the portal domain name in the client DNS server 702.
  • the domain name of the portal domain is suffixed by the domain name requested by the client 701 and the suffix of the pan-domain name.
  • the client DNS server 702 receives the domain name resolution request sent by the client 701, and resolves the domain name requested by the client 701 to the portal domain name of the content distribution network.
  • the domain name resolution server 703 is a domain name resolution server corresponding to any embodiment of FIG. 4-6. After the client DNS server 702 resolves the domain name requested by the client 701 to the portal domain name of the content distribution network, the client 701 Will request the domain name resolution server 703 to enter the domain name Line resolution.
  • the domain name resolution server 703 sets the same pan-domain name for the portal domain name of the same server group; the domain name resolution server 703 receives the portal domain name resolution request, parses the portal domain name, and returns the analysis result to the client as the parsing result of the domain name requested by the client. End 701.
  • the client 701 sends a domain name resolution request of the www.163.com to the client DNS server 702.
  • the client DNS server 702 is provided with the domain name www.163.com alias requested by the client 701 to the portal domain name www.163. .com.bbb.aa.com
  • the client DNS server 702 resolves the domain name www.163.com requested by the client to the portal domain name of the content distribution network through the alias www.163.com.bbb.aaa.com
  • the domain name resolution server 703 receives the parsing request of the portal domain name www.163.com.bbb.aaa.com, and then parses the portal domain name www.163.com.bbb.aaa.com.
  • the domain name resolution server 703 returns the analysis result to the client 701 as the analysis result of the domain name www.163.com sent from the client 701.
  • the generic domain name *.bbb.aaa.com of the portal domain name www.163.com.bbb.aaa.com is the domain name resolution server 703 based on the server group used to resolve the portal domain name www.163.com.bbb.aaa.com By default, all portal domains that use this server group have the same pan-domain name *.bbb.aaa.com.
  • the domain name resolution server 703 parses the ingress domain name, and returns the parsing result as the parsing result of the domain name requested by the client to the client 701. Specifically, the method includes: searching whether the portal domain name has an exact matching A record, and if yes, the exact matching The A record is returned to the client 701 as an analysis result; otherwise, the A record of the generic domain name corresponding to the entry domain name is returned to the client 701 as the parsing result of parsing the entry domain name.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without deliberate labor.
  • the various embodiments can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware. Based on such understanding, the above technical solutions may or may not contribute to the prior art.
  • the computer software product can be stored in a computer readable storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes a plurality of instructions for causing a computer device (which can be a personal computer or a server) , or a network device, etc.) performs the methods described in various embodiments or portions of the embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

本发明公开了一种域名解析系统、域名解析服务器和域名解析方法，域名解析方法包括以下步骤：为使用同一服务器组的入口域名设置同一泛域名；将客户端请求的域名通过别名解析到入口域名；对入口域名进行解析，并将解析结果作为客户端请求的域名的解析结果返回给客户端。本发明提出一种基于泛域名的一层别名记录方式，与现有方法相比减少了一层系统域名的别名记录解析，能够缩短系统域名解析时间，降低系统域名解析失败率；同时基于系统域名的服务器调度时间缩短，配置量减少。本发明还支持特殊的回源配置或者其它特殊配置，且增加的配置量较少；当受到攻击时也容易发现遭到攻击的具体客户。

Description

域名解析系统、域名解析服务器和域名解析方法 技术领域
本发明涉及计算机技术领域，特别涉及一种域名解析系统、域名解析服务器和域名解析方法。
背景技术
当前大部分客户接入内容分发网络(CDN)的入口是将客户端请求的域名通过别名解析(CNAME)到CDN域名，每个客户端请求的域名对应一个CDN域名，以下本文中称该CDN域名为入口域名。
在CDN网络中，同一服务器组同时供很多客户端使用，如果每个入口域名直接解析出一个服务器组的IP，这样一旦这个服务器组不能提供服务了，将会有大量的域名需要切换，即需要修改该入口域名对应该服务器组的IP地址的记录，也即入口域名的A记录，生成这些A记录的时间较长，部署这些A记录的时间也会很长。所以现有技术中一般会再把使用同一服务器组的一级域名CNAME到相同的二级域名，这样，如果一个服务器组不能提供服务了则可快速的将该服务器组对应的二级域名解析到另一IP地址。
但是现有技术存在以下不足：域名解析查询需要至少两层别名解析，即将将客户端请求的域名CNAME到入口域名，再将入口域名CNAME到二级域名，两层别名解析会增加解析时间，且两层别名解析导致解析失败率也会提高。且当大量客户端两层别名解析到一个二级域名，一旦该二级域名遭到攻击，由于多个客户端的请求的域名对应同一个二级域名，故无法追溯到具体是哪个客户端遭受攻击。
发明内容
鉴于以上现有技术的问题，本发明实施例提供了一种域名解析系统、服务器和域名解析方法，以解决现有技术中两层别名解析导致的解析时间过长、解析失败率高，且无法追溯客户端被攻击的问题。
本发明实施例提供一种域名解析方法，包括以下步骤：
为使用同一服务器组的入口域名设置同一泛域名；
将客户端请求的域名通过别名解析到入口域名；
对入口域名进行解析，并将解析结果作为客户端请求的域名的解析结果返回给客户端。
具体的，入口域名由客户端请求的域名作为前缀及泛域名的后缀作为后缀组成。
进一步的，对入口域名进行解析，并将解析结果作为客户端请求的域名的解析结果返回给客户端的步骤包括：
查找入口域名是否有精确匹配的A记录，如有，则将精确匹配的A记录作为解析结果返回给客户端；否则将入口域名对应的泛域名的A记录作为解析结果返回给客户端。
具体的，入口域名的精确匹配的A记录包含客户端请求的域名对应源站服务器的网络协议地址，当客户端请求的域名需要回源时，将源站的网络协议地址作为解析结果返回给客户端。
具体的，入口域名的精确匹配的A记录包括客户端请求的域名对应定制服务器的网络协议地址，当客户端请求的域名需要使用定制服务器时，将定制服务器的网络协议地址作为解析结果返回给客户端。
进一步的，同一服务器组包括多个服务器集群，每个服务器集群具有唯一的网络协议地址，使用同一泛域名的入口域名被解析出同一服务器组对应的网络协议地址。
进一步的，域名解析方法还包括：
当服务器组中的某一服务器集群发生故障时，将对应服务器组的泛域名重新解析到另一网络协议地址。
本发明实施例还挺提供一种域名解析服务器，包括：
设置模块，用于为使用同一服务器组的入口域名设置同一泛域名；
收发模块，与设置模块连接，用于接收入口域名的解析请求，其中客户端请求的域名通过别名解析到入口域名；
解析模块，与收发模块连接，用于对入口域名进行解析，并将解析结果作 为客户端请求的域名的解析结果返回给客户端。
进一步的，解析模块包括：
查找模块，用于查找入口域名是否有精确匹配的A记录，如有，则将精确匹配的A记录作为解析结果返回给客户端；
泛域名解析模块，与查找模块连接，用于当查找模块没有查找到入口域名对应的精确匹配的A记录时，将入口域名对应的泛域名的A记录作为解析结果返回给客户端。
进一步的，域名解析服务器还包括：
调度模块，与设置模块和解析模块分别连接，用于当服务器组中的某一服务器集群发生故障时，将对应服务器组的泛域名重新解析到另一网络协议地址。
进一步的，设置模块还用于设置入口域名的精确匹配的A记录，入口域名的精确匹配的A记录包含客户端请求的域名对应源站服务器的网络协议地址，当客户端请求的域名需要回源时，查找模块将源站的网络协议地址作为解析结果返回给客户端。
进一步的，设置模块还用于设置入口域名的精确匹配的A记录，入口域名的精确匹配的A记录包括客户端请求的域名对应定制服务器的网络协议地址，当客户端请求的域名需要使用定制服务器时，查找模块将定制服务器的网络协议地址作为解析结果返回给客户端。
本发明实施例再提供一种域名解析系统，包括：
客户端DNS服务器，将客户端请求的域名通过别名解析到内容分发网络的入口域名；
包括前述域名解析服务器，为使用同一服务器组的入口域名设置同一泛域名；接收入口域名的解析请求，并对入口域名进行解析，将解析结果作为客户端请求的域名的解析结果返回给客户端。
进一步的，域名解析服务器对入口域名进行解析，并将解析结果作为客户端请求的域名的解析结果返回给客户端具体包括：查找入口域名是否有精确匹配的A记录，如有，则将精确匹配的A记录作为解析结果返回给公网DNS服务器；否则将入口域名对应的泛域名的A记录作为解析结果返回给客户端。
具体的，在客户端DNS服务器中设置客户端请求的域名别名到入口域名， 其中入口域名由客户端请求的域名作为前缀及泛域名的后缀作为后缀组成。
本发明实施例提供的技术方案带来的有益效果是：本发明提出一种基于泛域名的一层别名记录方式，与现有方法相比减少了一层系统域名的别名记录解析，能够缩短系统域名解析时间，降低系统域名解析失败率；同时基于系统域名的服务器调度时间缩短，配置量减少。
进一步的，本发明并不需要修改泛域名或二级域名，只需要增加最少量的配置即可支持特殊的回源配置或者其它特殊配置。另外，因其采用一层别名方式，当某一域名受到攻击时，也容易通过一层别名精确的发现遭到攻击的具体客户，实现攻击追溯。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明提供的一种域名解析方法的实施方式的流程图；
图2是本发明提供的另一种域名解析方法的实施方式的流程图；
图3是本发明提供的再一种域名解析方法的实施方式的流程图；
图4是本发明提供的一种域名解析服务器的实施方式的结构图；
图5是本发明提供的另一种域名解析服务器的实施方式的结构图；
图6是本发明提供的再一种域名解析服务器的实施方式的结构图；
图7是本发明提供的一种域名解析系统的实施方式的结构图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明实施方式作进一步地详细描述。
一方面，本发明提供一种域名解析方法的实施方式，如图1所示，包括以下步骤：
步骤S101，为使用同一服务器组的入口域名设置同一泛域名。在一实施例 中，在内容分发网络的DNS服务器上设置入口域名到泛域名的配置，其中，入口域名由客户端请求的域名作为前缀及泛域名的后缀作为后缀组成。举例而言，客户端请求的域名为www.163.com，泛域名为*.bbb.aaa.com，则入口域名为www.163.com.bbb.aaa.com。
同一服务器组包括多个服务器集群，每个服务器集群具有唯一的网络协议地址(IP)，使用同一泛域名的入口域名被解析出同一服务器组对应的网络协议地址。在内容分发网络中有若干个入口域名www.163.com.bbb.aaa.com、news.163.com.bbb.aaa.com和music.163.com.bbb.aaa.com，……，这些入口域名在内容分发网络中均使用网络协议地址为192.168.100.100的服务器组。这些入口域名均设置有同一个泛域名*.bbb.aaa.com。故客户端请求的域名、入口域名及泛域名之间的设置规则是相互关联的。
步骤S102，将客户端请求的域名通过别名解析到内容分发网络的入口域名。客户端需要对域名进行加速解析的时候，只需在客户端的DNS服务器上配置客户端请求的域名别名到入口域名。例如，客户端DNS服务器收到客户端发来的www.163.com的域名解析请求，将www.163.com通过别名解析到内容分发网络的入口域名www.163.com.bbb.aaa.com。其他客户端发来请求解析的域名以此类推，本发明不再赘述。这种入口域名只对客户端请求解析的域名别名解析一次得到。
步骤S103，对入口域名进行解析，并将解析结果作为客户端请求的域名的解析结果返回给客户端。客户端DNS服务器将客户端请求的域名通过别名解析到内容分发网络的入口域名之后，客户端就会向内容分发网络的DNS服务器请求对该入口域名进行解析，内容分发网络的DNS服务器接收该解析请求并对入口域名www.163.com.bbb.aaa.com进行解析，将解析结果作为客户端请求的域名的解析结果返回给客户端。具体的，如前述，在内容分发网络的DNS服务器中设置了配置，即，使用同一服务器组的入口域名设置同一泛域名，所以对该入口域名进行解析的具体过程可以采用查找入口域名精确匹配的A记录及入口域名对应的泛域名的A记录的方式进行解析，具体解析过程可参见如图2对应的实施方式。
这种基于泛域名的一层别名记录方式，可以缩短域名系统解析时间，降低域名系统解析失败率。当某一域名受到攻击时，受攻击的域名只可能是精确的 域名，例如入口域名或客户端请求解析的域名，容易通过一层别名精确的发现遭到攻击的具体客户，比如当这个入口域名www.163.com.bbb.aaa.com受到攻击时，由于www.163.com.bbb.aaa.com是通过www.163.com别名解析得到，即可以得知具体被攻击的域名是www.163.com，实现攻击追溯。
本发明的另一种域名解析方法的实施方式如图2所示，步骤S103具体包括以下步骤：
步骤S1031，查找入口域名是否有精确匹配的A记录。在一实施方式中，入口域名的精确匹配的A记录包含客户端请求的域名对应源站服务器的网络协议地址和客户端请求的域名对应定制服务器的网络协议地址。如果入口域名有精确匹配的A记录，则进行步骤S1032，否则进行步骤S1033。
步骤S1032，将精确匹配的A记录作为解析结果返回给客户端。
当客户端请求的域名需要回源时，将源站的网络协议地址作为解析结果返回给客户端。比如客户端请求的域名www.163.com在北京电信区域需要回源，那么只需要在内容分发网络的DNS服务器上设置www.163.com.bbb.aaa.com在北京电信区域的A记录，如果内容分发网络收到北京电信的请求，会优先精确匹配到配置的A记录进行回源。
当客户端请求的域名需要使用定制服务器时，将定制服务器的网络协议地址作为解析结果返回给客户端。如客户端请求的域名www.163.com在新疆电信需要使用特殊的服务器，那么只需要在在内容分发网络的DNS服务器上为www.163.com在新疆电信区域单独配置服务器，如果内容分发网络收到新疆电信的请求，会优先匹配到单独配置的服务器。
步骤S1033，将入口域名对应的泛域名的A记录作为解析结果返回给客户端。如果入口域名没有前述精确匹配的A记录，则查找该入口域名对应的泛域名，泛域名的A记录作为对入口域名进行解析的解析结果返回给客户端。
本发明并不需要修改泛域名或二级域名，只需要增加最少量的配置即可支持特殊的回源配置或者其它特殊配置，增加的配置量小，且容易实施，可满足域名解析的特殊要求。
本发明的再一种实施方式如图3所示，步骤S301-S303参考如图1中步骤 S101-S103，故不再赘述。在本实施例中，域名解析方法还包括：步骤S304，当服务器组中的某一服务器集群发生故障时，将对应服务器组的泛域名重新解析到另一网络协议地址。
比如www.163.com.bbb.aaa.com、news.163.com.bbb.aaa.com和music.163.com.bbb.aaa.com均使用网络协议地址为192.168.100.100的服务器组，当这三个入口域名使用的服务器组(192.168.100.100)发生故障时，只需要在内容分发网络的DNS服务器中生成一条域名系统配置，将这三个入口域名在内容分发网络中的泛域名*.bbb.aaa.com，由原来的服务器组的网络协议地址192.168.100.100重新配置到一个新的服务器组的网络协议地址如192.168.100.110上，即将前述三个入口域名对应的泛域名*.bbb.aaa.com重新解析到192.168.100.110，即可以将三个入口域名在内容分发网络中一次性全部转移到新的服务器集群，而不需要逐个更改www.163.com.bbb.aaa.com、news.163.com.bbb.aaa.com和music.163.com.bbb.aaa.com对应的配置，缩短服务器调度时间，减少配置量。
本发明还提供一种域名解析服务器400的实施方式，如图4所示，包括：设置模块401、收发模块402和解析模块403。设置模块401用于为使用同一服务器组的入口域名设置同一泛域名；收发模块402与泛域名设置模块401连接，用于接收入口域名的解析请求，其中，客户端请求的域名通过别名解析到内容分发网络的入口域名；解析模块403与收发模块402连接，用于对入口域名进行解析，并将解析结果作为客户端请求的域名的解析结果返回给客户端。
整个域名解析服务器400的工作过程如下：比如在内容分发网络中有三个入口域名均使用网络协议地址为1.1.1.1的服务器组，这三个入口域名分别为www.163.com.bbb.aaa.com、news.163.com.bbb.aaa.com和music.163.com.bbb.aaa.com。
域名设置模块401为这三个入口域名设置同一个泛域名*.bbb.aaa.com。当客户端DNS服务器收到客户端发来的域名www.163.com的解析请求时，客户端DNS服务器将该域名别名解析到入口域名www.163.com.bbb.aaa.com，然后客户端就会向域名解析服务器400请求对该入口域名www.163.com.bbb.aaa.com进行解析，收发模块402接收该入口域名www.163.com.bbb.aaa.com的解析请求，然 后解析模块403对入口域名www.163.com.bbb.aaa.com进行解析，将解析结果作为客户端请求的域名www.163.com的解析结果返回给客户端。这种基于泛域名的一层别名记录方式可以缩短域名系统解析时间，降低域名系统解析失败率。当某一域名受到攻击时，容易通过一层别名精确的发现遭到攻击的具体客户，如这个内容分发网络入口域名www.163.com.bbb.aaa.com受到攻击时，由于www.163.com.bbb.aaa.com是通过www.163.com别名解析得到，即可以得知具体被攻击的域名是www.163.com，实现攻击追溯。
具体的，在本发明的另一种域名解析服务器400的实施方式中，如图5所示，域名解析服务器400如还包括调度模块404。调度模块404与泛域名设置模块401和解析模块403分别连接，用于当服务器组中的某一服务器集群发生故障时，将对应服务器组的泛域名重新解析到另一网络协议地址。
当入口域名www.163.com.bbb.aaa.com、news.163.com.bbb.aaa.com和music.163.com.bbb.aaa.com使用的服务器组发生故障时，内容分发网络生成一条域名系统配置，将这三个入口域名在内容分发网络中的泛域名*.bbb.aaa.com，由原来的服务器组的网络协议地址1.1.1.1重新配置到一个新的服务器组的网络协议地址如1.1.1.2上，即将泛域名*.bbb.aaa.com重新解析到1.1.1.2。调度模块404只通过一条域名系统配置，就将三个用户域名在内容分发网络中一次性全部转移到新的服务器组，缩短服务器调度时间，减少配置量。
本发明的再一种域名解析服务器400的实施方式中，如图6所示，解析模块403包括：查找模块4031和泛域名解析模块4032。
查找模块4031用于查找入口域名是否有精确匹配的A记录，如果入口域名有精确匹配的A记录，则将精确匹配的A记录作为解析结果返回给客户端，如果没有则由泛域名解析模块4032进行解析。
入口域名的精确匹配的A记录包含客户端请求的域名对应源站服务器的网络协议地址和客户端请求的域名对应定制服务器的网络协议地址，该配置通过设置模块401来设置达成。当客户端请求的域名需要回源时，查找模块4031查找后将源站的网络协议地址作为解析结果返回给客户端。比如客户端请求的域名www.163.com在北京电信区域需要回源，那么只需要设置 www.163.com.bbb.aaa.com在北京电信区域的A记录，如果内容分发网络收到北京电信的www.163.com解析请求，查找模块4031会将源站的网络协议地址作为解析结果，通过收发模块401返回给客户端。
当客户端请求的域名需要使用定制服务器时，查找模块4031查找后将定制服务器的网络协议地址作为解析结果返回给客户端。如客户端请求的域名www.163.com在新疆电信需要使用特殊的服务器，那么只需要为www.163.com在新疆电信区域单独配置服务器，如果内容分发网络收到客户端发来的新疆电信的www.163.com解析请求，查找模块4031会将定制服务器的网络协议地址作为解析结果通过收发模块401返回客户端。
泛域名解析模块4032用于当查找模块4031没有查找到入口域名对应的精确匹配的A记录时，将入口域名对应的泛域名的A记录作为对入口域名进行解析的解析结果返回给客户端。如客户端请求的域名www.163.com在湖南疆电信不需要任何特殊配置，当内容分发网络收到客户端发来的湖南电信的www.163.com解析请求，查找模块4031查找后没有发现www.163.com.bbb.aaa.com精确匹配的A记录，则由泛域名解析模块4032对泛域名*.bbb.aaa.com对应的A记录作为对入口域名www.163.com.bbb.aaa.com进行解析的解析结果，通过收发模块401返回客户端。
本发明并不需要修改泛域名或二级域名，只需要增加最少量的配置即可支持特殊的回源配置或者其它特殊配置。
本发明再提供一种域名解析系统，可实现如图1所述实施例中的域名解析方法。如图7所示，本发明实施例提供的域名解析系统包括：客户端DNS服务器702和前述如图4到图6任意一实施例对应的域名解析服务器703。
客户端DNS服务器702中设置客户端701请求的域名别名到入口域名，其中入口域名由客户端701请求的域名作为前缀及泛域名的后缀作为后缀组成。客户端DNS服务器702接收客户端701发来的域名解析请求，将客户端701请求的域名通过别名解析到内容分发网络的入口域名。
域名解析服务器703为如图4-图6任意一实施例对应的的域名解析服务器，客户端DNS服务器702将客户端701请求的域名通过别名解析到内容分发网络的入口域名之后，客户端701就会向域名解析服务器703请求对该入口域名进 行解析。域名解析服务器703为使用同一服务器组的入口域名设置同一泛域名；域名解析服务器703接收该入口域名解析请求，并对入口域名进行解析，将解析结果作为客户端请求的域名的解析结果返回给客户端701。
举例而言，客户端701向客户端DNS服务器702发送www.163.com的域名解析请求，客户端DNS服务器702中设置有客户端701请求的域名www.163.com别名到入口域名www.163.com.bbb.aaa.com，客户端DNS服务器702将客户端请求的域名www.163.com通过别名解析到内容分发网络的入口域名www.163.com.bbb.aaa.com，域名解析服务器703接收该入口域名www.163.com.bbb.aaa.com的解析请求，然后对入口域名www.163.com.bbb.aaa.com进行解析。解析完成后域名解析服务器703将解析结果作为客户端701发来的域名www.163.com的解析结果返回给客户端701。
其中入口域名www.163.com.bbb.aaa.com的泛域名*.bbb.aaa.com是域名解析服务器703根据解析入口域名www.163.com.bbb.aaa.com所使用的服务器组提前预设好的，所有使用这一服务器组的入口域名均设置了同一泛域名*.bbb.aaa.com。
域名解析服务器703对入口域名进行解析，并将解析结果作为客户端请求的域名的解析结果返回给客户端701具体包括：查找入口域名是否有精确匹配的A记录，如有，则将精确匹配的A记录作为解析结果返回给客户端701；否则将入口域名对应的泛域名的A记录作为对入口域名进行解析的解析结果返回给客户端701。
上述本发明实施例序号仅仅为了描述，不代表实施例的优劣。
以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性的劳动的情况下，即可以理解并实施。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到各实施方式可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件。基于这样的理解，上述技术方案本质上或者说对现有技术做出贡献的部分可以 以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行各个实施例或者实施例的某些部分所述的方法。
以上所述仅为本发明的较佳实施例，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (15)

  1. 一种域名解析方法，其特征在于，包括以下步骤：
    为使用同一服务器组的入口域名设置同一泛域名；
    将客户端请求的域名通过别名解析到所述入口域名；
    对所述入口域名进行解析，并将解析结果作为所述客户端请求的域名的解析结果返回给所述客户端。
  2. 如权利要求1所述的域名解析方法，其特征在于，所述入口域名由所述客户端请求的域名作为前缀及所述泛域名的后缀作为后缀组成。
  3. 如权利要求1所述的域名解析方法，其特征在于，所述对所述入口域名进行解析，并将解析结果作为所述客户端请求的域名的解析结果返回给所述客户端的步骤包括：
    查找所述入口域名是否有精确匹配的A记录，如有，则将所述精确匹配的A记录作为解析结果返回给所述客户端；否则将所述入口域名对应的泛域名的A记录作为解析结果返回给所述客户端。
  4. 如权利要求3所述的域名解析方法，其特征在于，所述入口域名的精确匹配的A记录包含所述客户端请求的域名对应源站服务器的网络协议地址，当所述客户端请求的域名需要回源时，将所述源站的网络协议地址作为解析结果返回给所述客户端。
  5. 如权利要求3所述的域名解析方法，其特征在于，所述入口域名的精确匹配的A记录包括所述客户端请求的域名对应定制服务器的网络协议地址，当所述客户端请求的域名需要使用定制服务器时，将所述定制服务器的网络协议地址作为解析结果返回给所述客户端。
  6. 如权利要求1所述的域名解析方法，其特征在于，所述同一服务器组包括多个服务器集群，每个服务器集群具有唯一的网络协议地址，所述使用同一 泛域名的入口域名被解析出所述同一服务器组对应的网络协议地址。
  7. 如权利要求6所述的域名解析方法，其特征在于，所述域名解析方法还包括：
    当所述服务器组中的某一服务器集群发生故障时，将对应所述服务器组的所述泛域名重新解析到另一网络协议地址。
  8. 一种域名解析服务器，其特征在于，包括：
    设置模块，用于为使用同一服务器组的入口域名设置同一泛域名；
    收发模块，与所述设置模块连接，用于接收所述入口域名的解析请求，其中客户端请求的域名通过别名解析到所述入口域名；
    解析模块，与所述收发模块连接，用于对所述入口域名进行解析，并将解析结果作为所述客户端请求的域名的解析结果返回给所述客户端。
  9. 如权利要求8所述的域名解析服务器，其特征在于，所述解析模块包括：
    查找模块，用于查找所述入口域名是否有精确匹配的A记录，如有，则将所述精确匹配的A记录作为解析结果返回给所述客户端；
    泛域名解析模块，与所述查找模块连接，用于当所述查找模块没有查找到所述入口域名对应的精确匹配的A记录时，将所述入口域名对应的泛域名的A记录作为解析结果返回给所述客户端。
  10. 如权利要求8所述的域名解析服务器，其特征在于，所述域名解析服务器还包括：
    调度模块，与所述设置模块和所述解析模块分别连接，用于当所述服务器组中的某一服务器集群发生故障时，将对应所述服务器组的所述泛域名重新解析到另一网络协议地址。
  11. 如权利要求9所述的域名解析服务器，其特征在于，所述设置模块还用于设置所述入口域名的精确匹配的A记录，所述入口域名的精确匹配的A记录包含所述客户端请求的域名对应源站服务器的网络协议地址，当所述客户端 请求的域名需要回源时，所述查找模块将所述源站的网络协议地址作为解析结果返回给所述客户端。
  12. 如权利要求9所述的域名解析服务器，其特征在于，所述设置模块还用于设置所述入口域名的精确匹配的A记录，所述入口域名的精确匹配的A记录包括所述客户端请求的域名对应定制服务器的网络协议地址，当所述客户端请求的域名需要使用定制服务器时，所述查找模块将所述定制服务器的网络协议地址作为解析结果返回给所述客户端。
  13. 一种域名解析系统，其特征在于，包括：
    客户端DNS服务器，将客户端请求的域名通过别名解析到内容分发网络的入口域名；
    如权利要求8至权利要求12任意一项所述的域名解析服务器，为使用同一服务器组的所述入口域名设置同一泛域名；接收所述入口域名的解析请求，并对所述入口域名进行解析，将解析结果作为所述客户端请求的域名的解析结果返回给所述客户端。
  14. 如权利要求13所述的域名解析系统，其特征在于，所述域名解析服务器对所述入口域名进行解析，并将解析结果作为所述客户端请求的域名的解析结果返回给所述客户端具体包括：查找所述入口域名是否有精确匹配的A记录，如有，则将所述精确匹配的A记录作为解析结果返回给所述公网DNS服务器；否则将所述入口域名对应的泛域名的A记录作为解析结果返回给所述客户端。
  15. 如权利要求13所述的域名解析系统，其特征在于，在所述客户端DNS服务器中设置所述客户端请求的域名别名到所述入口域名，其中所述入口域名由所述客户端请求的域名作为前缀及所述泛域名的后缀作为后缀组成。
PCT/CN2017/075002 2017-02-19 2017-02-27 域名解析系统、域名解析服务器和域名解析方法 WO2018148984A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/748,757 US20190036870A1 (en) 2017-02-19 2017-02-27 Domain name resolution system, domain name resolution server, and domain name resolution method
EP17875072.5A EP3389244B1 (en) 2017-02-19 2017-02-27 Domain name resolution system, domain name resolution server, and domain name resolution method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710088022.1 2017-02-19
CN201710088022.1A CN107071078B (zh) 2017-02-19 2017-02-19 域名解析系统、域名解析服务器和域名解析方法

Publications (1)

Publication Number Publication Date
WO2018148984A1 true WO2018148984A1 (zh) 2018-08-23

Family

ID=59622756

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/075002 WO2018148984A1 (zh) 2017-02-19 2017-02-27 域名解析系统、域名解析服务器和域名解析方法

Country Status (4)

Country Link
US (1) US20190036870A1 (zh)
EP (1) EP3389244B1 (zh)
CN (1) CN107071078B (zh)
WO (1) WO2018148984A1 (zh)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108462760B (zh) * 2018-03-21 2020-01-10 平安科技（深圳）有限公司 电子装置、集群访问域名自动生成方法及存储介质
CN108900648B (zh) * 2018-06-13 2020-11-06 网宿科技股份有限公司 一种控制多cname流量比例的方法和装置
CN109561101B (zh) * 2018-12-25 2021-08-10 上海点融信息科技有限责任公司 针对拒绝服务攻击的处理方法和装置
CN110213398B (zh) * 2019-05-30 2021-10-08 腾讯科技（深圳）有限公司 别名管理方法、装置、服务器及存储介质
CN110708309A (zh) * 2019-09-29 2020-01-17 武汉极意网络科技有限公司 反爬虫系统及方法
CN111629079B (zh) * 2020-04-29 2023-02-28 四川速宝网络科技有限公司 一种实现网络访问加速的系统及装置
CN112380072A (zh) * 2020-12-07 2021-02-19 中国建设银行股份有限公司 多数据中心访问方法及系统
CN112671860B (zh) * 2020-12-15 2023-04-18 杭州溪塔科技有限公司 用于kubernetes集群的服务访问方法、系统、电子设备及介质
CN112769976B (zh) * 2021-01-13 2023-10-24 网宿科技股份有限公司 一种域名解析方法及系统
CN113556411B (zh) * 2021-06-28 2023-05-26 深圳市高德信通信股份有限公司 一种cdn视频调度设备及方法
CN114448787A (zh) * 2021-12-27 2022-05-06 天翼云科技有限公司 一种cdn系统频道配置方法、装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130198409A1 (en) * 2012-02-01 2013-08-01 Microsoft Corporation Efficient implementation of user-provided dns names
CN103501358A (zh) * 2013-09-18 2014-01-08 北京蓝汛通信技术有限责任公司 一种域名托管管理方法及装置
CN106209832A (zh) * 2016-07-08 2016-12-07 中国互联网络信息中心 基于ns记录转移授权缓解域名权威记录劫持影响的方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7289519B1 (en) * 2002-05-01 2007-10-30 Cisco Technology, Inc. Methods and apparatus for processing content requests using domain name service
US8533317B2 (en) * 2009-06-22 2013-09-10 Citrix Systems, Inc. Systems and methods for monitor distribution in a multi-core system
CN103037030B (zh) * 2012-12-10 2016-01-27 中国科学院计算机网络信息中心 支持域名组dns解析的方法和系统
KR20150079422A (ko) * 2013-12-30 2015-07-08 주식회사 아이디어웨어 서버 그룹핑 장치, 그 방법 및 기록 매체

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130198409A1 (en) * 2012-02-01 2013-08-01 Microsoft Corporation Efficient implementation of user-provided dns names
CN103501358A (zh) * 2013-09-18 2014-01-08 北京蓝汛通信技术有限责任公司 一种域名托管管理方法及装置
CN106209832A (zh) * 2016-07-08 2016-12-07 中国互联网络信息中心 基于ns记录转移授权缓解域名权威记录劫持影响的方法

Also Published As

Publication number Publication date
CN107071078B (zh) 2019-05-10
US20190036870A1 (en) 2019-01-31
EP3389244A1 (en) 2018-10-17
CN107071078A (zh) 2017-08-18
EP3389244B1 (en) 2020-05-13
EP3389244A4 (en) 2019-03-06

Similar Documents

Publication Publication Date Title
WO2018148984A1 (zh) 域名解析系统、域名解析服务器和域名解析方法
US11632353B2 (en) Delegating DNS records to additional providers
CN105959433B (zh) 一种域名解析方法及其域名解析系统
WO2019061522A1 (zh) 域名解析方法、客户端、边缘节点及域名解析系统
US9525749B2 (en) DNS server arrangement and method
US10148611B2 (en) Network address sharing in a multitenant, monolithic application environment
US8103795B2 (en) TCP/IP host name resolution on a private network
CN103581213B (zh) 一种共享Hosts文件的应用方法、设备和系统
JP5974079B2 (ja) 変更ホストネームを使用するグローバル・トラフィック管理
WO2018188423A1 (zh) Dns服务器及配置加载方法、网络系统、域名解析方法及系统
US10341288B2 (en) Methods circuits devices systems and associated computer executable code for providing conditional domain name resolution
CN103685590A (zh) 获取ip地址的方法及系统
WO2017161965A1 (zh) 一种动态域名系统dns重定向方法、装置及系统
JP2019506692A (ja) データを処理する方法、装置、及びコンピュータプログラム、並びに階層ドメインネームシステムのゾーンファイル
CN103037029B (zh) 基于绑定注册的域名whois查询方法和服务系统
US20170295131A1 (en) Resource identification through dynamic domain name system (dns) labels
CN102624914A (zh) 通过Web方式探测客户端使用的本地DNS服务器的方法
CN105282269A (zh) 一种本地dns根服务器的配置方法和服务方法
CN104580542A (zh) Dns系统的智能解析方法
US8732314B2 (en) Generation of contact information based on associating browsed content to user actions
CN110868450B (zh) 双机房多入口会话保持方法、系统、装置及存储介质
CN105429880B (zh) 网络设备及其进行路由转发的方法
CN105245626B (zh) 在专网中使用快捷域名实现网站寻址的方法
JP6001512B2 (ja) 通信制御システム及び通信制御方法
US10291612B2 (en) Bi-directional authentication between a media repository and a hosting provider

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE