WO2016177276A1 - 一种域名解析的同步方法和设备 - Google Patents
一种域名解析的同步方法和设备 Download PDFInfo
- Publication number
- WO2016177276A1 WO2016177276A1 PCT/CN2016/079809 CN2016079809W WO2016177276A1 WO 2016177276 A1 WO2016177276 A1 WO 2016177276A1 CN 2016079809 W CN2016079809 W CN 2016079809W WO 2016177276 A1 WO2016177276 A1 WO 2016177276A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- sent
- domain name
- dns
- parsing result
- client device
- 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
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
Definitions
- the present application relates to the field of Internet information technology processing, and in particular, to a synchronization method and device for domain name resolution.
- IP Internet Protocol
- the IP address is not easily remembered by people, it is proposed to replace the IP address with a domain name.
- the domain name cannot be directly accessed by the domain name corresponding to the computer corresponding to the IP address. Therefore, when obtaining a domain name, the domain name resolution process is required to convert the obtained domain name into an IP address; and the obtained IP address is used to access the computer corresponding to the IP address.
- Domain name resolution generally relies on the domain name service (English: Domain Name Service; abbreviation: DNS) system to map domain names to IP addresses.
- DNS Domain Name Service
- the Domain Name Service System is a distributed database based on TCP/IP applications that provides translation between host names and IP addresses.
- DNS Domain Name Service
- the public DNS when receiving the domain name query request, queries the local cached parsing result; if the parsing result corresponding to the domain name included in the domain name query request is queried, the parsed result is returned to the user; if not yet queried If the domain name is included in the query request, the domain name to be queried is carried in the query request and sent to the upper layer DNS (for example, local DNS), and the upper layer DNS is requested to be included in the query request.
- the domain name is parsed.
- the DNS of the upper layer determines whether the domain name to be queried can be parsed, and if it can be directly parsed, returns the parsing result; if it cannot be directly parsed, the local cache parsing result is queried by querying the local cache. Determine whether the analysis result corresponding to the domain name can be determined.
- the domain name to be queried is carried in the query request and sent to the DNS of the upper layer.
- the above operations are performed in sequence, and the operation ends when the analysis result corresponding to the domain name is queried.
- Authoritative DNS refers to a server that is authorized to parse a domain name, and has the function of authorizing the resolution result to other DNS.
- the top-level server of the domain name com can authorize the authoritative server of the domain name ABC.com as NS.ABC.com.
- the authorized DNS sends the parsing result to the public DNS, so that the public DNS stores the parsed result received locally.
- the embodiment of the present application provides a method and a device for synchronizing domain name resolution, which are used to solve the problem that the analysis efficiency of the current public domain DNS for domain name resolution is low.
- a method for synchronizing domain name resolution comprising:
- the received parsing result is sent to a different public DNS device.
- a synchronization device for domain name resolution comprising:
- a receiving unit configured to receive an analysis result sent by the authoritative domain name service DNS device, where the parsing result is sent after the parsing result of the internal cache of the authoritative DNS device is updated;
- a sending unit configured to send the received parsing result to a different public DNS device.
- the embodiment of the present application receives the parsing result sent by the authoritative domain name service DNS device, and the parsing result is sent after the parsing result of the internal cache of the authoritative DNS device is updated;
- the parsing result is sent to different public DNS devices.
- the third device between the authoritative DNS device and the public DNS device sends the newly validated parsing result in the authoritative DNS device to the public DNS device to ensure the public DNS.
- the analysis result that is valid in the device cache is consistent with the resolution of the valid DNS device. This prevents the delay in the validity of the analysis result due to the inconsistency of the cache refresh time in the public DNS device. This improves the public DNS device's domain name resolution. Analytical efficiency.
- FIG. 1 is a schematic flowchart of a method for synchronizing domain name resolution according to an embodiment of the present disclosure
- FIG. 2 is a schematic structural diagram of a synchronization device for domain name resolution according to an embodiment of the present disclosure
- FIG. 3 is a schematic structural diagram of a synchronization system for domain name resolution according to an embodiment of the present disclosure.
- an embodiment of the present application provides a method and a device for synchronizing domain name resolution, and receiving an analysis result sent by an authoritative domain name service DNS device, where the parsing result is that an analysis result of the internal cache of the authoritative DNS device occurs.
- the update is sent; the received parsing result is sent to a different public DNS device.
- the third device between the authoritative DNS device and the public DNS device sends the newly validated parsing result in the authoritative DNS device to the public DNS device to ensure the public DNS.
- the analysis result that is valid in the device cache is consistent with the resolution of the valid DNS device. This prevents the delay in the validity of the analysis result due to the inconsistency of the cache refresh time in the public DNS device. This improves the public DNS device's domain name resolution. Analytical efficiency.
- FIG. 1 is a schematic flowchart of a method for synchronizing domain name resolution according to an embodiment of the present disclosure.
- the method can be as follows.
- the execution entity of the embodiment of the present application may be an application client or a third-party server, which is not limited herein.
- Step 101 The third-party server receives the parsing result sent by the authoritative DNS device.
- the parsing result is sent after the parsing result of the internal cache of the authoritative DNS device is updated.
- the third-party server may perform information interaction with the authoritative DNS device, and may also perform information interaction with the public DNS device.
- a third-party server uses the Hypertext Transfer Protocol (English: Hypertext Transfer Protocol; abbreviation: HTTP) to exchange information with an authoritative DNS device; and uses HTTP to interact with public DNS devices.
- Hypertext Transfer Protocol English: Hypertext Transfer Protocol; abbreviation: HTTP
- the authoritative DNS device actively sends the updated parsing result to the third-party server.
- the domain name to be resolved is carried in the parsing production request and sent to the authoritative DNS device.
- the parsing production request is used to request the authoritative DNS device to parse the domain name to be parsed and return an analysis result.
- the domain name to be resolved is carried in the parsing production request and sent to the authoritative DNS device, to request the authoritative DNS device to parse the domain name to be parsed. Returns the result of the analysis.
- the third-party server when the third-party server receives the domain name to be resolved, the third-party server sends a parsing result query request to the authoritative DNS device, where the parsing result query request includes the domain name to be parsed, and the parsing result query request is used to determine the received waiting Whether the parsed domain name has the corresponding parsing result.
- the authoritative DNS device determines that the domain name to be resolved does not have a corresponding parsing result
- the query result is sent to the third-party server.
- the third-party server carries the domain name to be parsed in the parsing production request and sends it to the authoritative DNS. device.
- the authoritative DNS device Upon receiving the parsing production request, the authoritative DNS device parses the domain name to be parsed, obtains the parsing result corresponding to the domain name to be parsed, and updates the parsing result in the cache.
- the authoritative DNS device sends the parsing result corresponding to the domain name to be resolved to the third-party server.
- the authoritative DNS device parses the domain name to be parsed when receiving the parsing production request, obtains the parsing result corresponding to the domain name to be parsed, and updates the parsing result of the internal cache, then the authoritative DNS device
- the analysis result corresponding to the domain name to be resolved may be sent to the third-party server, or the updated analysis result may be sent to the third-party server.
- the parsing production request sent by the third-party server can be regarded as a trigger condition for the authoritative DNS device to send the parsing result to the third-party server.
- the parsing result sent by the authoritative DNS device to the third-party server may be the parsing result currently in effect, or may be the parsing result that is valid within the set time range.
- the manner in which the third-party server receives the parsing result sent by the authoritative DNS device may also be:
- the third party server sends a query request to the authoritative DNS device in real time.
- the query request is used to request the authoritative DNS device to send the updated parsing result.
- the third party server receives the query result sent by the authoritative DNS device.
- the query result includes an analysis result of the latest update of the authoritative DNS device.
- the latest updated parsing result can be understood as an analysis result after an update operation that is closest to the time when the authoritative DNS device receives the query request.
- Step 102 The third-party server sends the received parsing result to different public DNS devices.
- step 102 when the third-party server receives the parsing result sent by the authoritative DNS device, The received parsing result is sent to different public DNS devices by using HTTP.
- the method further includes:
- the received parsing result is sent to the client device corresponding to each public DNS device, including:
- a heartbeat packet is sent to the client device corresponding to each public DNS device.
- the heartbeat data packet is used to determine whether the client device is online.
- the method further includes:
- the first set time range may be determined according to the effective time of the heartbeat data packet, or may be determined according to actual needs; the second set time range is larger than the first set time range.
- the heartbeat data packet is periodically sent to the client device, and the third party service is received when the response data packet sent by the client device is received again.
- the device may receive the parsing result sent by the authoritative DNS device multiple times. Therefore, the third-party server may send the parsing result from the time when the client device is offline to the client device, and send the result to the client device to ensure the internality of the client device.
- the analysis result is consistent with the analysis result in the authoritative DNS device.
- the parsing result sent by the authoritative domain name service DNS device where the parsing result is sent after the parsing result of the internal cache of the authoritative DNS device is updated; sending the parsing result received Give different public DNS devices.
- the third device between the authoritative DNS device and the public DNS device sends the newly validated parsing result in the authoritative DNS device to the public DNS device to ensure the public DNS.
- the analysis result that is valid in the device cache is consistent with the resolution of the valid DNS device. This prevents the delay in the validity of the analysis result due to the inconsistency of the cache refresh time in the public DNS device. This improves the public DNS device's domain name resolution. Analytical efficiency.
- FIG. 2 is a schematic structural diagram of a synchronization device for domain name resolution according to an embodiment of the present disclosure.
- the synchronization device includes: a receiving unit 21 and a transmitting unit 22, where:
- the receiving unit 21 is configured to receive an analysis result sent by the authoritative domain name service DNS device, where the parsing result is sent after the parsing result of the internal cache of the authoritative DNS device is updated;
- the sending unit 22 is configured to send the received parsing result to different public DNS devices.
- the sending unit 23 is further configured to: when the received parsing result is sent to a different public DNS device, send the received parsing result to a client corresponding to each public DNS device. And causing the client device to store the parsed result received locally.
- the sending unit 23 is configured to send a heartbeat data packet to a client device corresponding to each public DNS device, where the heartbeat data packet is used to determine whether the client device is online;
- the sending unit 23 is further configured to not receive the foregoing in the first set time range.
- the heartbeat data packet is periodically sent to the client device, and when the response data packet sent by the client device is received, the received device in the second set time range is received.
- the parsing result is sent to the client device.
- the synchronization device further includes: an obtaining unit 23, where:
- the obtaining unit 23 is configured to obtain a domain name to be parsed, and send the domain name to be parsed in a parsing production request to an authoritative domain name service DNS device, where the parsing production request is used to request the authoritative DNS
- the device parses the domain name to be resolved and returns an analysis result.
- the receiving unit 21 is configured to receive an analysis result sent by the authoritative DNS device, where the parsing result includes an analysis result corresponding to the domain name to be parsed.
- the synchronization device in the embodiment of the present invention may be implemented in a hardware manner or in a software manner, which is not limited herein.
- FIG. 3 is a schematic structural diagram of a synchronization system for domain name resolution according to an embodiment of the present disclosure.
- the synchronization system includes: an authoritative DNS device 31, a public DNS device 32, a synchronization device 33, and a client device 34 corresponding to the public DNS device, wherein:
- the authoritative DNS device 31 is configured to send the updated parsing result to the synchronization device 33;
- the synchronization device 33 is configured to receive the parsing result sent by the authoritative DNS device, where the parsing result is sent after the parsing result of the internal cache of the authoritative DNS device is updated, and the parsing result is received. Sent to a different public DNS device 32.
- the synchronization device 33 is further configured to send the received parsing result to the client device 34 corresponding to each public DNS device, so that the client device stores the parsed result received locally.
- the synchronization device 33 is specifically configured to send a heartbeat data packet to the client device 34 corresponding to each public DNS device 32, where the heartbeat data packet is used to determine whether the client device 34 is online;
- the received parsing result is sent to the client device 34.
- the synchronization device 33 is configured to periodically send a heartbeat data packet to the client device 34 when the response data packet sent by the client device 34 has not been received within the first set time range, and receive the heartbeat data packet.
- the response packet sent by the client device 34 is sent, the parsing result received in the second set time range is sent to the client device 34.
- the synchronization device 33 is further configured to: before receiving the parsing result sent by the authoritative DNS device 31, obtain the domain name to be parsed, and carry the domain name to be parsed in the parsing production request and send it to the authoritative DNS device 31, where The parsing production request is used to request the authoritative DNS device 31 to parse the domain name to be parsed and return an analysis result.
- the synchronization device 33 is configured to receive an analysis result sent by the authoritative DNS device 31, where the analysis result includes an analysis result corresponding to the domain name to be resolved.
- the authoritative DNS device resolves the domain name and generates a new resolution result
- the newly-resolved analysis result in the authoritative DNS device is sent to the public DNS device through the synchronization device between the authoritative DNS device and the public DNS device to ensure the public DNS device cache.
- the result of the validation is consistent with the resolution of the valid DNS device. This prevents the delay in the validity of the analysis result due to the inconsistency of the cache refresh time in the public DNS device. This improves the efficiency of domain name resolution for public DNS devices.
- embodiments of the present application can be provided as a method, apparatus (device), or computer program product.
- the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
- the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
- These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本申请公开了一种域名解析的同步方法和设备，包括：接收权威域名服务DNS设备发送的解析结果，所述解析结果是在所述权威DNS设备内部缓存的解析结果发生更新后发送的；将接收到的所述解析结果发送给不同的公共DNS设备。这样，当权威DNS设备解析域名产生新的解析结果时，通过权威DNS设备与公共DNS设备之间的第三设备，将在权威DNS设备中新生效的解析结果发送给公共DNS设备，确保公共DNS设备缓存中生效的解析结果与权威DNS设备中生效的解析结果一致，避免了由于公共DNS设备中缓存刷新时间的不一致使得解析结果生效时间出现延迟的问题，有效地提升公共DNS设备进行域名解析的解析效率。
Description
本申请涉及互联网信息技术处理领域，尤其涉及一种域名解析的同步方法和设备。
随着互联网技术的发展，人们对于互联网中的计算机可以通过网络之间互连的协议(英文：Internet Protocol；缩写：IP)地址进行定位，即在得到一个IP地址时，通过该IP地址可以确定互联网中与该IP地址对应的计算机。
然而，由于IP地址不容易被人们记住，于是提出由域名来代替IP地址。但是，通过域名无法直接访问该域名替代的IP地址对应的计算机。因此，在获取到一个域名时，需要通过域名解析流程，将获取的域名转换为IP地址；利用得到的IP地址访问该IP地址对应的计算机。
域名解析一般依靠域名服务(英文：Domain Name Service；缩写：DNS)系统实现将域名映射为IP地址。域名服务系统是一种基于TCP/IP应用程序的分布式数据库，提供主机名称和IP地址之间的转换。一般包含公共DNS和权威DNS。
其中，公共DNS在接收到域名查询请求时，查询本地缓存的解析结果；若查询到该域名查询请求中包含的域名对应的解析结果，则将查询到的解析结果返回给用户；若尚未查询到该域名查询请求中包含的域名对应的解析结果，则将待查询的域名携带在查询请求中发送给上一层的DNS(例如：本地DNS)，请求上一层的DNS对该查询请求中包含的域名进行解析。上一层的DNS在接收到该查询请求时，确定待查询的域名是否能够被解析，若能够被直接解析，则返回解析结果；若不能够被直接解析，则通过查询本地缓存的域名解析结果确定是否可以确定该域名对应的解析结果。
在尚未查询到该域名对应的解析结果时，则将待查询的域名携带在查询请求中发送给再上一层的DNS，依次执行上述操作，直至查询到该域名对应的解析结果时结束操作。
权威DNS是指经过授权对域名进行解析的服务器，同时具备将解析结果授权给其他DNS的功能。例如：域名com的顶级服务器可以授权域名ABC.com的权威服务器为NS.ABC.com。授权DNS将解析结果发送给公共DNS，使得公共DNS将接收到的解析结果存储在本地。
但是，在实际应用中，由于各个公共DNS获取权威DNS的解析结果的时间不同，导致权威DNS得到的解析结果在不同公共DNS上的生效时间不同，存在一定的延迟，大大降低公共DNS进行域名解析的解析效率。
发明内容
有鉴于此，本申请实施例提供了一种域名解析的同步方法和设备，用于解决目前公共DNS进行域名解析存在的解析效率低的问题。
一种域名解析的同步方法，包括：
接收权威域名服务DNS设备发送的解析结果，其中，所述解析结果是在所述权威DNS设备内部缓存的解析结果发生更新后发送的；
将接收到的所述解析结果发送给不同的公共DNS设备。
一种域名解析的同步设备，包括：
接收单元，用于接收权威域名服务DNS设备发送的解析结果，其中，所述解析结果是在所述权威DNS设备内部缓存的解析结果发生更新后发送的；
发送单元，用于将接收到的所述解析结果发送给不同的公共DNS设备。
本申请有益效果如下：
本申请实施例接收权威域名服务DNS设备发送的解析结果，所述解析结果是在所述权威DNS设备内部缓存的解析结果发生更新后发送的；将接收到
的所述解析结果发送给不同的公共DNS设备。这样，当权威DNS设备解析域名产生新的解析结果时，通过权威DNS设备与公共DNS设备之间的第三设备，将在权威DNS设备中新生效的解析结果发送给公共DNS设备，确保公共DNS设备缓存中生效的解析结果与权威DNS设备中生效的解析结果一致，避免了由于公共DNS设备中缓存刷新时间的不一致使得解析结果生效时间出现延迟的问题，有效地提升公共DNS设备进行域名解析的解析效率。
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简要介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域的普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例提供的一种域名解析的同步方法的流程示意图；
图2为本申请实施例提供的一种域名解析的同步设备的结构示意图；
图3为本申请实施例提供的一种域名解析的同步系统的结构示意图。
为了实现本申请目的，本申请实施例提供了一种域名解析的同步方法和设备，接收权威域名服务DNS设备发送的解析结果，所述解析结果是在所述权威DNS设备内部缓存的解析结果发生更新后发送的；将接收到的所述解析结果发送给不同的公共DNS设备。这样，当权威DNS设备解析域名产生新的解析结果时，通过权威DNS设备与公共DNS设备之间的第三设备，将在权威DNS设备中新生效的解析结果发送给公共DNS设备，确保公共DNS设备缓存中生效的解析结果与权威DNS设备中生效的解析结果一致，避免了由于公共DNS设备中缓存刷新时间的不一致使得解析结果生效时间出现延迟的问题，有效地提升公共DNS设备进行域名解析的解析效率。
下面结合说明书附图对本申请各个实施例作进一步地详细描述。显然，所
描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本申请保护的范围。
图1为本申请实施例提供的一种域名解析的同步方法的流程示意图。所述方法可以如下所述。本申请实施例的执行主体可以是一个应用客户端，也可以是一个第三方服务器，这里不做限定。
步骤101：第三方服务器接收权威DNS设备发送的解析结果。
其中，所述解析结果是在所述权威DNS设备内部缓存的解析结果发生更新后发送的。
在步骤101中，第三方服务器分别可以与权威DNS设备进行信息交互，也可以与公共DNS设备进行信息交互。
例如：第三方服务器利用超文本传输协议(英文：Hypertext Transfer Protocol；缩写：HTTP)与权威DNS设备进行信息交互；以及利用HTTP与公共DNS设备进行信息交互。
一旦权威DNS设备中发生解析结果更新，那么权威DNS设备将更新后的解析结果主动发送给第三方服务器。
此外，当第三方服务器获取待解析的域名时，将所述待解析的域名携带在解析生产请求中发送给权威DNS设备。
其中，所述解析生产请求用于请求所述权威DNS设备对所述待解析的域名进行解析并返回解析结果。
具体地，第三方服务器在接收到的待解析的域名时，将所述待解析的域名携带在解析生产请求中发送给权威DNS设备，以请求权威DNS设备对所述待解析的域名进行解析并返回解析结果。
具体地，第三方服务器在接收到的待解析的域名时，向权威DNS设备发送解析结果查询请求，该解析结果查询请求中包含待解析的域名，该解析结果查询请求用于确定接收到的待解析的域名是否存在对应的解析结果。
在权威DNS设备确定该待解析的域名不存在对应的解析结果时，将查询结果发送给第三方服务器，此时，第三方服务器将所述待解析的域名携带在解析生产请求中发送给权威DNS设备。
权威DNS设备在接收到解析生产请求时，对该待解析的域名进行解析，得到该待解析的域名对应的解析结果，并更新缓存中的解析结果。
此时，权威DNS设备将待解析的域名对应的解析结果发送给第三方服务器。
除此之外，由于权威DNS设备在接收到解析生产请求时，对待解析的域名进行解析，得到该待解析的域名对应的解析结果，并对内部缓存的解析结果进行了更新，那么权威DNS设备可以只将待解析的域名对应的解析结果发送给第三方服务器，也可以将更新后的解析结果发送给第三方服务器。
也就是说，第三方服务器发送的解析生产请求可以视为权威DNS设备向第三方服务器发送解析结果的触发条件。
需要说明的是，权威DNS设备向第三方服务器发送的解析结果可以是当前生效的解析结果，也可以是设定时间范围内生效的解析结果。
此外，第三方服务器接收所述权威DNS设备发送的解析结果的方式还可以是：
第三方服务器实时向所述权威DNS设备发送查询请求。
其中，所述查询请求用于请求所述权威DNS设备发送更新后的解析结果。
第三方服务器接收所述权威DNS设备发送的查询结果。
其中，所述查询结果中包含所述权威DNS设备最新更新的解析结果。
需要说明的是，“最新更新的解析结果”可以理解为距离所述权威DNS设备接收到查询请求的时间最近的一个更新操作后的解析结果。
步骤102：第三方服务器将接收到的所述解析结果发送给不同的公共DNS设备。
在步骤102中，第三方服务器在接收到权威DNS设备发送的解析结果时，
利用HTTP将接收到的所述解析结果发送给不同的公共DNS设备。
这样，对于公共DNS设备内部缓存中的解析结果，更新这些解析结果不再依赖于设定的更新时间，而是根据第三方服务器实时获取的权威DNS设备更新的解析结果进行实时更新，确保公共DNS设备缓存中生效的解析结果与权威DNS设备中生效的解析结果一致，避免了由于公共DNS设备中缓存刷新时间的不一致使得解析结果的生效时间出现延迟的问题，有效地提升公共DNS进行域名解析的解析效率。
可选地，在将接收到的所述解析结果发送给不同的公共DNS设备时，所述方法还包括：
将接收到的所述解析结果发送给每一个公共DNS设备对应的客户端设备，使所述客户端设备将接收到的所述解析结果存储在本地。
具体地，将接收到的所述解析结果发送给每一个公共DNS设备对应的客户端设备，包括：
向每一个公共DNS设备对应的客户端设备发送心跳数据包。
其中，所述心跳数据包用于确定所述客户端设备是否在线。
在第一设定时间范围内接收到所述客户端设备发送的响应数据包时，将接收到的所述解析结果发送给所述客户端设备。
在第一设定时间范围内尚未接收到所述客户端设备发送的响应数据包时，所述方法还包括：
定时向所述客户端设备发送心跳数据包，并在接收到所述客户端设备发送的响应数据包时，将第二设定时间范围内接收到的所述解析结果发送给所述客户端设备。
需要说明的是，第一设定时间范围可以根据心跳数据包的有效时间进行确定，也可以根据实际需要确定；第二设定时间范围要比第一设定时间范围大。
也就意味着，当确定客户端设备不在线时，定时向所述客户端设备发送心跳数据包，截止到再接收到所述客户端设备发送的响应数据包时，第三方服务
器可能多次接收到权威DNS设备发送的解析结果，因此，第三方服务器可以将从客户端设备不在线到客户端设备在线期间的解析结果一并发送给客户端设备，以保证客户端设备内部的解析结果与权威DNS设备内的解析结果保持一致。
通过本申请实施例的方案，接收权威域名服务DNS设备发送的解析结果，所述解析结果是在所述权威DNS设备内部缓存的解析结果发生更新后发送的；将接收到的所述解析结果发送给不同的公共DNS设备。这样，当权威DNS设备解析域名产生新的解析结果时，通过权威DNS设备与公共DNS设备之间的第三设备，将在权威DNS设备中新生效的解析结果发送给公共DNS设备，确保公共DNS设备缓存中生效的解析结果与权威DNS设备中生效的解析结果一致，避免了由于公共DNS设备中缓存刷新时间的不一致使得解析结果生效时间出现延迟的问题，有效地提升公共DNS设备进行域名解析的解析效率。
图2为本申请实施例提供的一种域名解析的同步设备的结构示意图。所述同步设备包括：接收单元21和发送单元22，其中：
接收单元21，用于接收权威域名服务DNS设备发送的解析结果，其中，所述解析结果是在所述权威DNS设备内部缓存的解析结果发生更新后发送的；
发送单元22，用于将接收到的所述解析结果发送给不同的公共DNS设备。
可选地，所述发送单元23，还用于在将接收到的所述解析结果发送给不同的公共DNS设备时，将接收到的所述解析结果发送给每一个公共DNS设备对应的客户端设备，使所述客户端设备将接收到的所述解析结果存储在本地。
具体地，所述发送单元23，具体用于向每一个公共DNS设备对应的客户端设备发送心跳数据包，其中，所述心跳数据包用于确定所述客户端设备是否在线；
在第一设定时间范围内接收到所述客户端设备发送的响应数据包时，将接收到的所述解析结果发送给所述客户端设备。
具体地，所述发送单元23，还用于在第一设定时间范围内尚未接收到所述
客户端设备发送的响应数据包时，定时向所述客户端设备发送心跳数据包，并在接收到所述客户端设备发送的响应数据包时，将第二设定时间范围内接收到的所述解析结果发送给所述客户端设备。
可选地，所述同步设备还包括：获取单元23，其中：
所述获取单元23，用于获取待解析的域名，并将所述待解析的域名携带在解析生产请求中发送给权威域名服务DNS设备，其中，所述解析生产请求用于请求所述权威DNS设备对所述待解析的域名进行解析并返回解析结果；
所述接收单元21，具体用于接收权威DNS设备发送的解析结果，其中，所述解析结果中包含所述待解析的域名对应的解析结果。
需要说明的是，本发明实施例所涉及的同步设备可以通过硬件方式实现，也可以通过软件方式实现，这里不做限定。
图3为本申请实施例提供的一种域名解析的同步系统的结构示意图。所述同步系统包括：权威DNS设备31、公共DNS设备32、同步设备33和与所述公共DNS设备对应的客户端设备34，其中：
所述权威DNS设备31，用于将更新后的解析结果发送给同步设备33；
所述同步设备33，用于接收所述权威DNS设备发送的解析结果，所述解析结果是在所述权威DNS设备内部缓存的解析结果发生更新后发送的，并将接收到的所述解析结果发送给不同的公共DNS设备32。
此外，所述同步设备33，还用于将接收到的所述解析结果发送给每一个公共DNS设备对应的客户端设备34，使所述客户端设备将接收到的所述解析结果存储在本地。
具体地，所述同步设备33，具体用于向每一个公共DNS设备32对应的客户端设备34发送心跳数据包，其中，所述心跳数据包用于确定所述客户端设备34是否在线；
在第一设定时间范围内接收到所述客户端设备34发送的响应数据包时，将接收到的所述解析结果发送给所述客户端设备34。
所述同步设备33，具体用于在第一设定时间范围内尚未接收到所述客户端设备34发送的响应数据包时，定时向所述客户端设备34发送心跳数据包，并在接收到所述客户端设备34发送的响应数据包时，将第二设定时间范围内接收到的所述解析结果发送给所述客户端设备34。
所述同步设备33，还用于在接收权威DNS设备31发送的解析结果之前，获取待解析的域名，并将所述待解析的域名携带在解析生产请求中发送给权威DNS设备31，其中，所述解析生产请求用于请求所述权威DNS设备31对所述待解析的域名进行解析并返回解析结果。
所述同步设备33，具体用于接收权威DNS设备31发送的解析结果，其中，所述解析结果中包含所述待解析的域名对应的解析结果。
当权威DNS设备解析域名产生新的解析结果时，通过权威DNS设备与公共DNS设备之间的同步设备，将在权威DNS设备中新生效的解析结果发送给公共DNS设备，确保公共DNS设备缓存中生效的解析结果与权威DNS设备中生效的解析结果一致，避免了由于公共DNS设备中缓存刷新时间的不一致使得解析结果生效时间出现延迟的问题，有效地提升公共DNS设备进行域名解析的解析效率。
本领域的技术人员应明白，本申请的实施例可提供为方法、装置(设备)、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、装置(设备)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他
可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。
Claims (10)
- 一种域名解析的同步方法，其特征在于，包括：接收权威域名服务DNS设备发送的解析结果，其中，所述解析结果是在所述权威DNS设备内部缓存的解析结果发生更新后发送的；将接收到的所述解析结果发送给不同的公共DNS设备。
- 如权利要求1所述的同步方法，其特征在于，在将接收到的所述解析结果发送给不同的公共DNS设备时，所述方法还包括：将接收到的所述解析结果发送给每一个公共DNS设备对应的客户端设备，使所述客户端设备将接收到的所述解析结果存储在本地。
- 如权利要求2所述的同步方法，其特征在于，将接收到的所述解析结果发送给每一个公共DNS设备对应的客户端设备，包括：向每一个公共DNS设备对应的客户端设备发送心跳数据包，其中，所述心跳数据包用于确定所述客户端设备是否在线；在第一设定时间范围内接收到所述客户端设备发送的响应数据包时，将接收到的所述解析结果发送给所述客户端设备。
- 如权利要求3所述的同步方法，其特征在于，在第一设定时间范围内尚未接收到所述客户端设备发送的响应数据包时，所述方法还包括：定时向所述客户端设备发送心跳数据包，并在接收到所述客户端设备发送的响应数据包时，将第二设定时间范围内接收到的所述解析结果发送给所述客户端设备。
- 如权利要求1至4任一项所述的同步方法，其特征在于，在接收权威DNS设备发送的解析结果之前，所述方法还包括：获取待解析的域名，并将所述待解析的域名携带在解析生产请求中发送给权威域名服务DNS设备，其中，所述解析生产请求用于请求所述权威DNS设备对所述待解析的域名进行解析并返回解析结果；接收权威DNS设备发送的解析结果，包括：接收权威DNS设备发送的解析结果，其中，所述解析结果中包含所述待解析的域名对应的解析结果。
- 一种域名解析的同步设备，其特征在于，包括：接收单元，用于接收权威域名服务DNS设备发送的解析结果，其中，所述解析结果是在所述权威DNS设备内部缓存的解析结果发生更新后发送的；发送单元，用于将接收到的所述解析结果发送给不同的公共DNS设备。
- 如权利要求6所述的同步设备，其特征在于，所述发送单元，还用于在将接收到的所述解析结果发送给不同的公共DNS设备时，将接收到的所述解析结果发送给每一个公共DNS设备对应的客户端设备，使所述客户端设备将接收到的所述解析结果存储在本地。
- 如权利要求7所述的同步设备，其特征在于，所述发送单元，具体用于向每一个公共DNS设备对应的客户端设备发送心跳数据包，其中，所述心跳数据包用于确定所述客户端设备是否在线；在第一设定时间范围内接收到所述客户端设备发送的响应数据包时，将接收到的所述解析结果发送给所述客户端设备。
- 如权利要求8所述的同步设备，其特征在于，所述发送单元，还用于在第一设定时间范围内尚未接收到所述客户端设备发送的响应数据包时，定时向所述客户端设备发送心跳数据包，并在接收到所述客户端设备发送的响应数据包时，将第二设定时间范围内接收到的所述解析结果发送给所述客户端设备。
- 如权利要求6至9任一项所述的同步设备，其特征在于，所同步设备还包括：获取单元，其中：所述获取单元，用于获取待解析的域名，并将所述待解析的域名携带在解析生产请求中发送给权威域名服务DNS设备，其中，所述解析生产请求用于请求所述权威DNS设备对所述待解析的域名进行解析并返回解析结果；所述接收单元，具体用于接收权威DNS设备发送的解析结果，其中，所 述解析结果中包含所述待解析的域名对应的解析结果。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510221614.7A CN106210158B (zh) | 2015-05-04 | 2015-05-04 | 一种域名解析的同步方法和设备 |
| CN201510221614.7 | 2015-05-04 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2016177276A1 true WO2016177276A1 (zh) | 2016-11-10 |
Family
ID=57217555
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2016/079809 Ceased WO2016177276A1 (zh) | 2015-05-04 | 2016-04-21 | 一种域名解析的同步方法和设备 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN106210158B (zh) |
| WO (1) | WO2016177276A1 (zh) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109922120A (zh) * | 2018-12-10 | 2019-06-21 | 网宿科技股份有限公司 | 提高dns可用性的方法及终端 |
| CN111510514A (zh) * | 2020-03-13 | 2020-08-07 | 视联动力信息技术股份有限公司 | 域名处理方法、装置、电子设备及存储介质 |
| CN112689030A (zh) * | 2020-12-31 | 2021-04-20 | 网根(南京)网络中心有限公司 | Dns缓存更新方法及系统 |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113301173A (zh) * | 2020-06-09 | 2021-08-24 | 阿里巴巴集团控股有限公司 | 域名更新系统及方法、消息转发方法、服务器 |
| CN114466073A (zh) * | 2021-12-24 | 2022-05-10 | 互联网域名系统北京市工程研究中心有限公司 | 适用局域网范围的快速更新dns缓存记录的方法及装置 |
| CN116405460A (zh) * | 2023-05-09 | 2023-07-07 | 北京有竹居网络技术有限公司 | 用于内容分发网络的域名解析方法、装置、电子设备及存储介质 |
| CN116436836B (zh) * | 2023-06-13 | 2023-09-01 | 阿里巴巴（中国）有限公司 | 域名数据同步检测方法、装置及设备 |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8200842B1 (en) * | 2006-10-25 | 2012-06-12 | Cellco Partnership | Automatic traffic control using dynamic DNS update |
| CN103905572A (zh) * | 2012-12-26 | 2014-07-02 | 中国移动通信集团公司 | 域名解析请求的处理方法及装置 |
| CN104184775A (zh) * | 2013-05-27 | 2014-12-03 | 电子科技大学 | 一种基于内容发布网络(cdn)的域名解析服务模型 |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101714991B (zh) * | 2009-10-30 | 2012-06-20 | 清华大学 | 心跳机制的实现方法 |
| US8924519B2 (en) * | 2009-11-03 | 2014-12-30 | Microsoft Corporation | Automated DNS configuration with local DNS server |
| CN101841409B (zh) * | 2010-01-26 | 2013-04-24 | 中国科学院计算机网络信息中心 | 实现dns区创建同步的方法、服务器以及域名系统 |
| CN102137174B (zh) * | 2010-12-29 | 2013-10-09 | 华为技术有限公司 | 域名系统缓存的方法、授权域名服务器、缓存域名服务器 |
| CN103167047A (zh) * | 2011-12-12 | 2013-06-19 | 工业和信息化部电信传输研究所 | 一种dns服务器资源记录动态更新的方法 |
| CN103685585B (zh) * | 2012-09-07 | 2016-11-23 | 中国科学院计算机网络信息中心 | 一种高可靠的dns数据更新方法及系统 |
| CN103024094B (zh) * | 2012-11-15 | 2015-07-22 | 中国科学院计算机网络信息中心 | 一种安全可靠的dns区文件信息下发更新方法及系统 |
| CN103856569B (zh) * | 2012-11-28 | 2018-09-11 | 方正宽带网络服务有限公司 | 一种同步域名系统资源信息的方法及设备 |
| CN103905574B (zh) * | 2012-12-27 | 2017-09-08 | 中国移动通信集团公司 | 一种dns业务访问方法、dns数据同步方法及设备 |
-
2015
- 2015-05-04 CN CN201510221614.7A patent/CN106210158B/zh active Active
-
2016
- 2016-04-21 WO PCT/CN2016/079809 patent/WO2016177276A1/zh not_active Ceased
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8200842B1 (en) * | 2006-10-25 | 2012-06-12 | Cellco Partnership | Automatic traffic control using dynamic DNS update |
| CN103905572A (zh) * | 2012-12-26 | 2014-07-02 | 中国移动通信集团公司 | 域名解析请求的处理方法及装置 |
| CN104184775A (zh) * | 2013-05-27 | 2014-12-03 | 电子科技大学 | 一种基于内容发布网络(cdn)的域名解析服务模型 |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109922120A (zh) * | 2018-12-10 | 2019-06-21 | 网宿科技股份有限公司 | 提高dns可用性的方法及终端 |
| CN111510514A (zh) * | 2020-03-13 | 2020-08-07 | 视联动力信息技术股份有限公司 | 域名处理方法、装置、电子设备及存储介质 |
| CN111510514B (zh) * | 2020-03-13 | 2022-04-05 | 视联动力信息技术股份有限公司 | 域名处理方法、装置、电子设备及存储介质 |
| CN112689030A (zh) * | 2020-12-31 | 2021-04-20 | 网根(南京)网络中心有限公司 | Dns缓存更新方法及系统 |
| CN112689030B (zh) * | 2020-12-31 | 2023-01-20 | 网根(南京)网络中心有限公司 | Dns缓存更新方法及系统 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106210158B (zh) | 2020-03-27 |
| CN106210158A (zh) | 2016-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2016177276A1 (zh) | 一种域名解析的同步方法和设备 | |
| US10225231B2 (en) | Method and server of remote information query | |
| Callahan et al. | On modern DNS behavior and properties | |
| EP3557841A1 (en) | Dns attack defense method, apparatus and system | |
| CN103973834B (zh) | 一种基于家庭网关的dns域名解析加速方法及装置 | |
| TWI565258B (zh) | 過濾https傳輸內容的系統、方法及裝置 | |
| CN102984286A (zh) | 一种dns服务器的缓存更新方法、装置及系统 | |
| WO2018112944A1 (zh) | 域名解析方法和装置 | |
| JP2013538410A (ja) | ネットワーク環境における要求ルーティング | |
| EP2617178A1 (en) | Method and system for triggering web crawling based on registry data | |
| TW200420031A (en) | Method and apparatus for local IP address translation | |
| CN109067936A (zh) | 一种域名解析的方法及装置 | |
| CN106209486B (zh) | 域名解析生效的检测方法、浏览器、服务端和系统 | |
| CN103685168B (zh) | 一种dns递归服务器的查询请求服务方法 | |
| US8819209B1 (en) | Name server property tracking | |
| WO2012010084A1 (zh) | 一种域名解析方法及装置 | |
| US10659424B2 (en) | Determining status of domain name registration | |
| CN103957289B (zh) | 一种基于复杂网络上的dnssec解析方法 | |
| WO2012092765A1 (zh) | 一种域名系统及其提供负荷均衡的方法 | |
| WO2017000561A1 (zh) | 域名资源记录缓存控制方法及服务器 | |
| WO2017124883A1 (zh) | 一种新型权威域名解析服务方法和装置 | |
| CN105812503A (zh) | 根服务器地址更新方法和一种递归服务器 | |
| CN107071091B (zh) | 一种优化dns域名解析的实现方法 | |
| CN110674098A (zh) | 一种分布式文件系统中的域名解析方法 | |
| WO2017000669A1 (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: 16789270 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 16789270 Country of ref document: EP Kind code of ref document: A1 |