US20190036870A1 - Domain name resolution system, domain name resolution server, and domain name resolution method - Google Patents

Domain name resolution system, domain name resolution server, and domain name resolution method Download PDF

Info

Publication number
US20190036870A1
US20190036870A1 US15/748,757 US201715748757A US2019036870A1 US 20190036870 A1 US20190036870 A1 US 20190036870A1 US 201715748757 A US201715748757 A US 201715748757A US 2019036870 A1 US2019036870 A1 US 2019036870A1
Authority
US
United States
Prior art keywords
domain name
client
portal
resolution
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US15/748,757
Other languages
English (en)
Inventor
Xiaoying WU
Zhenyong WU
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Wangsu Science and Technology Co Ltd
Original Assignee
Wangsu Science and Technology Co Ltd
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 Wangsu Science and Technology Co Ltd filed Critical Wangsu Science and Technology Co Ltd
Assigned to WANGSU SCIENCE & TECHNOLOGY CO., LTD. reassignment WANGSU SCIENCE & TECHNOLOGY CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: WU, Xiaoying, WU, Zhenyong
Publication of US20190036870A1 publication Critical patent/US20190036870A1/en
Abandoned legal-status Critical Current

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]
    • H04L61/1511—
    • 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
    • H04L67/42—
    • 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 disclosure relates to the field of computer technology and, more particularly, relates to a domain name resolution system, a domain name resolution server, and a domain name resolution method.
  • the portal for the most clients to access the content delivery network resolves a domain name requested by the client to the CDN domain name via a Canonical Name (CNAME), and each domain name requested by the client corresponds to one CDN domain name.
  • CDN domain name is called a portal domain name.
  • the same server group is supplied for use simultaneously by various clients. If the IP of one server group is resolved directly for each portal domain name, once the one server group is unable to provide service, a large amount of domain names need to be switched, that is, the record of the IP address of the one server group corresponding to the portal domain name (i.e., the A record of the portal domain name) needs to be modified.
  • the time to generate the A record can be relatively long, and the time to arrange the A record can be also relatively long. Accordingly, in existing technologies, often the top-level domain names using the same server group are aliased to the same second-level domain name via a CNAME. As such, if one server group cannot provide service, the second-level domain name corresponding to such server group may be rapidly resolved to another IP address.
  • the two-layer CNAME resolution may increase the resolution time, and the failure rate caused by the two-layer CNAME resolution may be also increased.
  • a large amount of clients are resolved to a second-level domain name via two-layer CNAME resolution, once the second-level domain name is under attack, because the domain names requested by a plurality of clients correspond to the same second-level domain name, it is nearly impossible to trace which client is specifically under attack.
  • embodiments of the present disclosure provides a domain name resolution system, server, and domain name resolution method, thereby solving the issues of a too long resolution time, a high resolution failure rate, and failure to trace the client under attack caused by the two-layer CNAME resolution in existing technologies.
  • Embodiments of the present disclosure provide a domain name resolution method, comprising the following steps:
  • the portal domain name includes the domain name requested by the client as a prefix and a suffix of the extensive domain name as the suffix.
  • steps of resolving the portal domain name, and using the resolution result as the resolution result of the domain requested by the client to be sent back to the client comprise:
  • the precisely matched A record of the portal domain name comprises a network protocol address of a source station server corresponding to the domain name requested by the client, and when the domain name requested by the client needs to be back to a source station, the network protocol address of the source station is used as the resolution result to be sent back to the client.
  • the precisely matched A record of the portal domain name comprises a network protocol address of a custom server corresponding to the domain name requested by the client, and when the domain name requested by the client needs to use the custom server, the network protocol address of the custom server is used as the resolution result to be sent back to the client.
  • the same server group comprises a plurality of server clusters, each server cluster has a unique network protocol address, and the network protocol address corresponding to the same service group is resolved for the portal domain names using the same extensive domain name.
  • domain name resolution method further comprises:
  • Embodiments of the present disclosure further provide a domain name resolution server, comprising:
  • a sending/receiving module connected to the configuring module and configured to receive a resolution request of a portal domain name, where the domain name requested by the client is resolved to the portal domain name via a CNAME;
  • a resolving module connected to the sending/receiving module, configured to perform resolving on the portal domain name, and use a resolution result as the resolution result of the domain name requested by the client to be sent back to the client.
  • the resolving module comprises:
  • a searching module configured to search whether the portal domain name has a precisely matched A record or not, if yes, the precisely matched A record is used as the resolution result to be sent back to the client;
  • An extensive domain name resolving module connected to the searching module and configured to, when the searching module finds no precisely matched A record corresponding to the portal domain name, use an A record of the extensive domain name corresponding to the portal domain name as the resolution result to be sent back to the client.
  • domain name resolution server further comprises:
  • a scheduling module connected to the configuring module and the resolving module, respectively, and configured to, when a certain server cluster in the server group encounters a fault, re-resolve the extensive domain name of the corresponding server group to another network protocol address.
  • the configuring module is for configuring a precisely matched A record of the portal domain name
  • the precisely matched A record of the portal domain name comprises a 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 back to a source station, the searching module uses the network protocol address of the source station as the resolution result to be sent back to the client.
  • the configuring module is for further configuring the precisely matched A record of the portal domain name, the precisely matched A record of the portal domain name comprises a network protocol address of a custom server corresponding to the domain name requested by the client, and when the domain name requested by the client needs to use the custom server, the searching module uses the network protocol address of the custom server as the resolution result to be sent back to the client.
  • Embodiments of the present disclosure further provide a domain name resolution system, comprising:
  • a client DNS server configured to resolve the domain name requested by the client to an portal domain name of a content delivery network via a CNAME;
  • the aforementioned domain name resolution server configured to configure a same extensive domain name for portal domain names using the same server group; receive a resolution request of the portal domain name, perform resolving on the portal domain name, and use the resolution result as the resolution result of the domain name requested by the client to be sent back to the client.
  • performing resolving, by the domain name resolution server, on the portal domain name, and using the resolution result as the resolution result of the domain name requested by the client to be sent back to the client specifically comprises: searching whether the portal domain name has a precisely matched A record, if yes, using the precisely matched A record as the resolution result to be sent back to a public network DNS server; otherwise, using an A record of the extensive domain name corresponding to the portal domain name as the resolution result to be sent back to the client.
  • the domain name requested by the client is aliased to the portal domain name via a CNAME, where the portal domain name includes the domain name requested by the client as a prefix and a suffix of the extensive domain name as the suffix.
  • the present disclosure proposes a one-layer CNAME record method based on the extensive domain name, thereby reducing the CNAME record analysis by one layer of system domain name, shortening the system domain name resolution time, and decreasing the failure rate of the system domain name resolution with respect to the existing method; and at the same time, the scheduling time of the server based on the system domain name is shortened, and the configuration amount is decreased.
  • the present disclosure no longer needs to modify the extensive domain name or the second-level domain name, and only the minimum amount of configuration needs to be added to support the special back-to-source configuration or other special configuration. Further, because the one-layer CNAME method is used, when a certain domain name is attacked, the specific client under attack may be easily and precisely found via the one-layer CNAME, thereby finding the source of the attack.
  • FIG. 1 illustrates a flow chart of an implementation method of a domain name resolution method according to the present disclosure
  • FIG. 2 illustrates a flow chart of an implementation method of another domain name resolution method according to the present disclosure
  • FIG. 3 illustrates a flow chart of an implementation method of another domain name resolution method according to the present disclosure
  • FIG. 4 illustrates a structural view of an implementation method of a domain name resolution server according to the present disclosure
  • FIG. 5 illustrates a structural view of an implementation method of another domain name resolution server according to the present disclosure
  • FIG. 6 illustrates a structural view of an implementation method of another domain name resolution server according to the present disclosure.
  • FIG. 7 illustrates a structural view of an implementation method of a domain name resolution system according to the present disclosure.
  • the present disclosure provides an implementation method of a domain name resolution method. As shown in FIG. 1 , the method comprises the following steps:
  • Step S 101 configuring a same extensive domain name for portal domain names using a same server group.
  • a configuration from an portal domain name pointing to an extensive domain name is configured at a DNS server of a content distribute network (CDN), where the portal domain name comprises a domain name requested by a client as a prefix and a suffix of the extensive domain name as the suffix.
  • CDN content distribute network
  • the portal domain name comprises a domain name requested by a client as a prefix and a suffix of the extensive domain name as the suffix.
  • the portal domain name is www.163.com.bbb.aaa.com.
  • the same server group may comprise a plurality of server clusters, each server cluster has a unique network protocol address (IP), and the portal domain names using the same extensive domain name are resolved to have a network protocol address corresponding to the same server group.
  • the content delivery network may have a plurality of portal domain names, such as www.163.com.bbb.aaa.com, news.163.com.bbb.aaa.com, and music.163.com.bbb.aaa.com, etc.
  • portal domain names may all use the server group with a network protocol address of 192.168.100.100 in the content delivery network.
  • the portal domain names may be all configured to have a same extensive domain name *.bbb.aaa.com. Accordingly, the configuration rules between the domain name requested by the client, the portal domain name, and the extensive domain name are associated.
  • Step S 102 resolving the domain name requested by the client to the portal domain name of the content delivery network via a CNAME.
  • the client DNS server receives the domain name request of www.163.com sent from the client, and resolves www.163.com to the portal domain name www.163.com.bbb.aaa.com of the content delivery network via a CNAME.
  • the domain names that request resolving sent from other clients are processed in a similar way, which is not repeated described here in the present disclosure.
  • Such portal domain name may be obtained by aliasing the domain name requested by the client one time via a CNAME.
  • Step S 103 performing resolving on the portal domain name, and using a resolution result as the resolution result of the domain name requested by the client to be sent back to the client.
  • a client DNS server resolves the domain name requested by the client to the portal domain name of the content delivery network via a CNAME
  • the client may request the DNS server of the content delivery network to perform resolving on the portal domain name.
  • the DNS server of the content delivery network receives the resolution request and performs resolving on the portal domain name such as www.163.com.bbb.aaa.com, and uses the resolution result as the resolution result of the domain name requested by the client to be sent back to the client.
  • a configuration is configured in the DNS server of the content delivery network.
  • the portal domain names using the same server group are configured to have the same extensive domain name.
  • the specific process of resolving the portal domain name may use a method of searching for a precisely matched A record of the portal domain name and an A record of an extensive domain name corresponding to the portal domain name for resolving.
  • the specific resolving process may refer to the implementation method corresponding to FIG. 2 .
  • Such one-layer CNAME record method based on extensive domain name may shorten the resolution time of the domain name system and reduce the resolution failure rate of the domain name system.
  • the domain name under attack may only be a precise domain name, such as the portal domain name or the domain name for which the client requests to resolve.
  • the specific client under attack may be found easily and precisely via the one-layer CNAME.
  • the domain name specifically under attack may thus be known to be www.163.com, thereby finding the source of the attack.
  • Step S 103 may specifically comprise the following steps:
  • Step S 1031 searching whether the portal domain name has a precisely matched A record.
  • the precisely matched A record of the portal domain name comprises a network protocol address of the source station server corresponding to the domain name requested by the client and a network protocol address of a custom server corresponding to the domain name requested by the client. If the portal domain name has a precisely matched A record, Step S 1032 is performed, otherwise Step S 1033 is performed.
  • Step S 1032 using the precisely matched A record as a resolution result to be sent back to the client.
  • the network protocol address of the source station is used as the resolution result to be sent back to the client.
  • the domain name www.163.com requested by the client needs to be back to the source station at the Beijing telecom area
  • only the A record of www.163.com.bbb.aaa.com at the Beijing telecom area needs to be configured at the DNS server of the content delivery network. If the content delivery network receives a request from the Beijing telecom, the A record precisely matched with the configuration may be preferably sent back to the client.
  • the network protocol address of the custom server is used as the resolution result to be sent back to the client.
  • a server may be individually configured for www.163.com at the Xinjiang telecom region over the DNS server of the content delivery network. If the content delivery network receives a request from the Xinjiang telecom, the server individually configured may be preferably matched.
  • Step S 1033 using the A record of the extensive domain name corresponding to the portal domain name as the resolution result to be sent back to the client. If the portal domain name has no aforementioned precisely matched A record, the extensive domain name corresponding to the portal domain name is searched, and the A record of the extensive domain name is used as the resolution result after performing resolving on the portal domain name to be sent back to the client.
  • the present disclosure does not need to modify the extensive domain name or the second-level domain name, and only the minimum amount of configuration needs to be added to support the special back-to-source configuration or other special configurations. Because the added configuration amount is small and the implementation is easy, the special requirements of the domain name resolution may be satisfied.
  • Step S 301 -S 303 may refer to Step S 101 -S 103 in FIG. 1 , which is not repeatedly described herein.
  • the domain name resolution method further comprises: Step S 304 , where when a certain server cluster in the server group encounters a fault, the extensive domain name of the corresponding server group is re-resolved to another network protocol address.
  • www.163.com.bbb.aaa.com, news.163.com.bbb.aaa.com, and music.163.com.bbb.aaa.com may all use the server group with a network protocol address of 192.168.100.100.
  • the server group (192.168.100.100) used by the three portal domain name encounters a fault, only one domain name system configuration needs to be generated in the DNS server of the content delivery network to re-configure the extensive domain name *.bbb.aaa.com of the three portal domain names in the content delivery network from the network protocol address 192.168.100.100 of the original server group to the network protocol address of a new server group, such as 192.168.100.110.
  • the three portal domain names may be transferred to a new server cluster all at once in the content delivery network, instead of modifying the configurations corresponding to www.163.com.bbb.aaa.com, news.163.com.bbb.aaa.com, and music.163.bbb.aaa.com one by one.
  • the scheduling time of the server is shortened, and the configuration amount is decreased.
  • the present disclosure further provides an implementation method of a domain name resolution server 400 .
  • the server 400 comprises: a configuring module 401 , a sending/receiving module 402 , and a resolving module 403 .
  • the configuring module 401 is configured to configure a same extensive domain name for portal domain names using a same server group; the sending/receiving module 402 is connected to the configuring module 401 , and configured to receive a resolution request of the portal domain name, where the domain name requested by the client is resolved to the portal domain name of the content delivery network via a CNAME; the resolving module 403 is connected to the sending/receiving module 402 and configured to perform resolving on the portal domain name, and further uses the resolution result as the resolution result of the domain name requested by the client to be sent back to the client.
  • the operational process of the domain name resolution server 400 is as follows: for example, the content delivery network may include three server groups with portal domain names all using a network protocol address of 1.1.1.1, and the three portal domain names may be www.163.com.bbb.aaa.com, news.163.com.bbb.aaa.com, and music.163.com.bbb.aaa.com, respectively.
  • the configuring module 401 may configure a same extensive domain name *.bbb.aaa.com for the three portal domain names.
  • the client DNS server receives a resolution request of a domain name www.163.com sent from the client, the client DNS server resolves the domain name to the portal domain name www.163.com.bbb.aaa.com via a CNAME, and the client may request the domain name resolution server 400 to perform resolving on the portal domain name www.163.com.bbb.aaa.com.
  • the sending/receiving module 402 receives a resolution request of the portal domain name www.163.com.bbb.aa.com, and the resolution module 403 performs resolving on the portal domain name www.163.com.bbb.aaa.com, and uses the resolution result as the resolution result of the domain name www.163.com requested by the client to be sent back to the client.
  • Such one-layer CNAME record method based on extensive domain name may shorten the resolution time of the domain name system and decrease the resolution failure rate of the domain name system.
  • the specific client under attack may be easily and precisely found via the one-layer CNAME.
  • the domain name resolution server 400 may further comprise a scheduling module 404 .
  • the scheduling module 404 may be connected to the configuring module 401 and the resolving module 403 , respectively, and may be configured to, when a certain server cluster in the server group encounters a fault, re-solve the extensive domain name of the corresponding server group to another network protocol address.
  • the content delivery network When the server group used by the portal domain names www.163.com.bbb.aa.com, news.163.com.bbb.aaa.com, and music.163.com.bbb.aaa.com encounters a fault, the content delivery network generates a domain name system configuration to re-configure the extensive domain name *.bbb.aaa.com of the three portal domain names in the content delivery network from the network protocol address 1.1.1.1 of the original server group to the network protocol address (e.g., 1.1.1.2) of a new server group. That is, the extensive domain name *.bbb.aaa.com may be re-solved to 1.1.1.2.
  • the scheduling module 404 may, via only one domain name system configuration, transfer the three user domain names to the new server group all at once in the content delivery network, thereby shortening the server scheduling time and reducing the configuration amount.
  • the resolving module 403 comprises: a searching module 4031 and an extensive domain name resolving module 4032 .
  • the searching module 4031 is configured to search whether the portal domain name has a precisely matched A record, if the portal domain name has the precisely matched A record, the precisely matched A record may be used as the resolution result to be sent back to the client, and if not, the extensive domain name resolving module 4032 may be configured to perform resolving.
  • the precisely matched A record of the portal domain name comprises a network protocol address of a source station server corresponding to the domain name requested by the client, and a network protocol address of a custom server corresponding to the domain name requested by the client.
  • Such configuration may be realized by the configuring module 401 .
  • the searching module 4031 may, after search, use the network protocol address of the source station as the resolution result to be sent back to the client. For example, if the domain name www.163.com requested by the client needs to be back to the source station at the Beijing telecom area, only the A record of www.163.com.bbb.aaa.com needs to be configured at the Beijing telecom area. If the content delivery network receives the resolution request of www.163.com from the Beijing telecom, the searching module 4031 may use the network protocol address of the source station as the resolution result to be sent back to the client via the sending/receiving module 402 .
  • the searching module 4031 may, after search, use the network protocol address of the custom server as the resolution result to be sent back to the client. For example, if the domain name www.163.com requested by the client needs to use a special server at the Xinjiang telecom, then only the special server needs to be individually configured for www.163.com at the Xinjiang telecom area. If the content delivery network receives the resolution request of www.163.com at the Xinjiang telecom sent from the client, the searching module 4031 may use the network protocol address of the custom server as the resolution result to be sent back to the client via the sending/receiving module 402 .
  • the extensive domain name resolving module 4032 is configured to, when the searching module 4031 finds no precisely matched A record corresponding to the portal domain name, use the A record of the extensive domain name corresponding to the portal domain name as the resolution result after performing resolving on the portal domain name to be sent back to the client.
  • the domain name www.163.com requested by the client needs no special configuration at the Hunan telecom, and when the content delivery network receives the resolution request of www.163.com at the Hunan telecom sent from the client and the searching module 4031 finds no precisely matched A record of www.163.com.bbb.aaa.com, the extensive domain name resolving module 4032 uses the A record corresponding to the extensive domain name *.bbb.aaa.com as the resolution result after performing resolving on the portal domain name www.163.com.bbb.aaa.com. The resolution result is sent back to the client via the sending/receiving module 402 .
  • the present disclosure does not need to modify the extensive domain name or the second-level domain name, and only the minimum amount of configuration needs to be added to support the special back-to-source configuration or other special configurations.
  • the present disclosure provides a domain name resolution system, thereby implementing the domain name resolution method in embodiments illustrated in FIG. 1 .
  • the domain name resolution system provided by embodiments of the present disclosure comprises: a client DNS server 702 , and a domain name resolution system 703 corresponding to any embodiment illustrated from FIG. 4 to FIG. 6 .
  • the domain name requested by the client 701 is aliased to the portal domain name in the client DNS server 702 via a CNAME, where the portal domain name comprises the domain name requested by the client 701 as a prefix and a suffix of the extensive domain name as the suffix.
  • the client DNS server 702 receives the domain name resolution request sent from the client 701 , and resolves the domain name requested by the client 701 to a portal domain name of the content delivery network via a CNAME.
  • the domain name resolution server 703 is a domain name resolution sever corresponding to any embodiment illustrated in FIG. 4 - FIG. 6 .
  • the client DNS server 702 may request the domain name resolution server 703 to perform resolving on the portal domain name.
  • the domain name resolution server 703 configures the same extensive domain name for portal domain names using the same server group.
  • the domain name resolution server 703 receives the portal domain name resolution request, performs resolving on the portal domain name, and uses a resolution result as the resolution result of the domain name requested by the client to be sent back to the client 701 .
  • the client 701 sends a domain name resolution request of www.163.com to the client DNS server 702 .
  • the domain name www.163.com requested by the client 701 is aliased to the portal domain name www.163.com.bbb.aaa.com via a CNAME at the client DNS server 702 .
  • the client DNS server 702 resolves the domain name www.163.com requested by the client to the portal domain name www.163.com.bbb.aaa.com of the content delivery network via a CNAME.
  • the domain name resolution server 703 receives the resolution request of the portal domain name www.163.com.bbb.aa.com, and performs resolving on the portal domain name www.163.com.bbb.aaa.com. After resolution is fulfilled, the domain name resolution server 703 uses the resolution result as the resolution result of the domain name www.163.com sent from the client 701 to be sent back to the client 701 .
  • the extensive domain name *.bbb.aaa.com of the portal domain name www.163.com.bbb.aaa.com is configured in advance by the domain name resolution server 703 based on the server group used when resolving the portal domain name www.163.com.bbb.aaa.com. All portal domain names using the server group are configured with the same extensive domain name *.bbb.aaa.com.
  • Performing, by the domain name resolution server 703 , resolving on the portal domain name, and using the resolution result as the resolution result of the domain name requested by the client to be sent back to the client 701 may specifically comprise: searching whether the portal domain name has a precisely matched A record, if yes, the precisely matched A record is used as the resolution result to be sent back to the client 701 ; otherwise the A record of the extensive domain name corresponding to the portal domain name is used as the resolution result after performing resolving on the portal domain name to be sent back to the client 701 .
  • the device embodiments described above are for illustrative purposes only, and the units illustrated as separate parts may be or may not be physically separated.
  • the parts illustrated as units may be or may not be physical units. That is, the parts may be located in a same place, or distributed to a plurality of network units. A part of or all modules thereof may be selected to realize the object of solutions of the present disclosure based on the actual demand. Those ordinarily skilled in the relevant art may understand and implement the present disclosure without contributing creative labor.
  • each embodiment may be implemented using software and an essential universal hardware platform, or via the hardware.
  • the nature of the aforementioned technical solutions or the part of the aforementioned technical solutions that contributes to the existing technique may be embodied in a form of software products.
  • Such computer software product may be stored in a computer readable storage medium, such as ROM/RAM, magnetic disc, and optical disc, etc., that comprises a plurality of commands configured to allow a computing device (e.g., a personal computer, a server, or a network device, etc.) to execute each embodiment or methods described in some parts of the embodiments.
  • a computing device e.g., a personal computer, a server, or a network device, etc.

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)
US15/748,757 2017-02-19 2017-02-27 Domain name resolution system, domain name resolution server, and domain name resolution method Abandoned US20190036870A1 (en)

