Patent Grant
10757065
Embodiments of the present disclosure relate to the field of communications technologies, and specifically, to a domain name resolution method, apparatus, and system, and a storage medium.
An Internet Protocol (IP) address is a numeric address for identifying a site in a network. For ease of memorization, generally, an IP address is replaced with a domain name to identify a site address, and domain name resolution is a process of converting a domain name into an IP address. To enable a user to access an IP address corresponding to a domain name, domain name resolution needs to be used.
Embodiments of the present disclosure provide a domain name resolution method, apparatus, and system, and a storage medium.
A first aspect of the present disclosure provides a domain name resolution method performed at a server having one or more processors and memory storing a plurality of programs to be executed by the one or more processors, the method comprising:
receiving a domain name resolution request sent by a network device, the domain name resolution request carrying a first target domain name that needs to be resolved;
using the first target domain name as an initial value of a second target domain name;
resolving the second target domain name, to obtain a corresponding resolution result;
determining whether the resolution result corresponds to a network address of a preset type;
repeating the aforementioned operations using the resolution result as the second target domain name until a resolution result corresponding to the network address of the preset type is obtained; and
after obtaining the resolution result corresponding to the network address of the preset type, returning the resolution result to the network device.
A second aspect of the present disclosure further provides a server for domain name resolution, comprising one or more processors, memory coupled to the one or more processors, and a plurality of computer-readable instructions that, when executed by the one or more processors, cause the server to perform the foregoing domain name resolution method.
A third aspect of the present disclosure further provides a non-transitory computer readable storage medium storing a plurality of instructions in connection with a server having one or more processors, wherein the plurality of instructions, when executed by the one or more processors, cause the server to perform the foregoing domain name resolution method.
To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly describes the accompanying drawings required for describing the embodiments. Apparently, the accompanying drawings in the following description show merely some embodiments of the present disclosure, and a person skilled in the art may still derive other drawings from these accompanying drawings without creative efforts.
The following clearly and completely describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. Apparently, the described embodiments are merely some but not all of the embodiments of the present disclosure. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure.
Embodiments of the present disclosure provide a domain name resolution method, apparatus, and system.
The domain name resolution system may include any one of domain name resolution apparatuses provided in embodiments of the present disclosure. The domain name resolution apparatus may be specifically integrated into a server, for example, an authorized DNS (that is, an authorized DNS server). The authorized DNS is a server that resolves a domain name with higher level authorization. In addition, the domain name resolution system may further include another device such as a recursive DNS. The recursive DNS is mainly configured to: receive a query of a user for any domain name, send a domain name resolution request to the domain name resolution apparatus, receive a resolution result returned by the domain name resolution apparatus, and return a result to the user.
For example, an example in which the domain name resolution apparatus is specifically integrated into an authorized DNS is used. Referring to
Detailed descriptions are separately provided below. It should be noted that, sequence numbers of the following embodiments are not intended to limit a preferred sequence of the embodiments.
This embodiment is described from the perspective of a domain name resolution apparatus. The domain name resolution apparatus may be specifically integrated into a server, for example, a device such as an authorized DNS (that is, an authorized DNS server).
It may be understood that, the authorized DNS includes a memory and a processor. The memory stores instructions executable by the processor, and the processor implements a domain name resolution method by executing the instructions. The method includes: receiving a domain name resolution request that is sent by a network device and that carries a target domain name that needs to be resolved; resolving the target domain name, to obtain a resolution result; determining whether the resolution result is a network address of a preset type; and if not, updating the target domain name to the resolution result, and going back to the step of resolving the target domain name; or if yes, sending the resolution result to the network device.
As shown in
101: Receive a domain name resolution request sent by a network device, the domain name resolution request carrying information such as a domain name that needs to be resolved. For ease of description, in this embodiment of the present disclosure, the domain name that needs to be resolved is referred to as a target domain name.
For example, specifically, a domain name resolution request sent by a recursive DNS may be received. The domain name resolution request may be generated when the recursive DNS receives a network access request triggered by a user.
It may be understood that, in a subsequent step, the target domain name may be updated. Therefore, when the following step 102 is performed each time, the target domain name may be different, and an obtained resolution result is also different. Therefore, the target domain name in step 101 is referred to as a first target domain name, and the first target domain name is used as an initial value of a second target domain name. The second target domain name is a target domain name in the following step 102 to step 105. That is, 101 may also be described as “receiving a domain name resolution request sent by a network device, the domain name resolution request carrying a first target domain name that needs to be resolved; and using the first target domain name as an initial value of a second target domain name”.
102: Resolve the target domain name, to obtain a resolution result.
Herein, the target domain name is actually the second target domain name. When it is the first time to perform step 102, the second target domain name is the first target domain name. When it is not the first time to perform step 102, the second target domain name is not the first target domain name, but is a resolution result obtained in step 102 that is performed a previous time.
For example, specifically, configuration information of the target domain name may be searched for; and an address to which the target domain name points may be determined according to the configuration information, to obtain the resolution result.
The configuration information may be specifically resolution records of multiple record types, for example, a canonical name (CNAME) record or an A record. The A record is a record used to specify an IP address corresponding to a domain name. The CNAME record is a record for pointing a domain name to another domain name.
103: Determine whether the resolution result is a network address of a preset type; and if not, perform step 104; or if yes, perform step 105.
A type of the network address may be set according to an actual application requirement. For example, the network address may be set as an IP address. Therefore, whether the resolution result is an IP address may be determined; and if not, step 104 is performed; or if yes, step 105 is performed.
For example, if a record type of the configuration information of the target domain name is a CNAME record, the obtained resolution result is another domain name. Therefore, in this case, it may be determined that the resolution result is not a finally required IP address, and the resolution result needs to continue to be resolved, so that step 104 is performed. However, if a record type of the configuration information of the target domain name is an A record, the obtained resolution result is an IP address. Therefore, in this case, it may be determined that the resolution result is a finally required IP address, so that step 105 is performed.
It may be learned that, for the A record, the obtained resolution result is a finally required network address. Therefore, the resolution result does not need to continue to be resolved. For the CNAME record, the obtained resolution result needs to continue to be resolved. Therefore, to improve flexibility and processing efficiency, a record type of a resolution record corresponding to the target domain name may be determined first, and when it is determined that the record type is a CNAME record, and accelerated resolution needs to be performed, the step of “determining whether the resolution result is a network address of a preset type” is performed. That is, after the step of “searching for configuration information of the target domain name”, the domain name resolution method may further include:
determining, when it is determined that a record type of the configuration information is a CNAME record, whether accelerated resolution needs to be performed on the target domain name; and if yes, after the resolution result is obtained, performing the step of determining whether the resolution result is a network address of a preset type; or if not, sending the resolution result to the network device after the resolution result is obtained.
There may be multiple manners of determining whether accelerated resolution needs to be performed on the target domain name. For example, a corresponding identifier may be set for an “accelerated resolution function”. When the identifier indicates that the “accelerated resolution function” is enabled, it is determined that accelerated resolution needs to be performed on the target domain name; or if the identifier indicates that the “accelerated resolution function” is disabled, it is determined that accelerated resolution does not need to be performed on the target domain name. Whether the “accelerated resolution function” is enabled may be voluntarily set by a user, and details are not described herein.
Optionally, to reduce procedures and improve processing efficiency, when it is determined that a record type of a resolution record corresponding to the target domain name is an A record, the resolution result may be directly sent to the corresponding network device such as the recursive DNS. That is, after the step of “searching for configuration information of the target domain name”, the domain name resolution method may further include:
sending the resolution result to the network device after the resolution result is obtained when it is determined that a record type of the configuration information is an A record.
104: Update the target domain name to the resolution result, and go back to the step of resolving the target domain name, that is, go back to step 103.
It may be understood that, “updating the target domain name to the resolution result” may also be described as “using the resolution result as the second target domain name”. After the update, the second target domain name is changed.
For example, an example in which the target domain name is “www.a.com” is used. If the resolution result obtained by resolving the target domain name is “www.b.com”, “www.b.com” may be used as a new target domain name, and the new target domain name is resolved. Similarly, if a resolution result obtained after the new target domain name is resolved is a domain name, the resolution result also needs to be used as a new target domain name and continues to be resolved. If a resolution result obtained after the new target domain name is resolved is a network address of a preset type, for example, an IP address “1.2.3.4”, resolution does not need to be performed, and the resolution result may be sent to the network device, for example, sent to the recursive DNS (that is, step 105 is performed).
Optionally, to prevent a fault when the resolution result continues to be resolved, for example, configuration information corresponding to the resolution result cannot be obtained, before the target domain name is updated to the resolution result, whether the configuration information of the resolution result exists in a local or preset storage device may be determined, and if yes, the step of updating the target domain name to the resolution result is performed. That is, before the step of “updating the target domain name to the resolution result”, the domain name resolution method may further include:
determining whether configuration information of the resolution result exists; and if yes, performing the step of updating the target domain name to the resolution result; or if not, sending the resolution result to the network device, that is, performing step 105.
105: Send the resolution result to the network device, for example, send the resolution result to the recursive DNS.
Optionally, when the resolution result is sent to the network device, if resolution is performed multiple times, in addition to sending a final resolution result to the network device, for example, to the recursive DNS, another resolution result generated in the resolution process may be sent to the network device. Details are not described herein again.
It may be learned from the above that, in this embodiment, after the domain name resolution request sent by the network device is received, the target domain name may be resolved; when it is determined that the resolution result is not a network address of a preset type, the resolution result may be used as a new target domain name and resolution may continue to be performed; and when a finally required network address is obtained, the resolution result may be returned to the network device at a time. It may be learned that, for multiple levels of CNAME records, in this solution, only one resolution request needs to be made to obtain the required resolution result. Therefore, compared with an existing solution in which multiple resolution requests need to be made, this solution can simplify a procedure, shorten a resolution time, and greatly improve overall resolution efficiency.
According to the method described in Embodiment 1, further description is provided below by using an example.
In this embodiment, an example in which the domain name resolution apparatus is specifically integrated into the authorized DNS, the network device is specifically the recursive DNS, and the network address of the preset type is an IP address is used for description.
As shown in
201: The recursive DNS (that is, a recursive DNS server) sends a domain name resolution request to the authorized DNS (that is, an authorized DNS server).
The domain name resolution request may carry information such as a target domain name that needs to be resolved.
202: The authorized DNS searches for configuration information of a target domain name after receiving the domain name resolution request. Herein, the target domain name is actually a first target domain name. The first target domain name is used as an initial value of a second target domain name, and a subsequent step is performed.
For example, specifically, a local (that is, the authorized DNS) or specified storage device may be searched for the configuration information of the target domain name.
The configuration information may be specifically resolution records of multiple record types, for example, a CNAME record or an A record. The A record is a record used to specify an IP address corresponding to a domain name. For example, an A record with a domain name “www.c.com” may be set in the authorized DNS, and a record value is “1.2.3.4”. The CNAME record is a record for pointing a domain name to another domain name. For example, a CNAME record with a domain name “www.a.com” may be set in the authorized DNS, and a record value is “www.b.com”, and a CNAME record with a domain name “www.b.com” may be set in the authorized DNS, and a record value is “www.c.com”.
203: The authorized DNS determines, according to the configuration information, an address to which the target domain name points, to obtain a resolution result. That is, the authorized DNS determines, according to the configuration information, an address to which the second target domain name points, to obtain a corresponding resolution result.
For example, using an example in which the target domain name is “www.a.com”, if the configuration information of the target domain name is a CNAME record, and a record value is “www.b.com”, it may be determined that the address to which the target domain name points is “www.b.com”. Therefore, it may be obtained that the resolution result is “www.b.com”.
For another example, using an example in which the target domain name is “www.a.com”, if the configuration information of the target domain name is an A record, and a record value is “1.2.3.4”, it may be determined that the address to which the target domain name points is “1.2.3.4”. Therefore, it may be obtained that the resolution result is “1.2.3.4”. The rest may be deduced by analogy.
204: The authorized DNS determines a record type of the configuration information; and if the record type is a CNAME record, performs step 205; or if the record type is an A record, performs step 208.
For example, using an example in step 205, because a resolution record configured in the authorized DNS for the target domain name “www.a.com” is a CNAME record, and the record value “www.b.com”, step 205 may be performed. If the target domain name is “www.c.com”, because a resolution record configured in the authorized DNS for the target domain name is an A record, and the record value is “1.2.3.4”, step 208 may be performed.
205: The authorized DNS determines whether accelerated resolution needs to be performed on the second target domain name; and if yes, performs step 206; or if not, performs step 208.
There may be multiple manners of determining whether accelerated resolution needs to be performed on the target domain name. For example, a corresponding identifier may be set for an “accelerated resolution function”. When the identifier indicates that the “accelerated resolution function” is enabled, it is determined that accelerated resolution needs to be performed on the target domain name; or if the identifier indicates that the “accelerated resolution function” is disabled, it is determined that accelerated resolution does not need to be performed on the target domain name. Whether the “accelerated resolution function” is enabled may be voluntarily set by a user, and details are not described herein.
206: The authorized DNS determines whether the resolution result is an IP address; and if yes, performs step 208; or if not, performs step 207.
For example, if a record type of the configuration information of the target domain name is a CNAME record, the obtained resolution result is another domain name. Therefore, in this case, it may be determined that the resolution result is not a finally required IP address, and the resolution result needs to continue to be resolved, so that step 207 is performed. However, if a record type of the configuration information of the target domain name is an A record, the resolution result is an IP address. Therefore, in this case, it may be determined that the resolution result is a finally required IP address, so that step 208 is performed.
For example, still using the example in which the target domain name is “www.a.com”, because the resolution record configured in the authorized DNS for the target domain name “www.a.com” is a CNAME record, and the record value is “www.b.com”, step 207 may be performed.
For another example, if the target domain name is “www.c.com”, because the resolution record configured in the authorized DNS for “www.c.com” is an A record, and the record value is “1.2.3.4”, step 208 may be performed.
207: The authorized DNS updates the target domain name to the resolution result (that is, the resolution result is used as the second target domain name), and goes back to the step of searching for configuration information of the second target domain name, that is, goes back to step 202.
For example, if the resolution result is “www.b.com”, “www.b.com” may be used as a new target domain name, and continues to be resolved.
Optionally, to prevent a fault when the resolution result continues to be resolved, for example, configuration information corresponding to the resolution result cannot be obtained, before the target domain name is updated to the resolution result, whether the configuration information of the resolution result exists in a local (that is, the authorized DNS) or preset storage device may be determined, and if yes, the step of updating the target domain name to the resolution result is performed; or if not, the resolution result is sent to the network device. That is, step 208 is performed.
208: The authorized DNS sends the resolution result to the recursive DNS.
Optionally, when the resolution result is sent to the network device, if resolution is performed multiple times, in addition to sending a final resolution result to the network device, for example, to the recursive DNS, another resolution result generated in the resolution process may be sent to the network device. For example, using an example in which the target domain name is “www.a.com”, details are as follows:
The resolution recorded configured in the authorized DNS for the domain name “www.a.com” is a CNAME record, and the record value is “www.b.com”, the resolution recorded configured in the authorized DNS for the domain name “www.b.com” is also a CNAME record, and the record value is “www.c.com”, and the resolution recorded configured in the authorized DNS for the domain name “www.c.com” is an A record, and the record value is “1.2.3.4”. Therefore, when “www.a.com” is used as the target domain name and resolution is performed the first time, an obtained resolution result is “www.b.com”. Assuming that accelerated resolution is enabled, “www.b.com” needs to be used as a new target domain name and resolution continues to be performed the second time, and an obtained resolution result is “www.c.com”. Assuming that accelerated resolution is also enabled for the domain name “www.c.com”, “www.c.com” needs to be used as a new target domain name and resolution continues to be performed the third time, and an obtained resolution result is “1.2.3.4”, and is a finally required IP address. Therefore, “1.2.3.4” may be used as a final resolution result and sent to the recursive DNS. Optionally, in addition, other resolution results generated in the resolution process, that is, “www.b.com” and “www.c.com” are also sent to the recursive DNS. Refer to
It may be understood that, step 205 of determining whether accelerated resolution needs to be performed may be performed before the cycle is entered, that is, before step 202. In this way, whether accelerated resolution needs to be performed does not need to be determined in each cycle, thereby further increasing a domain name resolution speed.
It should be noted that, if accelerated resolution is not enabled, as shown in
1. The recursive DNS requests the authorized DNS to resolve “www.a.com”, and the authorized DNS returns the resolution result “www.b.com”.
2. The recursive DNS requests the authorized DNS to resolve “www.b.com”, and the authorized DNS returns the resolution result “www.c.com”.
3. The recursive DNS requests the authorized DNS to resolve “www.c.com”, and the authorized DNS returns the resolution result “1.2.3.4”.
It may be learned from the above that, in this embodiment, after receiving the domain name resolution request sent by the recursive DNS, the authorized DNS may resolve the target domain name; when determining that the resolution result is not a network address of a preset type, use the resolution result as a new target domain name and continue to perform resolution; and when obtaining a finally required network address, return the resolution result to the recursive DNS at a time. It may be learned that, for multiple levels of CNAME records, in this solution, only one resolution request needs to be made to obtain the required resolution result. Therefore, compared with an existing solution in which multiple resolution requests need to be made, this solution can simplify a procedure, shorten a resolution time, and greatly improve overall resolution efficiency. In addition, whether accelerated resolution is performed may be further set, so that operation flexibility is greatly improved.
To better implement the foregoing method, this embodiment of the present disclosure further provides a domain name resolution apparatus. As shown in
one or more memories; and
one or more processors.
The one or more memories store one or more instruction modules, configured to be executed by the one or more processors.
The one or more instruction modules include a receiving unit 301, a resolution unit 302, a first determining unit 303, and a sending unit 304. Details are as follows:
(1) The Receiving Unit 301
The receiving unit 301 is configured to receive a domain name resolution request sent by a network device, the domain name resolution request carrying a target domain name that needs to be resolved.
For example, the receiving unit 301 may be specifically configured to receive a domain name resolution request sent by a recursive DNS, where the domain name resolution request may be generated when the recursive DNS receives a network access request triggered by a user.
(2) The Resolution Unit 302
The resolution unit 302 is configured to resolve the target domain name, to obtain a resolution result.
For example, the resolution unit 302 may be specifically configured to: search for configuration information of the target domain name; and determine, according to the configuration information, an address to which the target domain name points, to obtain the resolution result.
The configuration information may be specifically resolution records of multiple record types, for example, a CNAME record or an A record.
(3) The First Determining Unit 303
The first determining unit 303 is configured to: determine whether the resolution result is a network address of a preset type; and if not, update the target resolution result to the resolution result, and trigger the resolution unit 302 to perform the operation of resolving the target domain name.
A type of the network address may be set according to an actual application requirement. For example, the network address may be set as an IP address. That is,
the first determining unit 303 may be specifically configured to: determine whether the resolution result is an IP address; and if not, update the target domain name to the resolution result, and trigger the resolution unit 302 to perform the operation of resolving the target domain name.
Optionally, to prevent a fault when the resolution result continues to be resolved, for example, configuration information corresponding to the resolution result cannot be obtained, before the target domain name is updated to the resolution result, whether the configuration information of the resolution result exists in a local or preset storage device may be determined, and if yes, the operation of updating the target domain name to the resolution result is performed. That is,
the first determining unit 303 may be further configured to: before the target domain name is updated to the resolution result, determine whether configuration information of the resolution result exists; and if yes, perform the operation of updating the target domain name to the resolution result; or if not, trigger the sending unit 304 to perform the operation of sending the network device to the resolution result.
(4) The Sending Unit 304
The sending unit 304 is configured to send the resolution result to the network device when the first determining unit 303 determines that the resolution result is a network address of a preset type.
Optionally, when the resolution result is sent to the network device, if resolution is performed multiple times, in addition to sending a final resolution result to the network device, for example, to the recursive DNS, the sending unit 304 may send another resolution result generated in the resolution process to the network device. Details are not described herein again.
To improve flexibility and processing efficiency, a record type of a resolution record corresponding to the target domain name may be determined first, and when it is determined that the record type is a CNAME record, and accelerated resolution needs to be performed, the operation of “determining whether the resolution result is a network address of a preset type” is performed. That is, as shown in
The second determining unit 305 is configured to: determine, when it is determined that a record type of the configuration information found by the resolution unit 302 is a CNAME record, whether accelerated resolution needs to be performed on the target domain name; and if yes, trigger, after the resolution unit 302 obtains the resolution result, the first determining unit 303 to perform the operation of determining whether the resolution result is a network address of a preset type; or if not, trigger, after the resolution unit 302 obtains the resolution result, the sending unit 304 to send the resolution result to the network device.
Optionally, to reduce procedures and improve processing efficiency, when it is determined that a record type of a resolution record corresponding to the target domain name is an A record, the resolution result may be directly sent to the corresponding network device. That is,
the sending unit 304 may be further configured to: send the resolution result to the network device after the resolution unit 302 obtains the resolution result when it is determined that a record type of the configuration information found by the resolution unit 302 is an A record, for example, send the resolution result to the recursive DNS.
During specific implementation, the foregoing units may be implemented as separate entities or combined randomly, or implemented as a same entity or several entities. For specific implementations of the foregoing units, refer to the foregoing method embodiments. Details are not described herein again.
The domain name resolution apparatus may be specifically integrated into a server, for example, a device such as the authorized DNS.
It may be learned from the above that, in this embodiment, after the domain name resolution apparatus receives the domain name resolution request sent by the network device, the resolution unit 302 may resolve the target domain name; when the first determining unit 303 determines that the resolution result is not a network address of a preset type, the resolution result may be used as a new target domain name, and the resolution unit 3052 may continue to perform resolution; and when a finally required network address is obtained, the sending unit 304 may return the resolution result to the network device at a time. It may be learned that, for multiple levels of CNAME records, in this solution, only one resolution request needs to be made to obtain the required resolution result. Therefore, compared with an existing solution in which multiple resolution requests need to be made, this solution can simplify a procedure, shorten a resolution time, and greatly improve overall resolution efficiency.
Correspondingly, this embodiment of the present disclosure further provides a domain name resolution system, including any one of the domain name resolution apparatuses provided in the embodiments of the present disclosure. The domain name resolution apparatus may be specifically integrated into a server, for example, a device such as an authorized DNS. For example, an example in which the domain name resolution apparatus is integrated into the authorized DNS is used. Details may be as follows:
The authorized DNS is configured to: receive a domain name resolution request that is sent by a network device such as a recursive DNS and that carries a target domain name that needs to be resolved; resolve the target domain name, to obtain a resolution result; determining whether the resolution result is a network address of a preset type; and if not, update the target domain name to the resolution result, and go back to the step of resolving the target domain name; or if yes, send the resolution result to the network device.
For example, the authorized DNS may be specifically configured to: search for configuration information of the target domain name; and determine, according to the configuration information, an address to which the target domain name points, to obtain the resolution result.
The configuration information may be specifically resolution records of multiple record types, for example, a CNAME record or an A record.
Optionally, the authorized DNS may be further configured to: determine, when it is determined that a record type of the configuration information is a CNAME record, whether accelerated resolution needs to be performed on the target domain name; and if yes, after the resolution result is obtained, perform the operation of determining whether the resolution result is a network address of a preset type; or if not, send the resolution result to the network device (for example, the recursive DNS) after the resolution result is obtained.
Optionally, the authorized DNS may be further configured to send the resolution result to the network device after the resolution result is obtained when it is determined that a record type of the configuration information is an A record.
Optionally, the authorized DNS may be further configured to determine whether configuration information of the resolution result exists; and if yes, perform the operation of updating the target domain name to the resolution result; or if not, send the resolution result to the network device.
In addition, optionally, the domain name resolution system may further include another network device such as the recursive DNS. Details are as follows:
The recursive DNS may be configured to: send, to the authorized DNS, the domain name resolution request that carries the target domain name that needs to be resolved, and receive the resolution result sent by the authorized DNS.
For specific implementations of the foregoing devices, refer to the foregoing embodiments, and details are not described herein again.
Because the domain name resolution system may include any one of the domain name resolution apparatuses provided in the embodiments of the present disclosure, a beneficial effect that can be implemented by any one of the domain name resolution apparatuses provided in the embodiments of the present disclosure can be implemented. For details, refer to the foregoing embodiments, and details are not described herein again.
In addition, this embodiment of the present disclosure further provides a server.
The server may include components such as a processor 401 having one or more processing cores, a memory 402 having one or more computer-readable storage mediums, a radio frequency (RF) circuit 403, a power supply 404, an input unit 405, and a display unit 406. A person skilled in the art may understand that the structure of the server shown in
The processor 401 is the control center of the server, and is connected to various parts of the server by using various interfaces and lines. The processor 401 performs various functions and data processing of the server by running or executing the software program and/or module stored in the memory 402, and invoking data stored in the memory 402, thereby performing overall monitoring on the server. Optionally, the processor 401 may include one or more processing cores. Preferably, the processor 401 may integrate an application processor and a modem processor. The application processor mainly processes an operating system, a user interface, an application program, and the like. The modem processor mainly processes wireless communication. It may be understood that the foregoing modem processor may not be integrated into the processor 401.
The memory 402 may be configured to store a software program and module. The processor 401 runs the software program and module stored in the memory 402, to implement various functional applications and data processing. The memory 402 may mainly include a program storage area and a data storage area. The program storage area may store an operating system, an application program required by at least one function (such as a sound playback function and an image display function), and the like. The data storage area may store data created according to use of the server, and the like. In addition, the memory 402 may include a high-speed random access memory (RAM), and may further include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory, or other volatile solid-state storage devices. Correspondingly, the memory 402 may further include a memory controller for the processor 401 to access the memory 402.
The RF circuit 403 may be configured to receive and send signals during information receiving and sending. Particularly, the RF circuit 401 receives downlink information from a base station, then delivers the downlink information to one or more processors 401 for processing, and sends related uplink data to the base station. Generally, the RF circuit 403 includes, but is not limited to, an antenna, at least one amplifier, a tuner, one or more oscillators, a subscriber identity module (SIM) card, a transceiver, a coupler, a low noise amplifier (LNA), and a duplexer. In addition, the RF circuit 403 may further communicate with a network and another device through wireless communication. The wireless communication may use any communications standard or protocol, which includes, but is not limited to, a Global System for Mobile communications (GSM), a general packet radio service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), an e-mail, a Short Messaging Service (SMS), and the like.
The server further includes the power supply 404 (such as a battery) for supplying power to the components. Preferably, the power supply 404 may logically connect to the processor 401 by using a power supply management system, thereby implementing functions, such as charging, discharging, and power consumption management, by using the power supply management system. The power supply 404 may further include one or more of a direct current or alternating current power supply, a re-charging system, a power failure detection circuit, a power supply converter or inverter, a power supply state indicator, and any other components.
The server may further include an input unit 405. The input unit 405 may be configured to receive input digit or character information, and generate a keyboard, mouse, joystick, optical or track ball signal input related to the user setting and function control. Specifically, in a specific embodiment, the input unit 405 may include a touch-sensitive surface and another input device. The touch-sensitive surface, which may also be referred to as a touch display screen or a touch panel, may collect a touch operation of a user on or near the touch-sensitive surface (such as an operation of a user on the touch-sensitive surface or near the touch-sensitive surface by using any suitable object or accessory, such as a finger or a stylus), and drive a corresponding connection apparatus according to a preset program. Optionally, the touch-sensitive surface may include two parts: a touch detection apparatus and a touch controller. The touch detection apparatus detects a touch position of the user, detects a signal generated by the touch operation, and transfers the signal to the touch controller. The touch controller receives touch information from the touch detection apparatus, converts the touch information into touch point coordinates, and sends the touch point coordinates to the processor 401. Moreover, the touch controller can receive and execute a command sent by the processor 401. In addition, the touch-sensitive surface may be may be a resistive, capacitive, infrared, or surface sound wave type touch-sensitive surface. In addition to the touch-sensitive surface, the input unit 405 may include the another input device. Specifically, the another input device may include, but is not limited to, one or more of a physical keyboard, a functional key (such as a volume control key or a switch key), a track ball, a mouse, and a joystick.
The server may further include the display unit 406. The display unit 406 may be configured to display information entered by the user or information provided for the user, and various graphical user interfaces of the server. The graphical user interfaces may be formed by a graph, a text, an icon, a video, or any combination thereof. The display unit 406 may include a display panel. Optionally, the display panel may be configured by using a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like. Further, the touch-sensitive surface may cover the display panel. After detecting a touch operation on or near the touch-sensitive surface, the touch-sensitive surface transfers the touch operation to the processor 401, so as to determine the type of the touch event. Then, the processor 401 provides a corresponding visual output on the display panel according to the type of the touch event. Although, in
Although not shown in the figure, the server may further include a camera, a Bluetooth module, and the like. Details are not described herein. Specifically, in this embodiment, the processor 401 in the server loads, into the memory 402 according to the following instructions, executable files corresponding to processes of one or more application programs, and the processor 401 runs the application programs stored in the memory 402 to implement the following various functions:
receiving a domain name resolution request that is sent by a network device such as a recursive DNS and that carries a target domain name that needs to be resolved; resolving the target domain name, to obtain a resolution result; determining whether the resolution result is a network address of a preset type; and if not, updating the target domain name to the resolution result, and going back to the step of resolving the target domain name; or if yes, sending the resolution result to the network device.
For example, configuration information of the target domain name is searched for; and an address to which the target domain name points is determined according to the configuration information, to obtain the resolution result.
Optionally, to improve flexibility and processing efficiency, a record type of a resolution record corresponding to the target domain name may be determined first, and when it is determined that the record type is a CNAME record, and accelerated resolution needs to be performed, the operation of “determining whether the resolution result is a network address of a preset type” is performed. That is, an application program stored in the memory 402 can further implement the following function:
determining, when it is determined that a record type of the configuration information is a CNAME record, whether accelerated resolution needs to be performed on the target domain name; and if yes, after the resolution result is obtained, performing the operation of determining whether the resolution result is a network address of a preset type; or if not, sending the resolution result to the network device after the resolution result is obtained.
Optionally, to reduce procedures and improve processing efficiency, when it is determined that a record type of a resolution record corresponding to the target domain name is an A record, the resolution result may be directly sent to the corresponding network device such as the recursive DNS. That is, the application program stored in the memory 402 can further implement the following function:
sending the resolution result to the network device after the resolution result is obtained when it is determined that a record type of the configuration information is an A record.
Optionally, to prevent a fault when the resolution result continues to be resolved, for example, configuration information corresponding to the resolution result cannot be obtained, before the target domain name is updated to the resolution result, whether the configuration information of the resolution result exists in a local or preset storage device may be determined, and if yes, the operation of updating the target domain name to the resolution result is performed. That is, the application program stored in the memory 402 can further implement the following function:
determining whether configuration information of the resolution result exists; and if yes, performing an operation of updating the target domain name to the resolution result; or if not, sending the resolution result to the network device.
For specific implementations of the foregoing operations, refer to the foregoing embodiments, and details are not described herein again.
It may be learned from the above that, in this embodiment, after receiving the domain name resolution request sent by the network device, the server may resolve the target domain name; when determining that the resolution result is not a network address of a preset type, use the resolution result as a new target domain name and continue to perform resolution; and when obtaining a finally required network address, return the resolution result to the network device at a time. It may be learned that, for multiple levels of CNAME records, in this solution, only one resolution request needs to be made to obtain the required resolution result. Therefore, compared with an existing solution in which multiple resolution requests need to be made, this solution can simplify a procedure, shorten a resolution time, and greatly improve overall resolution efficiency.
A person of ordinary skill in the art may understand that all or some of the steps of the methods in the embodiments may be implemented by a program instructing relevant hardware. The program may be stored in a computer-readable storage medium. The storage medium may include: a read-only memory (ROM), a RAM, a magnetic disk, or an optical disc.
An embodiment of the present disclosure further provides a non-volatile computer-readable storage medium, storing a computer program, when being executed by a processor, the program implementing the steps of any one of the foregoing methods.
The domain name resolution method, apparatus, and system in the embodiments of the present disclosure are described in detail above. The principle and the implementation of the present disclosure are described herein through specific examples. The descriptions of the embodiments of the present disclosure are merely provided for ease of understanding of the method and core ideas of the present disclosure. In addition, a person skilled in the art may make variations and modifications to the present disclosure in terms of the specific implementations and application scopes according to the ideas of the present disclosure. Therefore, the specification shall not be construed as a limit to the present disclosure.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2016 1 1078704 | Nov 2016 | CN | national |
This application is a continuation of PCT Application PCT/CN2017/110342, entitled “DOMAIN NAME RESOLUTION METHOD, DEVICE AND SYSTEM, AND STORAGE MEDIUM” filed Nov. 10, 2017, which claims priority to Chinese Patent Application No. 201611078704.6, filed with the Chinese Patent Office on Nov. 28, 2016 and entitled “DOMAIN NAME RESOLUTION METHOD, APPARATUS, AND SYSTEM”, all of which are incorporated herein by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 8463877 | Richardson | Jun 2013 | B1 |
| 8577992 | Richardson | Nov 2013 | B1 |
| 9003035 | Richardson | Apr 2015 | B1 |
| 10097448 | Howard | Oct 2018 | B1 |
| 20020172206 | Vaman | Nov 2002 | A1 |
| 20090248786 | Richardson | Oct 2009 | A1 |
| 20090327517 | Sivasubramanian | Dec 2009 | A1 |
| 20100125673 | Richardson | May 2010 | A1 |
| 20100125675 | Richardson | May 2010 | A1 |
| 20130103784 | Lyon | Apr 2013 | A1 |
| 20130297826 | Raciborski et al. | Nov 2013 | A1 |
| 20160036943 | Kish | Feb 2016 | A1 |
| 20190222551 | Chen | Jul 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 102307248 | Jan 2012 | CN |
| 105681491 | Jun 2016 | CN |
| 106453692 | Feb 2017 | CN |
| Entry |
|---|
| Tencent Technology, Written Opinion, PCT/CN2017/110342, dated Jan. 30, 2018, 5 pgs. |
| Tencent Technology, IPRP, PCT/CN2017/110342, dated May 28, 2019, 6 pgs. |
| Tencent Technology, ISR, PCT/CN2017/110342, dated Jan. 30, 2018, 2 pgs. |
| Number | Date | Country | |
|---|---|---|---|
| 20190222551 A1 | Jul 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2017/110342 | Nov 2017 | US |
| Child | 16362456 | US |
