CN109561167B - Domain name resolution method and device - Google Patents
Domain name resolution method and device Download PDFInfo
- Publication number
- CN109561167B CN109561167B CN201811423493.4A CN201811423493A CN109561167B CN 109561167 B CN109561167 B CN 109561167B CN 201811423493 A CN201811423493 A CN 201811423493A CN 109561167 B CN109561167 B CN 109561167B
- Authority
- CN
- China
- Prior art keywords
- dns
- domain name
- user equipment
- response message
- target user
- 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.)
- Active
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
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/15—Flow control; Congestion control in relation to multipoint traffic
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
A domain name resolution method and device are disclosed. A domain name resolution method is characterized in that the method adds at least 2 target user equipment and a DNS server into 1 multicast group, and the method comprises the following steps: under the condition that any target user equipment determines that domain name resolution is needed, whether the domain name needing resolution is stored or not is inquired in a domain name resolution result stored in advance locally; the any target user equipment sends a DNS request message to the DNS server under the condition that the DNS request message is not stored in the any target user equipment; the DNS server replies a DNS response message in a multicast mode under the condition of receiving the DNS request message; and under the condition that any target user equipment monitors a multicast DNS response message, acquiring the DNS response message, and updating a locally stored domain name resolution result according to the DNS response message.
Description
Technical Field
The embodiment of the specification relates to the technical field of network communication, in particular to a domain name resolution method and a domain name resolution device.
Background
The DNS (Domain Name System) is a distributed database that maps Domain names and IP addresses of hosts in a network to each other, and makes it easier for people to access the network by facilitating the mapping relationship between a Domain Name that is memorized and input by a person and an IP address that is processed by a computer.
In the prior art, when a user needs to access a certain domain name through user equipment, the user equipment sends a request message to the DNS server, and the DNS server returns a response message including a corresponding IP address or an upstream DNS server to the user equipment according to the stored mapping relationship.
However, in a network environment where there are a lot of similar domain name resolution requirements, each user equipment may send a lot of resolution requests of the same domain name to the DNS server in a short time, and the DNS server responds according to the prior art scheme, which may cause low response efficiency, waste of network bandwidth, and the like.
Disclosure of Invention
In view of this, embodiments of the present specification provide a method and an apparatus for domain name resolution, where the technical solution is as follows:
a domain name resolution method is characterized in that the method adds at least 2 target user equipment and a DNS server into 1 multicast group, and the method comprises the following steps:
under the condition that any target user equipment determines that domain name resolution is needed, whether the domain name needing resolution is stored or not is inquired in a domain name resolution result stored in advance locally;
the any target user equipment sends a DNS request message to the DNS server under the condition that the DNS request message is not stored in the any target user equipment;
the DNS server replies a DNS response message in a multicast mode under the condition of receiving the DNS request message;
and under the condition that any target user equipment monitors a multicast DNS response message, acquiring the DNS response message, and updating a locally stored domain name resolution result according to the DNS response message.
A domain name resolution system, wherein the system comprises at least 2 target user equipments and DNS servers, and the target user equipments and DNS servers join 1 multicast group:
under the condition that any target user equipment determines that domain name resolution is needed, whether the domain name needing resolution is stored or not is inquired in a domain name resolution result stored in advance locally;
the any target user equipment sends a DNS request message to the DNS server under the condition that the DNS request message is not stored in the any target user equipment;
the DNS server replies a DNS response message in a multicast mode under the condition of receiving the DNS request message;
and under the condition that any target user equipment monitors a multicast DNS response message, acquiring the DNS response message, and updating a locally stored domain name resolution result according to the DNS response message.
According to the technical scheme provided by the embodiment of the description, the user equipment with the similar domain name resolution request and the DNS server are added into the same multicast group, and the DNS server returns the DNS response message in a multicast mode, so that each user equipment in the multicast group can request the same domain name resolution result from the DNS server less, and the network bandwidth and the time for the user equipment to access the webpage are saved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of embodiments of the invention.
In addition, any one of the embodiments in the present specification is not required to achieve all of the effects described above.
Drawings
In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the embodiments of the present specification, and other drawings can be obtained by those skilled in the art according to the drawings.
Fig. 1 is a schematic structural diagram of a domain name resolution system according to an embodiment of the present specification;
fig. 2 is a schematic flowchart of a domain name resolution method according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of a domain name resolution device according to an embodiment of the present disclosure;
fig. 4 is another schematic structural diagram of a domain name resolution device in the embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of an apparatus for configuring a device according to an embodiment of the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the embodiments of the present specification, the technical solutions in the embodiments of the present specification will be described in detail below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all the embodiments. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of protection.
To solve the problems in the prior art, the present specification provides a domain name resolution scheme.
In the embodiment of the present specification, the domain name resolution process involves at least 2 target user equipments and a DNS server, and a corresponding system architecture diagram is shown in fig. 1, and includes user equipments 11, 12, … … 1n and a DNS server 20. It should be understood that the user device referred to in this embodiment may be an electronic device such as a mobile phone, a tablet computer, a notebook computer, or the like, which can access a website through a domain name, and a specific form of the DNS server may be a specific server or a server cluster, and the like.
The domain name resolution scheme in the embodiment of the present description may be applied to a network environment where there are a large number of similar domain name resolution requirements, and for 2 or more user equipments with similar domain name resolution requirements, the at least 2 user equipments and the DNS server may be added to one multicast group, and the DNS server sends a DNS response packet by using a multicast technology, and simultaneously, all the user equipments monitor the multicast DNS response packet, thereby saving a large amount of bandwidth by multicast.
In addition, when determining target user equipment (i.e. user equipment with similar domain name resolution requirements) joining the same multicast group, operators can judge whether the similar domain name resolution requirements exist or not, whether the same multicast group is joined or not, and the like according to the domain name resolution requirements of each user and each equipment; or by extracting the characteristics of the domain name resolution requirements, such as frequently-visited websites, frequently-visited webpage types, and the like, determining whether the corresponding user equipment has similar domain name resolution requirements and whether to join the same multicast group or the like through a certain algorithm (such as a training model) of the domain name resolution requirements; the examples in this specification do not limit this.
Fig. 2 is an interaction flowchart of a domain name resolution method provided in an embodiment of this specification, which may specifically include the following steps:
s201, under the condition that any target user equipment determines that domain name resolution is needed, whether the domain name needing resolution is stored or not is inquired in a domain name resolution result stored in advance locally;
the user equipment joining the multicast group can locally pre-store part of commonly used domain name resolution results, and the user equipment determines that the domain name resolution needs to be performed in various situations, for example, the user equipment is a notebook computer, and when a user opens a browser installed in the computer, inputs and accesses a domain name in an address bar, the user equipment can determine that the domain name input by the user needs to be resolved; for another example, the user equipment is a smart phone, and when the user clicks a certain web page link (domain name) through certain application software, the user equipment can determine that the domain name clicked by the user needs to be analyzed, so as to access the web page; and so on.
When the user equipment determines that domain name resolution is required, the user equipment can firstly search in a domain name resolution result which is locally pre-stored to inquire whether the domain name required to be resolved is stored, and if the domain name required to be resolved is stored, the user equipment can directly access the corresponding website by using the pre-stored resolution result without sending a domain name resolution request to the DNS server.
S202, when any target user equipment is inquired that the DNS request message is not stored, the DNS request message is sent to the DNS server;
if the user equipment does not inquire the IP address corresponding to the domain name needing to be analyzed in the domain name analysis result stored locally in advance, a DNS request message can be sent to the DNS server in the same multicast group, and the DNS server is requested to return the domain name analysis result.
S203, the DNS server replies a DNS response message in a multicast mode under the condition of receiving the DNS request message;
in the embodiment of the present description, when receiving the DNS request message, the DNS server may specifically reply to the DNS reply message in a multicast manner in multiple ways.
In a specific implementation manner of the embodiments of this specification, a domain name to be resolved may be determined according to a received DNS request packet, and then, in a domain name resolution result locally stored in a DNS server and currently stored in the DNS server, whether a domain name to be resolved and a resolution result of the domain name have been stored is queried, if the domain name to be resolved and the resolution result of the domain name have been stored are queried, the DNS server may reply a DNS reply packet in a multicast manner, where the reply packet includes a queried domain name resolution result.
If the query is not stored, further determining a DNS query mode of the DNS server system, then obtaining query result information returned to the user equipment according to the determined DNS query mode, and replying the query result information in a multicast mode.
For example, in a case that the DNS query result is determined to be a recursive query, specifically, a DNS resolution request may be first sent to an upstream DNS server according to a received DNS request message, and then, in a case that a DNS resolution result returned by the upstream DNS server is received, a DNS response message including the returned domain name resolution result may be replied in a multicast manner according to the DNS resolution result.
For another example, in a case that the DNS query result is determined to be an iterative query, specifically, an address of an upstream DNS server may be obtained first, and then the obtained address of the upstream DNS server is returned to the target user equipment that sends the DNS request packet, so that the target user equipment queries a domain name resolution result according to the address of the upstream DNS server.
S204, under the condition that any target user equipment monitors the multicast DNS response message, the DNS response message is obtained, and the domain name resolution result stored locally is updated according to the DNS response message.
As described above, in this embodiment of the present specification, each user device joining the same multicast group has similar domain name resolution requirements, so that the DNS server returns the DNS reply message in a multicast form, and each target user device in the multicast group monitors the multicast DNS reply message.
Any user equipment in the multicast group can obtain the multicast DNS response message under the condition of monitoring the message, and update the domain name resolution result of the local storage according to the DNS response message, for example, if the domain name and the resolution result thereof are not stored in advance, the domain name and the resolution result thereof can be added into the local storage; for another example, if the resolution result corresponding to the domain name stored in advance is inconsistent with the resolution result in the DNS reply message, the resolution result stored locally may be updated according to the resolution result in the message, so that it is ensured that the correct IP address can be accessed when the domain name is accessed again, thereby avoiding traffic waste and access errors.
Therefore, by applying the scheme of the embodiment of the present specification, the user equipment can save the bandwidth and time for obtaining the domain name resolution result and accessing the web page by multicasting the DNS response message and updating the local storage in time.
Corresponding to the foregoing method embodiment, an embodiment of the present specification further provides a domain name resolution apparatus, which is applied to a target user equipment, and as shown in fig. 3, the apparatus may include:
the domain name query module 110 is configured to query whether a domain name to be resolved is stored in a domain name resolution result that is locally pre-stored in the case that it is determined that domain name resolution is required;
a message sending module 120, configured to send a DNS request message to the DNS server when it is found that the DNS request message is not stored, so that the DNS server replies a DNS response message in a multicast manner when receiving the DNS request message;
the message monitoring module 130 is configured to monitor a multicast DNS response message, obtain the DNS response message when the multicast DNS response message is monitored, and update a locally stored domain name resolution result according to the DNS response message.
An embodiment of the present specification further provides a domain name resolution device, which is applied to a DNS server, and as shown in fig. 4, the device may include:
a request message receiving module 210, configured to receive a DNS request message sent by a target user equipment; the DNS request message is sent to the DNS server when any target user equipment inquires that a domain name resolution result is not stored locally;
the response message multicast module 220 is configured to reply the DNS response message in a multicast manner, so that any target user equipment obtains the DNS response message when monitoring the multicast DNS response message and updates a locally stored domain name resolution result according to the DNS response message.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus 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 can be selected according to actual needs to achieve the purpose of the solution of the embodiments of the present specification. One of ordinary skill in the art can understand and implement it without inventive effort.
Fig. 5 is a schematic diagram illustrating a more specific hardware structure of a computing device according to an embodiment of the present disclosure, where the computing device may include: a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050. Wherein the processor 1010, memory 1020, input/output interface 1030, and communication interface 1040 are communicatively coupled to each other within the device via bus 1050.
The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solutions provided in the embodiments of the present disclosure.
The Memory 1020 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, or the like. The memory 1020 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present specification is implemented by software or firmware, the relevant program codes are stored in the memory 1020 and called to be executed by the processor 1010.
The input/output interface 1030 is used for connecting an input/output module to input and output information. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input devices may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices may include a display, a speaker, a vibrator, an indicator light, etc.
The communication interface 1040 is used for connecting a communication module (not shown in the drawings) to implement communication interaction between the present apparatus and other apparatuses. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, Bluetooth and the like).
It should be noted that although the above-mentioned device only shows the processor 1010, the memory 1020, the input/output interface 1030, the communication interface 1040 and the bus 1050, in a specific implementation, the device may also include other components necessary for normal operation. In addition, those skilled in the art will appreciate that the above-described apparatus may also include only those components necessary to implement the embodiments of the present description, and not necessarily all of the components shown in the figures.
While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. In other instances, features described in connection with one embodiment may be implemented as discrete components or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of various system modules and components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
Thus, particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. Further, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some implementations, multitasking and parallel processing may be advantageous.
The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.
Claims (10)
1. A domain name resolution method is characterized in that the method adds at least 2 target user equipment and a DNS server into 1 multicast group, and the method comprises the following steps:
under the condition that any target user equipment determines that domain name resolution is needed, whether the domain name needing resolution is stored or not is inquired in a domain name resolution result stored in advance locally;
the any target user equipment sends a DNS request message to the DNS server under the condition that the DNS request message is not stored in the any target user equipment;
the DNS server replies a DNS response message in a multicast mode under the condition of receiving the DNS request message;
and under the condition that any target user equipment monitors a multicast DNS response message, acquiring the DNS response message, and updating a locally stored domain name resolution result according to the DNS response message.
2. The method according to claim 1, wherein the replying the DNS reply message in a multicast manner in case of receiving the DNS request message comprises:
determining a domain name to be analyzed according to the received DNS request message;
inquiring whether the domain name to be analyzed and the analysis result of the domain name are stored in the local and currently stored domain name analysis results;
if yes, replying a DNS response message in a multicast mode, wherein the response message comprises the queried domain name resolution result.
3. The method of claim 2, wherein after querying whether the domain name to be resolved and the resolution result of the domain name are stored, the method further comprises:
if not, determining a DNS query mode of the DNS server system;
and according to the determined DNS query mode, obtaining query result information returned to the user equipment, and replying the query result information in a multicast mode.
4. The method according to claim 3, wherein in a case that the DNS query result is determined to be a recursive query, the obtaining query result information returned to the user equipment according to the determined DNS query manner and replying the query result information in a multicast manner includes:
according to the received DNS request message, sending a DNS analysis request to an upstream DNS server;
and under the condition of receiving a DNS analysis result returned by the upstream DNS server, replying a DNS response message in a multicast mode according to the DNS analysis result, wherein the response message comprises the returned domain name analysis result.
5. The method according to claim 3, wherein in a case that it is determined that the DNS query result is an iterative query, the obtaining query result information returned to the user equipment according to the determined DNS query manner and replying the query result information in a multicast manner includes:
obtaining an address of an upstream DNS server;
and returning the obtained address of the upstream DNS server to the target user equipment which sends the DNS request message, so that the target user equipment inquires a domain name resolution result of the upstream DNS server according to the address.
6. A domain name resolution system, wherein the system comprises at least 2 target user equipments and DNS servers, and the target user equipments and DNS servers join 1 multicast group:
under the condition that any target user equipment determines that domain name resolution is needed, whether the domain name needing resolution is stored or not is inquired in a domain name resolution result stored in advance locally;
the any target user equipment sends a DNS request message to the DNS server under the condition that the DNS request message is not stored in the any target user equipment;
the DNS server replies a DNS response message in a multicast mode under the condition of receiving the DNS request message;
and under the condition that any target user equipment monitors a multicast DNS response message, acquiring the DNS response message, and updating a locally stored domain name resolution result according to the DNS response message.
7. The apparatus according to claim 6, wherein the DNS server replies to the DNS reply message in a multicast manner when receiving the DNS request message by:
determining a domain name to be analyzed according to the received DNS request message;
inquiring whether the domain name to be analyzed and the analysis result of the domain name are stored in the local and currently stored domain name analysis results;
if yes, replying a DNS response message in a multicast mode, wherein the response message comprises the queried domain name resolution result.
8. The apparatus according to claim 7, wherein the DNS server, after querying whether the domain name to be resolved and the resolution result of the domain name have been stored, further replies the DNS reply packet in a multicast manner specifically by:
if not, determining a DNS query mode of the DNS server system;
and according to the determined DNS query mode, obtaining query result information returned to the user equipment, and replying the query result information in a multicast mode.
9. The apparatus according to claim 8, wherein in a case that it is determined that the DNS query result is a recursive query, the obtaining query result information returned to the user equipment according to the determined DNS query manner and replying the query result information in a multicast manner includes:
according to the received DNS request message, sending a DNS analysis request to an upstream DNS server;
and under the condition of receiving a DNS analysis result returned by the upstream DNS server, replying a DNS response message in a multicast mode according to the DNS analysis result, wherein the response message comprises the returned domain name analysis result.
10. The apparatus according to claim 8, wherein the DNS server obtains query result information returned to the user equipment according to the determined DNS query method and replies to the query result information in a multicast manner, specifically by:
obtaining an address of an upstream DNS server;
and returning the obtained address of the upstream DNS server to the target user equipment which sends the DNS request message, so that the target user equipment inquires a domain name resolution result of the upstream DNS server according to the address.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811423493.4A CN109561167B (en) | 2018-11-27 | 2018-11-27 | Domain name resolution method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811423493.4A CN109561167B (en) | 2018-11-27 | 2018-11-27 | Domain name resolution method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109561167A CN109561167A (en) | 2019-04-02 |
| CN109561167B true CN109561167B (en) | 2021-09-24 |
Family
ID=65867528
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811423493.4A Active CN109561167B (en) | 2018-11-27 | 2018-11-27 | Domain name resolution method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109561167B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112671866B (en) * | 2020-12-15 | 2022-11-25 | 牙木科技股份有限公司 | DNS (Domain name Server) shunt analysis method, DNS server and computer readable storage medium |
| CN112822309B (en) * | 2021-04-19 | 2021-07-16 | 北京视界云天科技有限公司 | Domain name resolution method and device |
| CN113206785B (en) * | 2021-05-28 | 2023-01-10 | 深圳市中科明望通信软件有限公司 | Network request method and device, terminal equipment and storage medium |
| CN114465791B (en) * | 2022-01-25 | 2024-04-30 | 杭州盈高科技有限公司 | Method and device for establishing white list in network management equipment, storage medium and processor |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101272407A (en) * | 2008-04-28 | 2008-09-24 | 杭州华三通信技术有限公司 | Caching detecting method, caching detecting device and detection responding device for domain name system |
| CN101483648A (en) * | 2009-02-20 | 2009-07-15 | 杭州华三通信技术有限公司 | Method, system, apparatus and DNS server for DNS buffer probe |
| CN103905572A (en) * | 2012-12-26 | 2014-07-02 | 中国移动通信集团公司 | Domain name resolution request processing method and device |
| CN107872544A (en) * | 2016-09-28 | 2018-04-03 | 中兴通讯股份有限公司 | A kind of domain name analytic method, device, gateway and system |
| CN108156274A (en) * | 2017-12-18 | 2018-06-12 | 杭州迪普科技股份有限公司 | Equipment is made to obtain the method and device of domain name mapping result in a kind of VPN network |
-
2018
- 2018-11-27 CN CN201811423493.4A patent/CN109561167B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101272407A (en) * | 2008-04-28 | 2008-09-24 | 杭州华三通信技术有限公司 | Caching detecting method, caching detecting device and detection responding device for domain name system |
| CN101483648A (en) * | 2009-02-20 | 2009-07-15 | 杭州华三通信技术有限公司 | Method, system, apparatus and DNS server for DNS buffer probe |
| CN103905572A (en) * | 2012-12-26 | 2014-07-02 | 中国移动通信集团公司 | Domain name resolution request processing method and device |
| CN107872544A (en) * | 2016-09-28 | 2018-04-03 | 中兴通讯股份有限公司 | A kind of domain name analytic method, device, gateway and system |
| CN108156274A (en) * | 2017-12-18 | 2018-06-12 | 杭州迪普科技股份有限公司 | Equipment is made to obtain the method and device of domain name mapping result in a kind of VPN network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109561167A (en) | 2019-04-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109561167B (en) | Domain name resolution method and device | |
| CN109787952B (en) | Network data access method and device and electronic equipment | |
| CN112073405A (en) | Webpage data loading method and device, computer equipment and storage medium | |
| CN111327647B (en) | Method and device for providing service to outside by container and electronic equipment | |
| CN109787951B (en) | Network data access method and device and electronic equipment | |
| US9448897B2 (en) | Process for selecting an authoritative name server | |
| CN102904765B (en) | The method and apparatus that data report | |
| CN107241372A (en) | Configuration information generation, sending method and resource loading method and apparatus and system | |
| CN111885216B (en) | DNS query method, device, equipment and storage medium | |
| CN103873918A (en) | Picture processing method, device and terminal | |
| CN108200132B (en) | Resource acquisition method, device, equipment and computer readable storage medium | |
| US20170289243A1 (en) | Domain name resolution method and electronic device | |
| EP3528474B1 (en) | Webpage advertisement anti-shielding methods and content distribution network | |
| CN109768980B (en) | Server access method, device, mobile terminal and computer readable storage medium | |
| CN102867266A (en) | Inquiry method and device | |
| CN110809070A (en) | Website domain name resolution record processing method and device, electronic equipment and storage medium | |
| CN113890879B (en) | Load balancing method and device for data access, computer equipment and medium | |
| CN109086158B (en) | Abnormal cause analysis method and device and server | |
| CN111200649B (en) | Scheduling method and device and scheduling model generation method and device | |
| CN110933193B (en) | Domain name resolution method and device, electronic equipment and computer readable storage medium | |
| CN112437148A (en) | Service request processing method and device, service server and system | |
| CN113315852B (en) | Domain name resolution method, device and system | |
| CN104182229A (en) | Callback display method and device and callback method and device | |
| US10095791B2 (en) | Information search method and apparatus | |
| CN103973819A (en) | Method, related device and system for responding to request for community domain name |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |