[go: up one dir, main page]

WO2018112944A1 - Procédé et appareil de résolution de nom de domaine - Google Patents

Procédé et appareil de résolution de nom de domaine Download PDF

Info

Publication number
WO2018112944A1
WO2018112944A1 PCT/CN2016/111855 CN2016111855W WO2018112944A1 WO 2018112944 A1 WO2018112944 A1 WO 2018112944A1 CN 2016111855 W CN2016111855 W CN 2016111855W WO 2018112944 A1 WO2018112944 A1 WO 2018112944A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
domain name
user
record
resolution
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.)
Ceased
Application number
PCT/CN2016/111855
Other languages
English (en)
Chinese (zh)
Inventor
朱磊
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.)
Cloudminds Shenzhen Robotics Systems Co Ltd
Original Assignee
Cloudminds Shenzhen Robotics Systems 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 Cloudminds Shenzhen Robotics Systems Co Ltd filed Critical Cloudminds Shenzhen Robotics Systems Co Ltd
Priority to CN201680002953.9A priority Critical patent/CN106797410A/zh
Priority to PCT/CN2016/111855 priority patent/WO2018112944A1/fr
Publication of WO2018112944A1 publication Critical patent/WO2018112944A1/fr
Anticipated expiration legal-status Critical
Ceased 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]

Definitions

  • the present disclosure relates to the field of network technologies, and in particular, to a domain name resolution method and apparatus.
  • DNS Domain Name System
  • IP Internet Protocol
  • DNS Domain Name System
  • IP Internet Protocol
  • the process of obtaining the IP address corresponding to the domain name through the domain name is called domain name resolution (or host name resolution).
  • domain name resolution or host name resolution
  • the majority of the local DNS uses the default DNS address assigned by the operator, such as home broadband, corporate broadband, etc.
  • These local DNS can implement non-boot domain names (the boot domain name refers to a special domain name that needs to use the private network service).
  • Recursive query function in the existing DNS resolution process, when multiple users perform recursive query for the same domain name, the local DNS only performs DNS query for the first user who queries the domain name, so the local DNS cache The content is only the result of this query, and does not support multi-user differentiated queries.
  • the disclosure provides a domain name resolution method and apparatus.
  • the present disclosure provides a domain name resolution method, the method comprising:
  • the access request includes an IP address of the first user and a first domain name to be accessed, and the first user is any one of multiple users accessing the first domain name user;
  • the present disclosure provides a domain name resolution apparatus, where the apparatus includes:
  • a request receiving module configured to receive an access request sent by the first user, where the access request includes an IP address of the first user and a first domain name to be accessed, where the first user accesses the first domain name Any of the users;
  • a request sending module configured to send the IP address of the first user and the first domain name to a domain name resolution device
  • An address determining module configured to acquire, by the domain name resolution device, a first IP address of the first domain name, where the first IP address is determined according to a network attribute of an IP address of the first user;
  • a record caching module configured to cache a first parsing record for the first user according to the first user's IP address, the first domain name, and the first IP address;
  • An address sending module configured to send the first IP address to the first user.
  • the present disclosure provides a computer program product comprising a computer program executable by a programmable device, the computer program having when executed by the programmable device The code part used for the above method.
  • the present disclosure provides a non-transitory computer readable storage medium including one or more programs for the one or more programs In the above method.
  • the present disclosure provides an electronic device, the electronic device including:
  • One or more processors for executing a program in the non-transitory computer readable storage medium.
  • the domain name resolution method and apparatus receives an IP address sent by a first user and a first domain name to be accessed, and the first user is any one of a plurality of users accessing the first domain name. Transmitting the first user's Internet Protocol IP address and the first domain name to the domain name resolution device, and then obtaining, from the domain name resolution device, the first IP address of the first domain name determined according to the network attribute of the first user's IP address. The address, and then buffering the first parsing record for the first user according to the IP address of the first user, the first domain name, and the first IP address, and finally sending the first IP address to the first user.
  • the present disclosure is capable of generating a source of different users based on a request for domain name resolution
  • the IP address, for the first domain name returns the domain name resolution result most suitable for the user, and implements multi-user differentiated query for domain name resolution.
  • FIG. 1 is a flowchart of a domain name resolution method according to an exemplary embodiment
  • FIG. 2 is a schematic diagram of a domain name resolution method according to an exemplary embodiment
  • FIG. 3 is a schematic diagram of another domain name resolution method according to an exemplary embodiment.
  • FIG. 4 is a flowchart of another method for domain name resolution according to an exemplary embodiment
  • FIG. 5 is a flowchart of a cache parsing recording method according to the embodiment shown in FIG. 1;
  • FIG. 6 is a flowchart of still another method for domain name resolution according to an exemplary embodiment
  • FIG. 7 is a flowchart of a domain name resolution method according to another exemplary embodiment.
  • FIG. 8 is a flowchart of a method for acquiring a domain name IP address according to the embodiment shown in FIG. 1;
  • FIG. 9 is a block diagram of a domain name resolution apparatus according to an exemplary embodiment.
  • FIG. 10 is a block diagram of another domain name resolution apparatus according to an exemplary embodiment.
  • FIG. 11 is a block diagram of still another domain name resolution apparatus according to an exemplary embodiment
  • FIG. 12 is a block diagram of still another domain name resolution apparatus according to an exemplary embodiment
  • Figure 13 is a block diagram of still another address determining module according to the embodiment shown in Figure 9;
  • FIG. 14 is a block diagram of a domain name resolution apparatus according to another exemplary embodiment.
  • FIG. 15 is a block diagram of another domain name resolution apparatus according to another exemplary embodiment.
  • the application scenario may include at least one user, the at least one user is not limited to an individual user or an enterprise user, and the application scenario further includes a domain name resolution.
  • Device and domain name resolution device wherein the domain name resolution device can be understood as an intelligent DNS device, which supports access to multiple users
  • the request is received, the (for the domain name resolution device) is forwarded, the record cache is cached, and the query is performed.
  • the domain name resolution device is configured to perform domain name resolution according to the access request forwarded by the domain name resolution device, and returns a resolution record.
  • FIG. 1 is a flowchart of a domain name resolution method according to an exemplary embodiment. As shown in FIG. 1 , the domain name resolution method may include the following steps.
  • Step 101 Receive an access request sent by the first user, where the access request includes an IP address of the first user and a first domain name to be accessed, where the first user is any one of multiple users accessing the first domain name. .
  • the first domain name may include a boot domain name, a non-boot domain name, or an alias domain name
  • the IP address of the first user may include an IP address in the form of an A record or an IP address in an AAAA record format.
  • Step 102 Send the IP address of the first user and the first domain name to the domain name resolution device.
  • the first domain name is a non-boot domain name
  • the non-boot domain name can be recursively resolved. Therefore, the domain name resolution device can be a domain name resolution server. Therefore, the step 102 can include: the IP address of the first user and the first The domain name is sent to the domain name resolution server.
  • the domain name resolution server is generally referred to as a DNS server.
  • the domain name resolution server is an HTTP DNS (English: Hyper Text Transfer Protocol Domain Name System) server, or an HTTPS DNS ( English: Hyper Text Transfer Protocol over Secure Socket Layer Domain Name System, Chinese: Secure Hypertext Transfer Protocol Domain Name System) Server, or EDNS (English: Extension Mechanisms for Domain Name System, Chinese: Extended Domain Name System) server.
  • HTTP DNS Hyper Text Transfer Protocol Domain Name System
  • HTTPS DNS English: Hyper Text Transfer Protocol over Secure Socket Layer Domain Name System
  • Chinese Secure Hypertext Transfer Protocol Domain Name System
  • EDNS English: Extension Mechanisms for Domain Name System, Chinese: Extended Domain Name System
  • the step 102 may include: sending the IP address of the first user and the first domain name to a management center of a private network corresponding to the first domain name, where the private network includes multiple Access points.
  • Step 103 Obtain a first IP address of the first domain name from the domain name resolution device, where the first IP address is determined according to a network attribute of an IP address of the first user.
  • the first IP address may also include an IP address in the form of an A record or an IP address in the form of an AAAA record.
  • the first domain name is a non-boot domain name.
  • the step 103 may include: receiving, by the domain name resolution server, the first IP address, where the first IP address belongs to the domain name resolution server according to the IP address of the first user. At least one of a geographic area and a network operator determines the first domain name IP address.
  • the step 103 may further include: receiving, by the domain name resolution server, the first IP address, where the first IP address belongs to the domain name resolution server according to the IP address of the first user. a geographical area, a network operator to which the IP address of the first user belongs, a user in the management center, and an access point IP address mapping record determined by at least one of the access point for accessing the private network IP address.
  • the boot domain name may be a domain name of a special ICP (Internet Content Provider) that needs to use a dedicated network service.
  • the private network may include a CDN (Content Delivery Network) or an AND (Application Delivery Network) that performs access guidance and control for a specified ICP.
  • a mapping relationship between a plurality of different users and an IP address of an access point within the private network may be recorded in a management center of the private network.
  • the mapping relationship between different users and the IP addresses of the access points in the private network may be mappings from different geographic regions and/or different network operators and different access points; or, may be some A mapping relationship between a single user's IP address and a network access point.
  • the IP address applicable to the ICP domain name applicable to the user may be directly determined according to the foregoing mapping relationship.
  • Step 104 Cache the first parsing record for the first user according to the IP address of the first user, the first domain name, and the first IP address.
  • the first parsing record may include: a combination of the first user's IP address, the first domain name, and the first IP address; or the first user's IP address, the first domain name, and the user IP address. The combination of the three.
  • the step 104 may include: the first user's IP address, the The combination of the first domain name and the first IP address is cached as the first parsing record.
  • the first resolution record from the domain name resolution device can be cached in the form of a key/value pair.
  • the key may include: a combination of the IP address of the first user and the first domain name or a combination of a user IP address segment and the first domain name, and the value may be the first IP address.
  • Step 105 Send the first IP address to the first user.
  • the above steps 101-105 can be performed by the domain name resolution device described in the foregoing application scenario, and the first user can be a user registered in the domain name resolution device.
  • the domain name resolution service may not be provided by the access request initiated by the user.
  • FIG. 2 is a schematic diagram of a domain name resolution method according to an exemplary embodiment.
  • the user 1 to the user 3 access the domain name resolution device.
  • a domain name initiates an access request.
  • the IP address of User 1 is 1.1.1.1
  • the IP address of User 2 is 2.2.2.2
  • User 3 is an unregistered user
  • the first domain to be accessed by User 1 to User 3 is www.exmaple.com.
  • the parsing device After receiving the access request from User 1 to User 3, the parsing device sends a resolution request including the IP address of the user 1 and the domain name www.exmaple.com to the domain name resolution server, and includes the IP address and domain name of the user 2 www.exmaple.
  • the domain name resolution server determines the IP address 3.3.3.3 of the domain name www.exmaple.com suitable for user 1 according to user 1's IP address 1.1.1.1 and domain name www.exmaple.com, and According to User 2's IP address 2.2.2.2 and domain name www.exmaple.com, determine the IP address 4.4.4.4 for User 2's domain name www.exmaple.com; the domain name resolution server will be suitable for User 1's domain name www.exmaple.com IP Address 3.3.3.3 and the IP address 4.4.4.4 of the domain name www.exmaple.com suitable for User 2 are sent to the domain name resolution device, and the domain name resolution device caches the received IP address with the corresponding user and the domain name www.exmaple.com.
  • the cache can be as shown in Table 1. Key-value pairs in the form:
  • Timeout (seconds) 1.1.1.1_www.exmaple.com 3.3.3.3 120 2.2.2.2_www.exmaple.com 4.4.4.4 120
  • the timeout period is used to indicate the effective time of each parsing record.
  • FIG. 3 is a schematic diagram of another domain name resolution method according to an exemplary embodiment.
  • the enterprise 1 to the enterprise 3 access the domain name resolution device.
  • a domain name initiates an access request.
  • the IP1 address of enterprise 1 is: 1.1.1.1
  • the IP address of enterprise 2 is 2.2.2.2
  • the enterprise 3 is an unregistered user
  • the first domain name to be accessed by enterprise 1 to enterprise 3 is www.exmaple.com.
  • the analysis device received the interview from Enterprise 1 to Enterprise 3 After requesting the request, send a resolution request containing the IP address of the enterprise 1 and the domain name www.exmaple.com to the management center of the private network accessed by the domain name www.exmaple.com, and include the IP address and domain name of the enterprise 2 www.exmaple .com resolves the request and ignores the request of enterprise 3; the management center of the private network determines the suitable enterprise according to the IP address 1.1.1.1 of enterprise 1 and the mapping relationship between the IP address of the enterprise 1 and the access point recorded in the management center.
  • the IP address IP1 of the access point of the private network of 1 and the mapping relationship between the IP address 2.2.2.2 of the enterprise 2 and the IP address of the enterprise 2 recorded in the management center and the access point are determined to be suitable for the enterprise 2
  • the IP address IP2 of the access point of the network; Enterprise 1 and Enterprise 2 can access the first domain name www.exmaple.com through the IP1 and IP2 respectively.
  • the management center of the private network will be suitable for the IP address IP1 of the private network access point where the domain name www.exmaple.com of the enterprise 1 is located and the IP address IP2 of the private network access point where the domain name of the enterprise 2 is www.exmaple.com.
  • the domain name resolution device sends the IP address of the received private network access point to the corresponding enterprise and the domain name www.exmaple.com, where the cache can be in the form of a key-value pair as shown in Table 2:
  • the domain name resolution method receives an IP address sent by a first user and a first domain name to be accessed, and the first user is any one of multiple users accessing the first domain name. Transmitting the first user's Internet Protocol IP address and the first domain name to the domain name resolution device; obtaining, from the domain name resolution device, the first IP address of the first domain name determined according to the network attribute of the first user's IP address And caching the first parsing record for the first user according to the first user's IP address, the first domain name, and the first IP address; and sending the first IP address to the first user.
  • the disclosure can return the domain name resolution result that is most suitable for the user, and implement the multi-user differentiated query of the domain name resolution.
  • FIG. 4 is a flowchart of another method for domain name resolution according to an exemplary embodiment. As shown in FIG. 4, when the first resolution record includes the IP address of the first user, the first domain name, and the first When the IP address is combined, the domain name resolution method may further include the following steps.
  • step 106 when receiving the access request sent by the first user again, it is determined whether the domain name included in the resent access request is the same as the first domain name in the first resolution record.
  • step 107 when it is determined that the domain name included in the resent access request is the same as the first domain name in the first parsing record, the first IP address is obtained according to the cached first parsing record.
  • step 108 the first IP address is sent to the first user.
  • the first IP address corresponding to the domain name may be searched in the first parsed record of the cache according to the IP address of the user, without re-locating the domain name.
  • the parsing device sends a parsing request.
  • FIG. 5 is a flowchart of still another cache parsing recording method according to the embodiment shown in FIG. 1.
  • the step 104 may include the following steps.
  • Step 1041 Determine a user IP address segment to which the IP address of the first user belongs.
  • the range of the user IP address segment may be determined according to the same geographical area, or the IP address of multiple users of the same network operator or the same local area network (such as multiple users in an enterprise).
  • the range of the IP address segment may also be customized within the domain name resolution device according to the user's requirement for the size of the address segment.
  • the IP address segment can be defined as a 24-bit mask of IPv4 according to the needs of the user.
  • Step 1042 cache the combination of the first user's IP address, the first domain name, and the user IP address segment as the first resolution record.
  • FIG. 6 is a flowchart of still another method for domain name resolution according to an exemplary embodiment. As shown in FIG. 6, when the first resolution record includes an IP address of the first user, the first domain name, and the user IP. When the combination of the three address segments, the domain name resolution method may further include the following steps.
  • Step 109 When receiving the access request sent by the second user, determine whether the domain name included in the access request sent by the second user is the same as the first domain name in the first resolution record.
  • step 110 is continued.
  • Step 110 Determine whether the IP address of the second user belongs to the user IP address segment.
  • the user IP address segment may be acquired, and step 111 is continued.
  • Step 111 Acquire the first IP address according to the cached first parsing record.
  • the first IP address can be obtained according to the user IP address segment.
  • Step 112 Send the first IP address to the second user, where the second user is the same or different user as the first user.
  • a parsing record can cache a parsing record so that users belonging to the same IP address segment share a parsing record.
  • the embodiment described in FIG. 2 is taken as an example, and the user IP address segment to which the user 1 and the user 2 belong can be determined during the buffering, so that the parsing records cached for the user 1 and the user 2 can be represented as Table 3.
  • Timeout (seconds) 1.1.1.0/24_www.exmaple.com 3.3.3.3 120 2.2.2.0/24_www.exmaple.com 4.4.4.4 120
  • 1.1.1.0/24 indicates that the IP address segment of the IP from 1.1.1.0 to 1.1.1.24, when the user whose IP address is in this range requests to access www.exmaple.com again, the DNS query is no longer performed for the user.
  • the cache of the record is parsed, and the IP address of 3.3.3.3 is obtained directly from the record in Table 3 to the user.
  • 2.2.2.0/24 is the same as 1.1.1.0/24, and the above scheme is also applicable to the case of guiding the domain name.
  • the method is the same as the method shown in Table 3, and will not be described again.
  • the IP address segment where the IP address of the user is located may be directly in the first parsed record cached. Find the first IP address corresponding to the domain name without resending the resolution request to the domain name resolution device.
  • FIG. 7 is a flowchart of a domain name resolution method according to another exemplary embodiment. As shown in FIG. 7, the method may further include the following steps.
  • Step 113 Set a timeout period for the first parsing record when the first parsing record is cached.
  • the timeout period of the first parsing record may also be set, and the timeout period may be marked as TTL (Time to life).
  • Step 114 When the first parsing record cache duration exceeds the timeout period, the first solution is obtained. Analysis of record deletion.
  • FIG. 8 is a flowchart of a method for acquiring a domain name IP address according to the embodiment shown in FIG. 1. As shown in FIG. 8, the step 103 may include the following steps.
  • Step 1031 Obtain a second domain name determined according to the first domain name from the domain name resolution device, where the second domain name is an alias domain name of the first domain name.
  • step 1032 can be performed.
  • Step 1032 Send the IP address of the first user and the second domain name to the domain name resolution device.
  • Step 1033 Obtain an IP address of the second domain name from the domain name resolution device, where the IP address of the second domain name is determined according to a network attribute of the IP address of the first user.
  • Step 1034 Determine the IP address of the second domain name as the first IP address.
  • the IP address corresponding to the first domain name can be determined by the domain name resolution of the alias domain name.
  • the method for domain name resolution receives an IP address sent by a first user and a first domain name to be accessed, and the first user is any one of multiple users accessing the first domain name.
  • a user sending the first user's Internet Protocol IP address and the first domain name to the domain name resolution device; and obtaining, from the domain name resolution device, the first IP address of the first domain name determined according to the network attribute of the first user's IP address Addressing: storing, by the first user, an IP address, the first domain name, and the first IP address, a first parsing record for the first user; sending the first IP address to the first user.
  • the disclosure can report the recursive resolution or authoritative analysis result most suitable for the user according to the source IP address of the different users that issue the boot domain name, the non-boot domain name or the alias record, and implement the recursive resolution and authoritative analysis of the domain name. Multi-user differentiated queries.
  • FIG. 9 is a block diagram of a domain name resolution apparatus, which may be used to perform the method described in FIG. 1 , which may be implemented as a server by software, hardware, or a combination of both, according to an exemplary embodiment.
  • the server may be the server described in the above application scenario.
  • the apparatus 9000 can include:
  • the request receiving module 9010 is configured to receive an access request sent by the first user, where the access request includes an IP address of the first user and a first domain name to be accessed, where the first user is a plurality of users accessing the first domain name. Any user.
  • the request sending module 9020 is configured to send the IP address of the first user and the first domain name to the domain name resolution device.
  • the address determining module 9030 is configured to obtain, by the domain name resolution device, a first IP address of the first domain name, where the first IP address is determined according to a network attribute of an IP address of the first user.
  • the record cache module 9040 is configured to cache the first parsing record for the first user according to the first user's IP address, the first domain name, and the first IP address.
  • the address sending module 9050 is configured to send the first IP address to the first user.
  • the record caching module 9040 can be used to:
  • the combination of the first user's IP address, the first domain name, and the first IP address is cached as the first analysis record.
  • FIG. 10 is a block diagram of another domain name resolution apparatus, which may be used to perform the method described in FIG. 4, according to an exemplary embodiment.
  • the apparatus 9000 may further include: a domain name identification module 9060 and an address obtaining module 9070.
  • the domain name identification module 9060 is configured to determine, when receiving the access request sent by the first user, whether the domain name included in the resent access request is the same as the first domain name in the first resolution record.
  • the address obtaining module 9070 is configured to obtain the first IP address according to the cached first parsing record when it is determined that the domain name included in the resent access request is the same as the first domain name in the first parsing record.
  • the address sending module 9050 is configured to send the first IP address to the first user.
  • the record caching module 9040 is further configured to:
  • the combination of the first user's IP address, the first domain name, and the user IP address segment is cached as the first analysis record.
  • FIG. 11 is a block diagram of still another domain name resolution apparatus, which may be used to perform the method described in FIG. 6 according to an exemplary embodiment.
  • the device 9000 may further include: a domain name identification module 9060, an address segment determining module 9080, and an address obtaining module 9070.
  • the domain name identification module 9060 is further configured to: when receiving the access request sent by the second user, determine whether the domain name included in the access request sent by the second user is the same as the first domain name in the first resolution record.
  • the address segment determining module 9080 is configured to determine a domain included in the resent access request When the name is the same as the first domain name in the first parsing record, it is determined whether the IP address of the second user belongs to the user IP address segment.
  • the address obtaining module 9070 is further configured to: when determining whether the IP address of the second user belongs to the user IP address segment, obtain the first IP address according to the cached first parsing record.
  • the address sending module 9050 is further configured to send the first IP address to the second user, where the second user is the same user or a different user.
  • FIG. 12 is a block diagram of still another domain name resolution apparatus, which may be used to perform the method described in FIG. 7, according to an exemplary embodiment.
  • the device 9000 may further include:
  • the timeout setting module 9090 is configured to set a timeout period for the first parsing record when the first parsing record is cached.
  • the record deletion module 9100 is configured to delete the first parsing record when the first parsing record cache duration exceeds the timeout period.
  • the first domain name is a non-boot domain name
  • the request sending module 9020 is configured to:
  • the domain name resolution server is an HTTP DNS server, or an HTTPS DNS server, or an EDNS server.
  • the address determining module 9030 is configured to:
  • the domain name resolution server Receiving, by the domain name resolution server, the first IP address, where the first IP address is determined by the domain name resolution server according to at least one of a geographical area and a network operator to which the IP address of the first user belongs address.
  • the first domain name is a boot domain name
  • the request sending module 9020 is configured to:
  • the first user's IP address and the first domain name are sent to a management center of a private network corresponding to the first domain name, and the private network includes a plurality of access points.
  • the address determining module 9030 is configured to:
  • the first IP address is a network operator to which the domain name resolution server belongs according to the IP address of the first user, a network operator to which the IP address of the first user belongs, and the management The IP address of the access point used to access the private network determined by at least one of the user and the access point IP address mapping record in the center.
  • the IP address of the first user and the first IP address include an IP address in the form of an A record, or an IP address in an AAAA record format.
  • FIG. 13 is a block diagram of yet another address determination module, which may be used to perform the method described in FIG. 8, in accordance with the embodiment of FIG.
  • the address determining module 9030 may include:
  • the alias domain name obtaining sub-module 9031 is configured to obtain, from the domain name resolution device, a second domain name determined according to the first domain name, where the second domain name is an alias domain name of the first domain name.
  • the domain name sending submodule 9032 is configured to send the IP address of the first user and the second domain name to the domain name resolution device.
  • the address obtaining sub-module 9033 is configured to obtain an IP address of the second domain name from the domain name resolution device, where the IP address of the second domain name is determined according to a network attribute of the IP address of the first user.
  • the address determining submodule 9034 is configured to determine the IP address of the second domain name as the first IP address.
  • the apparatus for domain name resolution receives an IP address sent by a first user and a first domain name to be accessed, and the first user is any one of multiple users accessing the first domain name.
  • a user sending the first user's Internet Protocol IP address and the first domain name to the domain name resolution device; and obtaining, from the domain name resolution device, the first IP address of the first domain name determined according to the network attribute of the first user's IP address Addressing: storing, by the first user, an IP address, the first domain name, and the first IP address, a first parsing record for the first user; sending the first IP address to the first user.
  • the disclosure can return the result of recursive resolution or authoritative analysis that is most suitable for the user according to the source IP address of the different user that issues the boot domain name or the non-boot domain name resolution request, and implement the recursive resolution and authoritative analysis of the domain name. Multi-user differentiated queries.
  • the present disclosure also provides a computer program product comprising a computer program executable by a programmable device, the computer program having any of Figures 1 through 10 when executed by the programmable device The code portion of the method shown.
  • the present disclosure also provides a non-transitory computer readable storage medium including one or more programs for use in any of FIGS. 1 through 10 method.
  • the present disclosure also provides an electronic device, the electronic device comprising:
  • One or more processors for executing a program in the non-transitory computer readable storage medium.
  • FIG. 14 is a block diagram of a domain name resolution apparatus according to another exemplary embodiment, the domain The name resolution device 1400 can be an electronic device, such as the smart DNS device described in the aforementioned application scenario. As shown in FIG. 14, the apparatus 1400 can include a processor 1401, a memory 1402, a multimedia component 1403, an input/output (I/O) interface 1404, and a communication component 1405.
  • a processor 1401 a memory 1402
  • multimedia component 1403 multimedia component 1403
  • I/O input/output
  • the processor 1401 is configured to control the overall operation of the apparatus 1400 to complete all or part of the steps of the method shown in any of the foregoing FIGS. 1 to 10.
  • Memory 1402 is used to store various types of data to support operations at the device 1400, such as may include instructions for any application or method operating on the device 1400, as well as application related data, such as Contact data, sent and received messages, pictures, audio, video, and more.
  • the memory 1402 can be implemented by any type of volatile or non-volatile storage terminal device or a combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read only memory.
  • SRAM Static Random Access Memory
  • the multimedia component 1403 can include a screen and an audio component.
  • the screen may be, for example, a touch screen, and the audio component is used to output and/or input an audio signal.
  • the audio component can include a microphone for receiving an external audio signal.
  • the received audio signal may be further stored in memory 1402 or transmitted via communication component 1405.
  • the audio component also includes at least one speaker for outputting an audio signal.
  • the I/O interface 1404 provides an interface between the processor 1401 and other interface modules, such as a keyboard, a mouse, a button, and the like. These buttons can be virtual buttons or physical buttons.
  • Communication component 1405 is used for wired or wireless communication between the device 1400 and other terminal devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G or 4G, or a combination of one or more of them, so the corresponding communication component 1405 can include: Wi-Fi module, Bluetooth module, NFC module.
  • the device 1400 may be configured by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), and digital signal processing terminals (Digital).
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • Digital Digital
  • DSPD Signal Processing Device
  • PLD Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • a controller a microcontroller, a microprocessor or other electronic component is implemented for performing the above-described monitoring method of the terminal device.
  • non-transitory computer readable storage medium comprising instructions, such as a memory 1402 comprising instructions executable by processor 1401 of apparatus 1400 to perform the terminal device described above Monitoring method.
  • the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage terminal device.
  • FIG. 15 is a block diagram of another domain name resolution apparatus according to another exemplary embodiment.
  • the apparatus 1500 may be a server, which may be a server cluster composed of several servers, or may be a cloud computing service center.
  • the apparatus 1500 includes a processor 1501, a memory 1502, an I/O interface 1503, and a network interface 1504, wherein the memory 1502 can be used to store instructions executable by the processor 1501, and the processor 1502 can execute the instructions to The method shown in any of the above FIGS. 1 to 10 is performed.