Applications Claiming Priority (3)

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

Publications (1)

Publication Number Publication Date
US20190036870A1 true US20190036870A1 (en) 2019-01-31

Family

ID=59622756

Family Applications (1)

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

Country Status (4)

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

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110708309A (zh) * 2019-09-29 2020-01-17 武汉极意网络科技有限公司 反爬虫系统及方法
CN112380072A (zh) * 2020-12-07 2021-02-19 中国建设银行股份有限公司 多数据中心访问方法及系统
CN112671860A (zh) * 2020-12-15 2021-04-16 杭州溪塔科技有限公司 用于kubernetes集群的服务访问方法、系统、电子设备及介质
CN113556411A (zh) * 2021-06-28 2021-10-26 深圳市高德信通信股份有限公司 一种cdn视频调度设备及方法
CN114448787A (zh) * 2021-12-27 2022-05-06 天翼云科技有限公司 一种cdn系统频道配置方法、装置、设备及存储介质

Families Citing this family (6)

* 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 腾讯科技（深圳）有限公司 别名管理方法、装置、服务器及存储介质
CN111629079B (zh) * 2020-04-29 2023-02-28 四川速宝网络科技有限公司 一种实现网络访问加速的系统及装置
CN112769976B (zh) * 2021-01-13 2023-10-24 网宿科技股份有限公司 一种域名解析方法及系统

