CN111614783A - Domain name resolution emergency response method and system - Google Patents
Domain name resolution emergency response method and system Download PDFInfo
- Publication number
- CN111614783A CN111614783A CN202010482096.5A CN202010482096A CN111614783A CN 111614783 A CN111614783 A CN 111614783A CN 202010482096 A CN202010482096 A CN 202010482096A CN 111614783 A CN111614783 A CN 111614783A
- Authority
- CN
- China
- Prior art keywords
- domain name
- name resolution
- emergency response
- node
- information
- 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.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/2895—Intermediate processing functionally located close to the data provider application, e.g. reverse proxies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
Abstract
The invention discloses a domain name resolution emergency response method and system. The method comprises the following steps: the domain name resolution emergency response node captures a domain name resolution request message sent by a domain name resolution request node to a domain name resolution server; extracting information in a domain name resolution request message by a domain name resolution emergency response node; when the domain name resolution server can not normally provide domain name resolution service, the domain name resolution emergency response node searches an IP corresponding to the domain name request according to domain name information requested in the extracted domain name resolution request message, adds the IP into the constructed domain name resolution response message, and sends the IP to the domain name resolution request node. The method can ensure that the domain name resolution emergency response node can provide domain name resolution emergency response to the domain name resolution request node instead of the domain name resolution server when the domain name resolution request node cannot obtain domain name resolution service due to the failure of the domain name resolution server, denial of service attack, network failure and the like.
Description
(I) technical field
The invention relates to the technical field of computer networks, in particular to a domain name resolution emergency response method and system.
(II) background of the invention
The domain name system is a distributed database with a hierarchical structure, and can map domain names and IP addresses with each other, so that users can access the Internet more conveniently without remembering IP strings which can be directly read by machines. The domain name resolution server includes a root server, an authoritative server, a recursive server, etc.
When a user accesses the internet service through a domain name, the client encapsulates the domain name to be analyzed into a domain name analysis request message and sends the domain name analysis request message to the designated domain name analysis recursive server. And after inquiring the IP address corresponding to the domain name through the local cache, the recursion server returns the IP address to the client through a domain name resolution response message. If the local cache does not have the IP corresponding to the domain name, the authoritative server of the top-level domain name is inquired from the root server, and then recursive inquiry is carried out on the authoritative server until the IP address corresponding to the domain name is analyzed.
The current domain name resolution server has the safety problem: on one hand, when the normal domain name resolution requests are too many or a denial of service attack occurs, the domain name resolution server processing resources are seriously consumed and network congestion occurs, and the domain name resolution service cannot be normally provided. On the other hand, when the domain name resolution server fails, or the network where the domain name resolution server is located fails, the domain name resolution server cannot normally provide domain name resolution service. When the above security problem occurs, the domain name resolution request node cannot obtain the domain name resolution service.
Disclosure of the invention
In order to solve the above problem, embodiments of the present invention provide a domain name resolution emergency response method and system.
In a first aspect, an embodiment of the present invention provides a domain name resolution emergency response method, including: the domain name resolution emergency response node captures a domain name resolution request message sent by a domain name resolution request node to a domain name resolution server; extracting information in a domain name resolution request message by a domain name resolution emergency response node; when the domain name resolution server can not normally provide domain name resolution service, the domain name resolution emergency response node searches an IP corresponding to the domain name request according to domain name information requested in the extracted domain name resolution request message, adds the IP into the constructed domain name resolution response message, and sends the IP to the domain name resolution request node.
Further, a data link layer header, a network layer header, a transport layer header and application layer domain name resolution request information are extracted from the domain name resolution request message.
Further, the domain name resolution emergency response node synchronizes domain name information with the domain name resolution server in each timeout period, and the domain name information is used for constructing a domain name resolution response message.
Further, according to the information in the domain name resolution request message extracted by the domain name resolution emergency response node, the construction of the corresponding domain name resolution response message comprises:
constructing a data link layer header of a domain name resolution response message;
constructing a network layer header of a domain name resolution response message;
constructing a transmission layer header of a domain name resolution response message;
and constructing domain name resolution application layer data of the domain name resolution response message, and adding the searched IP corresponding to the requested domain name into the domain name resolution application layer data according to the domain name information synchronized with the domain name resolution server and the requested domain name information.
In a second aspect, an embodiment of the present invention provides a domain name resolution emergency response system, including: the network flow capturing module is used for capturing a domain name resolution request message sent to a domain name resolution server by a domain name resolution request node in network flow; the domain name resolution request information extraction module is used for extracting information in the domain name resolution request message; and the domain name resolution response message construction module is used for searching the IP corresponding to the domain name request according to the domain name information requested in the extracted domain name resolution request message by the domain name resolution emergency response node when the domain name resolution server can not normally provide the domain name resolution service, adding the IP into the constructed domain name resolution response message and sending the IP to the domain name resolution request node.
In a third aspect, an embodiment of the present invention provides an electronic device, which includes a memory, a processor, and a computer program that is stored in the memory and is executable on the processor, where the processor executes the computer program to implement the steps of the domain name resolution emergency response method according to the first aspect of the present invention.
In a fourth aspect, an embodiment of the present invention provides a non-transitory computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the domain name resolution emergency response method according to the first aspect of the present invention.
According to the domain name resolution emergency response method and system provided by the embodiment of the invention, the domain name resolution emergency response node synchronizes the domain name information with the domain name resolution server in each timeout period, so that the consistency between the domain name resolution response data and the domain name resolution server before the fault occurs can be ensured. The domain name resolution emergency response node constructs a domain name resolution response message according to a data link layer header, a network layer header, a transmission layer header and requested domain name information in the domain name resolution request message, and can ensure that the domain name resolution request node normally receives the domain name resolution response message and obtains a resolution response corresponding to the domain name request. When the domain name resolution server fails to provide the domain name resolution service normally due to the faults of the domain name resolution server, denial of service attack and network faults, the domain name resolution emergency response node can replace the domain name resolution server to achieve the domain name resolution emergency response service, and the domain name resolution response service is provided for the domain name resolution request node.
(IV) description of the drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
Fig. 1 is a flowchart of a domain name resolution emergency response method according to an embodiment of the present invention;
fig. 2 is a structural diagram of a domain name resolution emergency response system according to an embodiment of the present invention;
fig. 3 is a schematic physical structure diagram of an electronic device according to an embodiment of the present invention.
(V) detailed description of the preferred embodiments
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Because the current domain name resolution server has security risks: on one hand, when the normal domain name resolution requests are too many or a denial of service attack occurs, the domain name resolution server processing resources are seriously consumed and network congestion occurs, and the domain name resolution service cannot be normally provided. On the other hand, when the domain name resolution server fails, or the network where the domain name resolution server is located fails, the domain name resolution server cannot normally provide domain name resolution service. When the above security problem occurs, the domain name resolution request node cannot obtain the domain name resolution service.
The invention provides a domain name resolution emergency response method, which solves the problem that a domain name resolution request node cannot obtain domain name resolution service when the domain name resolution server cannot normally provide the domain name resolution service due to the reasons of domain name resolution server failure, denial of service attack, network failure and the like. The domain name resolution emergency response node can replace a domain name resolution server to realize domain name resolution emergency response service and provide domain name resolution response for the domain name resolution request node.
Fig. 1 is a flowchart of a domain name resolution emergency response method according to an embodiment of the present invention, and as shown in fig. 1, the embodiment of the present invention provides a domain name resolution emergency response method, including:
101. and the domain name resolution emergency response node captures a domain name resolution request message sent to the domain name resolution server by the domain name resolution request node.
The domain name resolution emergency response node captures a network data message through a network interface, and network flow can flow to the network interface of the domain name resolution emergency response node in a drainage mode, a light splitting mode and the like. Because the domain name resolution protocol specifies that port number 53 is used for domain name resolution service, the domain name resolution request packet is identified by using the target port 53 as a decision condition, where: the source IP of the domain name resolution request message is a domain name resolution request node, and the destination IP is a domain name resolution server.
102. And extracting the information in the domain name resolution request message by the domain name resolution emergency response node.
The domain name resolution request message comprises data link layer, network layer, transmission layer and application layer data, and the protocols of the layers are regulated by standard protocols to form the message format. The domain name resolution protocol specifies an application layer data format of the domain name resolution request, and realizes extraction of information of the domain name resolution request according to the data format, including but not limited to information of a requested domain name, a CNAME, an A record or an AAAA record.
103. When the domain name resolution server can not normally provide domain name resolution service, the domain name resolution emergency response node searches an IP corresponding to the domain name request according to domain name information requested in the extracted domain name resolution request message, adds the IP into the constructed domain name resolution response message, and sends the IP to the domain name resolution request node.
The domain name resolution emergency response node can timely acquire the information that the domain name resolution server cannot normally provide domain name resolution service through passive notification, periodic detection and other modes. Constructing each layer of data of the corresponding analysis message according to the information of the data link layer, the network layer and the transmission layer in the domain name analysis request message, searching the IP corresponding to the domain name request according to the domain name information requested in the extracted domain name analysis request message, and adding the IP into the constructed domain name analysis response message.
Based on the content of the foregoing embodiment, as an optional embodiment, the domain name resolution request packet is extracted with a data link layer header, a network layer header, a transport layer header, and application layer domain name resolution request information.
Because the standard protocol stipulates the message formats of a link layer, a network layer, a transmission layer and a domain name resolution application layer protocol, corresponding information of each layer can be extracted for message construction of subsequent domain name resolution response.
Based on the content of the foregoing embodiment, as an optional embodiment, the domain name resolution emergency response node synchronizes domain name information with the domain name resolution server at each timeout period, where the domain name information is used to construct a domain name resolution response packet.
The domain name resolution emergency response node synchronizes the domain name information with the domain name resolution server within the overtime period, so that the domain name resolution emergency response node is consistent with the domain name information stored by the domain name resolution server, and the problem that a domain name resolution response message is constructed by adopting outdated domain name information is avoided.
Based on the content of the foregoing embodiment, as an optional embodiment, according to the information in the domain name resolution request message extracted by the domain name resolution emergency response node, the constructing of the corresponding domain name resolution response message includes: constructing a data link layer header of a domain name resolution response message; constructing a network layer header of a domain name resolution response message; constructing a transmission layer header of a domain name resolution response message; and constructing domain name resolution application layer data of the domain name resolution response message, and adding the searched IP corresponding to the requested domain name into the domain name resolution application layer data according to the domain name information synchronized with the domain name resolution server and the requested domain name information.
In order to enable the domain name resolution response message constructed by the domain name resolution emergency response node to be transmitted to and received by the domain name resolution request node, a data link layer header, a network layer header and a transmission layer header need to be constructed according to information in the domain name resolution request message, and a domain name resolution application layer data is constructed according to an IP corresponding to a requested domain name.
Fig. 2 is a structural diagram of a domain name resolution emergency response system according to an embodiment of the present invention, and as shown in fig. 2, the domain name resolution emergency response system includes: a network traffic capturing module 201, a domain name resolution request information extracting module 202 and a domain name resolution response message constructing module 203. The network traffic capturing module 201 is configured to capture a domain name resolution request packet sent by a domain name resolution request node to a domain name resolution server in network traffic; the domain name resolution request information extraction module 202 is configured to extract information in the domain name resolution request message; the domain name resolution response message construction module 203 is configured to, when the domain name resolution server cannot normally provide the domain name resolution service, find, by the domain name resolution emergency response node, an IP corresponding to the domain name request according to domain name information requested in the extracted domain name resolution request message, add the IP to the constructed domain name resolution response message, and send the IP to the domain name resolution request node.
The system embodiment provided in the embodiments of the present invention is for implementing the above method embodiments, and for details of the process and the details, reference is made to the above method embodiments, which are not described herein again.
The domain name resolution emergency response system provided by the embodiment of the invention identifies the domain name resolution network message through a 53 port of a domain name resolution protocol by capturing network flow, and extracts information of each layer through message formats of a link layer, a network layer, a transmission layer and a domain name resolution application layer protocol specified by a standard protocol. When the domain name resolution server can not normally provide domain name resolution service, the IP corresponding to the domain name request is searched, a data link layer header, a network layer header and a transmission layer header are constructed according to the information in the extracted domain name resolution request message, and meanwhile, domain name resolution application layer data are constructed according to the IP corresponding to the requested domain name and are sent to a domain name resolution request node.
Fig. 3 is a schematic entity structure diagram of an electronic device according to an embodiment of the present invention, and as shown in fig. 3, the electronic device may include: a processor (processor)301, a communication Interface (communication Interface)302, a memory (memory)303 and a bus 304, wherein the processor 301, the communication Interface 302 and the memory 303 complete communication with each other through the bus 304. The communication interface 302 may be used for information transfer of an electronic device. Processor 301 may call logic instructions in memory 303 to perform a method comprising: the domain name resolution emergency response node captures a domain name resolution request message sent by a domain name resolution request node to a domain name resolution server; extracting information in a domain name resolution request message by a domain name resolution emergency response node; when the domain name resolution server can not normally provide domain name resolution service, the domain name resolution emergency response node searches an IP corresponding to the domain name request according to domain name information requested in the extracted domain name resolution request message, adds the IP into the constructed domain name resolution response message, and sends the IP to the domain name resolution request node.
In addition, the logic instructions in the memory 303 may be implemented in the form of software functional units and stored in a computer readable storage medium when the logic instructions are sold or used as independent products. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the above-described method embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
In another aspect, an embodiment of the present invention further provides a non-transitory computer-readable storage medium, on which a computer program is stored, where the computer program is implemented to perform the transmission method provided in the foregoing embodiments when executed by a processor, and for example, the method includes: the domain name resolution emergency response node captures a domain name resolution request message sent by a domain name resolution request node to a domain name resolution server; extracting information in a domain name resolution request message by a domain name resolution emergency response node; when the domain name resolution server can not normally provide domain name resolution service, the domain name resolution emergency response node searches an IP corresponding to the domain name request according to domain name information requested in the extracted domain name resolution request message, adds the IP into the constructed domain name resolution response message, and sends the IP to the domain name resolution request node.
The above-described system embodiments are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (7)
1. A domain name resolution emergency response method is characterized by comprising the following steps:
the domain name resolution emergency response node captures a domain name resolution request message sent by a domain name resolution request node to a domain name resolution server;
extracting information in a domain name resolution request message by a domain name resolution emergency response node;
when the domain name resolution server can not normally provide domain name resolution service, the domain name resolution emergency response node searches an IP corresponding to the domain name request according to domain name information requested in the extracted domain name resolution request message, adds the IP into the constructed domain name resolution response message, and sends the IP to the domain name resolution request node.
2. The domain name resolution emergency response method according to claim 1, wherein a data link layer header, a network layer header, a transport layer header, and application layer domain name resolution request information are extracted for the domain name resolution request message.
3. The domain name resolution emergency response method according to claim 1, wherein the domain name resolution emergency response node synchronizes domain name information with the domain name resolution server at each timeout period, the domain name information being used to construct a domain name resolution response packet.
4. The domain name resolution emergency response method according to claim 1, wherein according to the information in the domain name resolution request message extracted by the domain name resolution emergency response node, the construction of the corresponding domain name resolution response message comprises:
constructing a data link layer header of a domain name resolution response message;
constructing a network layer header of a domain name resolution response message;
constructing a transmission layer header of a domain name resolution response message;
and constructing domain name resolution application layer data of the domain name resolution response message, and adding the searched IP corresponding to the requested domain name into the domain name resolution application layer data according to the domain name information synchronized with the domain name resolution server and the requested domain name information.
5. A domain name resolution emergency response system, comprising:
the network flow capturing module is used for capturing a domain name resolution request message sent to a domain name resolution server by a domain name resolution request node in network flow;
the domain name resolution request information extraction module is used for extracting information in the domain name resolution request message;
and the domain name resolution response message construction module is used for searching the IP corresponding to the domain name request according to the domain name information requested in the extracted domain name resolution request message by the domain name resolution emergency response node when the domain name resolution server can not normally provide the domain name resolution service, adding the IP into the constructed domain name resolution response message and sending the IP to the domain name resolution request node.
6. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the program performs the steps of the domain name resolution emergency response method according to any of claims 1 to 4.
7. A non-transitory computer readable storage medium having stored thereon a computer program, wherein the computer program when executed by a processor implements the steps of the domain name resolution emergency response method according to any of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010482096.5A CN111614783A (en) | 2020-05-29 | 2020-05-29 | Domain name resolution emergency response method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010482096.5A CN111614783A (en) | 2020-05-29 | 2020-05-29 | Domain name resolution emergency response method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111614783A true CN111614783A (en) | 2020-09-01 |
Family
ID=72201519
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010482096.5A Pending CN111614783A (en) | 2020-05-29 | 2020-05-29 | Domain name resolution emergency response method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111614783A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100049872A1 (en) * | 2008-08-25 | 2010-02-25 | Google Inc. | Parallel, Side-Effect Based DNS Pre-Caching |
| CN101815105A (en) * | 2010-03-25 | 2010-08-25 | 上海交通大学 | Domain name resolution service system with intelligent buffer and service method thereof |
| CN102025794A (en) * | 2010-01-22 | 2011-04-20 | 中国移动通信集团北京有限公司 | Domain name resolution method, DNS (Domain Name Server) server and system |
| CN106550056A (en) * | 2015-09-18 | 2017-03-29 | 中国移动通信集团江苏有限公司 | A kind of domain name analytic method and device |
| CN108449444A (en) * | 2018-03-29 | 2018-08-24 | 江苏省未来网络创新研究院 | Local data transport method, self-loopa domain name analysis system and method |
| CN109474718A (en) * | 2018-12-29 | 2019-03-15 | 杭州迪普科技股份有限公司 | Domain name analytic method and device |
| CN110113447A (en) * | 2019-06-27 | 2019-08-09 | 网易（杭州）网络有限公司 | Domain name analytic method and device |
-
2020
- 2020-05-29 CN CN202010482096.5A patent/CN111614783A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100049872A1 (en) * | 2008-08-25 | 2010-02-25 | Google Inc. | Parallel, Side-Effect Based DNS Pre-Caching |
| CN102025794A (en) * | 2010-01-22 | 2011-04-20 | 中国移动通信集团北京有限公司 | Domain name resolution method, DNS (Domain Name Server) server and system |
| CN101815105A (en) * | 2010-03-25 | 2010-08-25 | 上海交通大学 | Domain name resolution service system with intelligent buffer and service method thereof |
| CN106550056A (en) * | 2015-09-18 | 2017-03-29 | 中国移动通信集团江苏有限公司 | A kind of domain name analytic method and device |
| CN108449444A (en) * | 2018-03-29 | 2018-08-24 | 江苏省未来网络创新研究院 | Local data transport method, self-loopa domain name analysis system and method |
| CN109474718A (en) * | 2018-12-29 | 2019-03-15 | 杭州迪普科技股份有限公司 | Domain name analytic method and device |
| CN110113447A (en) * | 2019-06-27 | 2019-08-09 | 网易（杭州）网络有限公司 | Domain name analytic method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8935419B2 (en) | Filtering device for detecting HTTP request and disconnecting TCP connection | |
| US20120297478A1 (en) | Method and system for preventing dns cache poisoning | |
| US11218437B2 (en) | Method for network traffic forwarding, request sending, and communication acceleration, forwarding server and node server | |
| US10645057B2 (en) | Domain name system identification and attribution | |
| JP5976232B2 (en) | Domain name system and domain name service method based on user information | |
| US20050185658A1 (en) | Gateway apparatus connected to a plurality of networks forming respective different network segments, and program and method for transferring IP packets | |
| EP2725873A1 (en) | Information sending method and gateway | |
| WO2017096888A1 (en) | Method and device for implementing domain name system | |
| CN103685584B (en) | A kind of anti-Domain Hijacking method and system based on tunneling technique | |
| CN106412063A (en) | CDN node detection and resource scheduling system and method in education network | |
| WO2018214853A1 (en) | Method, apparatus, medium and device for reducing length of dns message | |
| CN107959732A (en) | Allow the method and system that domain name is used during network strategy is carried out | |
| CN102833262A (en) | Whois information-based phishing website gathering, identification method and system | |
| CN111314301A (en) | Website access control method and device based on DNS (Domain name Server) analysis | |
| CN103581361A (en) | Domain name resolution proxy method, device and system | |
| CN110708309A (en) | Anti-crawler system and method | |
| CN109413224B (en) | Message forwarding method and device | |
| CN110505300A (en) | A kind of Novel chain type Proxy Method that IP network is mixed with name data network | |
| WO2001033364A1 (en) | Device for searching name of communication node device in communication network | |
| CN107222588A (en) | A kind of method and system of raising DNS availabilities | |
| CN111614783A (en) | Domain name resolution emergency response method and system | |
| KR101645222B1 (en) | Advanced domain name system and management method | |
| Gañán | WHOIS sunset? A primer in Registration Data Access Protocol (RDAP) performance. | |
| CN114710560A (en) | Data processing method and system, proxy equipment and terminal equipment | |
| US20200267064A1 (en) | Action based on advertisement indicator in network packet |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200901 |