Landscapes

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

Abstract

La présente invention concerne un procédé et un appareil de résolution de nom de domaine. Le procédé consiste à : recevoir une adresse de protocole Internet (IP) envoyée par un premier utilisateur, ainsi qu'un premier nom de domaine devant faire l'objet d'un accès, le premier utilisateur étant l'un quelconque d'une pluralité d'utilisateurs accédant au premier nom de domaine ; envoyer l'adresse IP du premier utilisateur et le premier nom de domaine à un dispositif de résolution de nom de domaine ; obtenir une première adresse IP du premier nom de domaine à partir du dispositif de résolution de nom de domaine, la première adresse IP étant déterminée en fonction des attributs de réseau de l'adresse IP du premier utilisateur ; mettre en cache un premier enregistrement de résolution pour le premier utilisateur en fonction de l'adresse IP du premier utilisateur, du premier nom de domaine et de la première adresse IP ; et envoyer la première adresse IP au premier utilisateur. Au moyen du procédé et de l'appareil, des résultats de résolution de nom de domaine meilleurs pour l'utilisateur peuvent être renvoyés pour le premier nom de domaine en fonction d'adresses IP sources de différents utilisateurs envoyant une demande de nom de domaine, et par conséquent, une demande différentielle multiutilisateur de résolution de nom de domaine peut être satisfaite.
PCT/CN2016/111855 2016-12-23 2016-12-23 Procédé et appareil de résolution de nom de domaine Ceased WO2018112944A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201680002953.9A CN106797410A (zh) 2016-12-23 2016-12-23 域名解析方法和装置
PCT/CN2016/111855 WO2018112944A1 (fr) 2016-12-23 2016-12-23 Procédé et appareil de résolution de nom de domaine

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/111855 WO2018112944A1 (fr) 2016-12-23 2016-12-23 Procédé et appareil de résolution de nom de domaine

Publications (1)

Publication Number Publication Date
WO2018112944A1 true WO2018112944A1 (fr) 2018-06-28

Family

ID=58952248

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/111855 Ceased WO2018112944A1 (fr) 2016-12-23 2016-12-23 Procédé et appareil de résolution de nom de domaine

Country Status (2)

Country Link
CN (1) CN106797410A (fr)
WO (1) WO2018112944A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112217915A (zh) * 2020-09-28 2021-01-12 中国工商银行股份有限公司 传统环境互联网接入区适云改造方法及装置
CN113364895A (zh) * 2021-06-29 2021-09-07 中国电信股份有限公司 用于资源调度的方法、装置、电子设备及存储介质
CN114500471A (zh) * 2022-03-28 2022-05-13 北京天维信通科技有限公司 Ip地址列表分析维护方法、系统、智能终端及存储介质
CN114553826A (zh) * 2022-01-11 2022-05-27 阿里巴巴（中国）有限公司 域名管理方法、装置、电子设备、介质及程序产品
CN115189940A (zh) * 2022-07-08 2022-10-14 深圳依时货拉拉科技有限公司 一种域名解析方法、装置、计算机设备和计算机可读存储介质
CN118233428A (zh) * 2024-05-22 2024-06-21 中国电信股份有限公司 域名访问方法、装置及相关设备
CN119011380A (zh) * 2024-10-24 2024-11-22 天翼视联科技有限公司 一种dns解析监控方法、装置、电子装置和存储介质

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107360269A (zh) * 2017-07-21 2017-11-17 中国移动通信集团江苏有限公司 域名解析系统优化方法、装置、设备和存储介质
CN111213348B (zh) * 2017-10-11 2021-07-16 华为技术有限公司 数据中心系统中域名解析的方法、装置和系统
CN109756584B (zh) * 2017-11-07 2022-01-18 中国电信股份有限公司 域名解析方法、域名解析装置及计算机可读存储介质
CN108418881A (zh) * 2018-03-05 2018-08-17 北京云端智度科技有限公司 一种cdn网络内容分发系统及方法
WO2019237288A1 (fr) * 2018-06-13 2019-12-19 深圳前海达闼云端智能科技有限公司 Procédé et appareil de résolution de nom de domaine, et support d'informations lisible par ordinateur
CN110636374A (zh) * 2018-06-22 2019-12-31 北京京东尚科信息技术有限公司 用于查找信息的方法和装置
CN108449283A (zh) * 2018-06-22 2018-08-24 郑州云海信息技术有限公司 基于负载均衡的域名解析方法、系统、设备及存储介质
CN109561082A (zh) * 2018-11-16 2019-04-02 国网思极网安科技（北京）有限公司 一种区分dns用户的方法和系统
CN109618016B (zh) * 2018-12-10 2022-02-22 深圳市网心科技有限公司 一种dns请求的发送处理方法、相关方法及相关装置
CN111355819B (zh) * 2018-12-24 2022-11-11 北京华为数字技术有限公司 解析域名的方法和网络设备
CN109618024A (zh) * 2019-02-01 2019-04-12 网宿科技股份有限公司 一种基于http的域名解析方法和系统
CN109769043A (zh) * 2019-03-14 2019-05-17 中国工商银行股份有限公司 域名解析方法、装置及系统
CN110602270B (zh) * 2019-11-01 2022-10-14 北京博睿宏远数据科技股份有限公司 域名解析方法、装置、计算机设备及存储介质
CN112866424A (zh) * 2019-11-28 2021-05-28 华为技术有限公司 域名查询方法以及相关设备
CN111064821A (zh) * 2019-12-23 2020-04-24 北京达佳互联信息技术有限公司 边缘节点的ip地址的确定方法和装置
CN111405079A (zh) * 2020-03-06 2020-07-10 深圳市宝能投资集团有限公司 一种域名解析方法、装置、存储介质及电子设备
CN111541798B (zh) * 2020-04-24 2022-09-13 东软睿驰汽车技术（沈阳）有限公司 域名解析方法、装置以及电子设备
CN114143332B (zh) * 2021-11-03 2024-06-11 阿里巴巴（中国）有限公司 基于内容分发网络cdn的处理方法、电子设备和介质
CN116489128B (zh) * 2023-06-02 2024-06-07 北京云宽志业网络技术有限公司 域名解析方法和电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102216923A (zh) * 2008-11-17 2011-10-12 亚马逊技术有限公司 请求路由和利用客户位置信息来更新路由信息
CN103581213A (zh) * 2012-07-19 2014-02-12 阿里巴巴集团控股有限公司 一种共享Hosts文件的应用方法、设备和系统
CN104917851A (zh) * 2015-05-08 2015-09-16 亚信科技（南京）有限公司 信息处理方法及dns缓存服务器
CN105516385A (zh) * 2015-12-02 2016-04-20 传线网络科技（上海）有限公司 域名解析方法、服务器和系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102739811B (zh) * 2011-04-07 2016-03-02 中国移动通信集团公司 域名解析的方法和设备
CN103491201A (zh) * 2013-08-27 2014-01-01 北京蓝汛通信技术有限责任公司 一种域名解析的方法和域名服务器
WO2015112206A1 (fr) * 2014-01-21 2015-07-30 Telecommunication Systems, Inc. Résolveur ip intelligent
CN104243627A (zh) * 2014-08-29 2014-12-24 华为技术有限公司 一种域名解析方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102216923A (zh) * 2008-11-17 2011-10-12 亚马逊技术有限公司 请求路由和利用客户位置信息来更新路由信息
CN103581213A (zh) * 2012-07-19 2014-02-12 阿里巴巴集团控股有限公司 一种共享Hosts文件的应用方法、设备和系统
CN104917851A (zh) * 2015-05-08 2015-09-16 亚信科技（南京）有限公司 信息处理方法及dns缓存服务器
CN105516385A (zh) * 2015-12-02 2016-04-20 传线网络科技（上海）有限公司 域名解析方法、服务器和系统

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112217915A (zh) * 2020-09-28 2021-01-12 中国工商银行股份有限公司 传统环境互联网接入区适云改造方法及装置
CN112217915B (zh) * 2020-09-28 2022-10-11 中国工商银行股份有限公司 传统环境互联网接入区适云改造方法及装置
CN113364895A (zh) * 2021-06-29 2021-09-07 中国电信股份有限公司 用于资源调度的方法、装置、电子设备及存储介质
CN113364895B (zh) * 2021-06-29 2023-01-13 天翼云科技有限公司 用于资源调度的方法、装置、电子设备及存储介质
CN114553826A (zh) * 2022-01-11 2022-05-27 阿里巴巴（中国）有限公司 域名管理方法、装置、电子设备、介质及程序产品
CN114553826B (zh) * 2022-01-11 2023-10-17 阿里巴巴（中国）有限公司 域名管理方法、装置、电子设备、介质及程序产品
CN114500471A (zh) * 2022-03-28 2022-05-13 北京天维信通科技有限公司 Ip地址列表分析维护方法、系统、智能终端及存储介质
CN115189940A (zh) * 2022-07-08 2022-10-14 深圳依时货拉拉科技有限公司 一种域名解析方法、装置、计算机设备和计算机可读存储介质
CN118233428A (zh) * 2024-05-22 2024-06-21 中国电信股份有限公司 域名访问方法、装置及相关设备
CN119011380A (zh) * 2024-10-24 2024-11-22 天翼视联科技有限公司 一种dns解析监控方法、装置、电子装置和存储介质