Citations (3)

* 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
WO2014089872A1 (zh) * 2012-12-10 2014-06-19 中国科学院计算机网络信息中心 支持域名组dns解析的方法和系统
US20150188879A1 (en) * 2013-12-30 2015-07-02 Ideaware Inc. Apparatus for grouping servers, a method for grouping servers and a recording medium

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8533317B2 (en) * 2009-06-22 2013-09-10 Citrix Systems, Inc. Systems and methods for monitor distribution in a multi-core system
US20130198409A1 (en) * 2012-02-01 2013-08-01 Microsoft Corporation Efficient implementation of user-provided dns names
CN103501358B (zh) * 2013-09-18 2016-08-17 北京蓝汛通信技术有限责任公司 一种域名托管管理方法及装置
CN106209832A (zh) * 2016-07-08 2016-12-07 中国互联网络信息中心 基于ns记录转移授权缓解域名权威记录劫持影响的方法

Patent Citations (3)

* 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
WO2014089872A1 (zh) * 2012-12-10 2014-06-19 中国科学院计算机网络信息中心 支持域名组dns解析的方法和系统
US20150188879A1 (en) * 2013-12-30 2015-07-02 Ideaware Inc. Apparatus for grouping servers, a method for grouping servers and a recording medium

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110708309A (zh) * 2019-09-29 2020-01-17 武汉极意网络科技有限公司 反爬虫系统及方法
CN112380072A (zh) * 2020-12-07 2021-02-19 中国建设银行股份有限公司 多数据中心访问方法及系统
CN112671860A (zh) * 2020-12-15 2021-04-16 杭州溪塔科技有限公司 用于kubernetes集群的服务访问方法、系统、电子设备及介质
CN113556411A (zh) * 2021-06-28 2021-10-26 深圳市高德信通信股份有限公司 一种cdn视频调度设备及方法
CN114448787A (zh) * 2021-12-27 2022-05-06 天翼云科技有限公司 一种cdn系统频道配置方法、装置、设备及存储介质