Also Published As

Publication number Publication date
CN106797410A (zh) 2017-05-31

Similar Documents

Publication Publication Date Title
WO2018112944A1 (fr) Procédé et appareil de résolution de nom de domaine
US20230216884A1 (en) Method for minimizing the risk and exposure duration of improper or hijacked dns records
JP7514383B2 (ja) ネットワーク機能発見サービス向上を提供するための方法、システムおよびコンピュータ読取可能媒体
CN106068639B (zh) 通过dns处理的透明代理认证
US10033818B2 (en) Using listen ranges to deliver content to electronic devices from local caching servers
CN108737515B (zh) 在联网环境中请求路由选择
US10432581B2 (en) Network identification as a service
TWI652585B (zh) 遠端查詢訊息的方法及伺服器
JP5974079B2 (ja) 変更ホストネームを使用するグローバル・トラフィック管理
CN103957239B (zh) Dns缓存信息处理方法、设备及系统
US20100281146A1 (en) Dynamic domain name service system and automatic registration method
JP7771472B2 (ja) Ｃｄｎネットワーク要求のスケジューリング方法、装置、電子機器及び記憶媒体
US20150032905A1 (en) Method and system for associating internet protocol (ip) address, media access control (mac) address and location for a user device
US11025584B2 (en) Client subnet efficiency by equivalence class aggregation
WO2019010694A1 (fr) Procédé et dispositif d'acquisition d'adresse de serveur local de noms de domaine et serveur de noms faisant autorité
CN110071986A (zh) 一种用于域名解析的系统
RU2642833C2 (ru) Способ и устройство для обеспечения медиаресурса
WO2017012475A1 (fr) Procédé et dispositif d'acquisition de données
WO2017166524A1 (fr) Procédé et appareil d'analyse de nom de domaine
WO2022206549A1 (fr) Procédé et système d'acquisition de nom de domaine, dispositif électronique, équipement et support
WO2021129603A1 (fr) Procédé et dispositif d'acquisition d'informations d'emplacement, appareil, et support de stockage
US9438579B2 (en) Processing data
CN112769970A (zh) 一种用于dns ecs智能透传的方法和系统
WO2017000669A1 (fr) Procédé de commande de gestion centralisée, appareil, et dispositif associé pour la mise en cache d'enregistrements de ressources de noms de domaine
CN105872125A (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: 16924882

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 23.10.2019)

122 Ep: pct application non-entry in european phase

Ref document number: 16924882

Country of ref document: EP

Kind code of ref document: A1