Also Published As

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

Similar Documents

Publication Publication Date Title
US20190036870A1 (en) Domain name resolution system, domain name resolution server, and domain name resolution method
US10506033B2 (en) Distributed global load-balancing system for software-defined data centers
CN111245972B (zh) 一种域名解析方法、装置、介质及设备
US20070220302A1 (en) Session failover management in a high-availability server cluster environment
US9712422B2 (en) Selection of service nodes for provision of services
JP6967615B2 (ja) 分散型検索及びインデックスの更新方法、システム、サーバー並びにコンピューター機器
US20160373405A1 (en) Managing dynamic ip address assignments
US9525648B2 (en) Method for acquiring physical address of virtual machine
US9742731B2 (en) Geolocation via internet protocol
US20130346576A1 (en) Cloud server for managing hostnames and ip addresses, and management method for the cloud server
US9319377B2 (en) Auto-split DNS
WO2012065641A1 (en) Dns server arrangement and method
US20230022183A1 (en) Systems and methods for processing requests for content of a content distribution network
CN103458013A (zh) 一种流媒体服务器集群负载均衡系统及均衡方法
US20130067540A1 (en) Techniques for achieving storage and network isolation in a cloud storage environment
CN104935653A (zh) 一种访问热点资源的旁路缓存方法和装置
CN104580542A (zh) Dns系统的智能解析方法
CN112583952A (zh) 重定向调度处理方法、装置、系统及相关设备、存储介质
CN112866432A (zh) 一种域名解析方法、系统、电子设备及存储介质
US20130297825A1 (en) Method, switch, and system for processing a message
WO2019067027A1 (en) DYNAMIC ASSOCIATION AND LOAD DETERMINATION IN A CONTENT BROADCAST NETWORK (CDN)
CN108494870B (zh) 基于cdn的动态数据加载方法及装置
CN106534390B (zh) 权威域名系统服务器数据的存储和管理方法及系统
US11706189B2 (en) Domain management and synchronization system
US8964743B2 (en) Methods and arrangements in a packet switched network

Legal Events

Date Code Title Description
AS Assignment

Owner name: WANGSU SCIENCE & TECHNOLOGY CO., LTD., CHINA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WU, XIAOYING;WU, ZHENYONG;REEL/FRAME:044767/0256

Effective date: 20180130

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION