CN116405463A - Domain name query method, system, electronic device and non-transitory machine-readable medium - Google Patents
Domain name query method, system, electronic device and non-transitory machine-readable medium Download PDFInfo
- Publication number
- CN116405463A CN116405463A CN202310672952.7A CN202310672952A CN116405463A CN 116405463 A CN116405463 A CN 116405463A CN 202310672952 A CN202310672952 A CN 202310672952A CN 116405463 A CN116405463 A CN 116405463A
- Authority
- CN
- China
- Prior art keywords
- query
- domain name
- negative
- cache node
- type
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 67
- 230000004044 response Effects 0.000 claims abstract description 88
- 230000000694 effects Effects 0.000 abstract description 9
- 238000005516 engineering process Methods 0.000 abstract description 3
- 238000004590 computer program Methods 0.000 description 17
- 238000010586 diagram Methods 0.000 description 8
- 238000012545 processing Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000009471 action Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 230000003139 buffering effect Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 235000013399 edible fruits Nutrition 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 108020001568 subdomains Proteins 0.000 description 1
- 230000004083 survival effect Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
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
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/58—Caching of addresses or names
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to a domain name query method, a domain name query system, an electronic device and a non-transitory machine-readable medium. The method comprises the following steps: receiving a domain name query message, wherein the domain name query message comprises a query domain name and a query type; querying the negative cache node by using the query domain name; judging whether the query domain name exists in the negative cache node; if the query domain name exists in the negative cache node, calculating a bit identifier corresponding to the query type; judging whether a bit identifier corresponding to the query type exists in the negative cache node; and if the bit identifier corresponding to the query type exists in the negative cache node, returning the negative response content of the domain name query message. By the method and the device, the technical problems that the domain name does not have a negative cache scope which is too large and the negative cache nodes are repeated and the memory is not occupied by invalidation in the related technology are solved, and the technical effects that the domain name does not have the negative cache scope, the cache content is shared by different types of negative caches under the same domain name, and the memory is saved are achieved.
Description
Technical Field
The present disclosure relates to the field of computer networks, and in particular, to a domain name query method, system, electronic device, and non-transitory machine-readable medium.
Background
The domain name resolution system (Domain Name System, DNS) protocol standard defines that DNS negative caching is significant in that by reducing the query interaction of a recursive DNS server to an external authoritative DNS server in a responding DNS negative acknowledgement scenario, the DNS resolution response time of a client in that scenario is reduced. DNS negative caching is divided into two types:
(1) Domain name does not have a cache: this type negates the scope of the cache as the entire domain name, i.e., all requests querying the domain name hit the cache before the cache has not expired. The DNS protocol standards set forth later further expand the scope of this type of negative caching. Since the organization of the domain name system is an inverted tree, if a parent node on a fruit tree does not exist, all leaf nodes of the corresponding node should not exist.
As shown in fig. 1, if taobao.com is not present, its child node www.taobao.com must not be present. According to such a protocol, the scope where the domain name does not have a cache is further enlarged, from affecting the domain name itself to affecting the domain name itself and all of his sub-domains.
The negative buffered TTL is the TTL of the SOA record itself and a smaller value of the minimum TTL field in the SOA record, as specified by the DNS protocol. In the actual DNS service operation process, some authoritative DNS server implementation non-specifications are often encountered, and the negative acknowledgement TTL is not set according to the above-mentioned smaller value logic. Or the minimum TTL field in the SOA record is unreasonable (1 day or longer). Once the recursive DNS server obtains a negative acknowledgement from the authority DNS server, an excessively large negative acknowledgement TTL may cause the acknowledgement to survive as a negative cache at the recursive DNS server for an excessively long time, and meanwhile, since the scope of the negative cache is the whole domain name or even all sub-domain names under the domain name, during the survival of the negative cache, DNS resolution of the domain name itself or even all sub-domain names under the domain name is affected. The addition of the DNS service domain name and DNS resolution are asynchronous, and there is a great possibility that DNS resolution occurs before the DNS service domain name is added into effect, so that the problem that the domain name becomes slow in effect due to the similar domain name negative buffering occurs frequently in the DNS service operation process.
(2) Type no cache: this type of negative cache is indexed by < query domain name, query type >, i.e., all requests that query the same < query domain name, query type > hit the cache before the cache has not expired. Typically, a recursive DNS server stores and queries with < query domain name, query type > as an index for negative caches of this type.
As shown in fig. 2, under the www.taobao.com domain name, no record exists in the type a, AAAA and TXT, the recursive DNS server may query the domain name according to the term < query type > to index independent cache nodes of different types (a, AAAA and TXT) with the same domain name (www.taobao.com), the contents of the negative cache nodes of different types are SOA records, and the TTL may be different. The query types are organized according to the DNS protocol according to 16-bit unsigned integers (2 bytes), the theoretical value range is [0, 65535], the defined maximum available DNS record type of the query is 257 (CAA), that is, for the same domain name, on the recursive DNS server side, according to < query domain name, the query type > is an index, no negative cache exists in the types, and 257-1=256 cache nodes can exist in the types at most, and the contents of the nodes are all the same SOA record. The content of the negative cache nodes of different types is the same, but the negative cache nodes need to be stored independently, so that the waste exists in the use of the memory, and the optimization space exists.
In summary, the domain name on the recursive DNS server is not provided with a negative caching scope of the type which is too large, so that the domain name change is actually effective and becomes slow; and the query type on the recursive DNS server is not negative, the cache node is repeated under the scene of multiple query types, and the memory is occupied in invalid.
For the above-described problems, no effective solution has been proposed.
Disclosure of Invention
The domain name query method, system, electronic equipment and non-transient machine-readable medium at least solve the problems that in the related technology, a domain name does not have a negative cache action domain which is too large and a negative cache node is repeated, and memory is not occupied.
According to an aspect of the embodiments of the present application, there is provided a domain name query method, including: receiving a domain name query message, wherein the domain name query message comprises a query domain name and a query type; querying a negative cache node by using the query domain name, wherein the negative cache node uses the domain name and a record type bitmap as indexes to store the negative response content of the domain name query message, and the record type bitmap is provided with a bit identifier corresponding to the query type; judging whether the query domain name exists in the negative cache node; if the query domain name exists in the negative cache node, calculating a bit identifier corresponding to the query type; judging whether a bit identifier corresponding to the query type exists in the negative cache node; and if the bit identifier corresponding to the query type exists in the negative cache node, returning negative response content of the domain name query message.
According to another aspect of an embodiment of the present application, there is provided a domain name query system, including: the client is used for sending a domain name query message, wherein the domain name query message comprises a query domain name and a query type; the recursion server is connected with the client and is used for receiving the domain name query message; querying a negative cache node by using the query domain name, wherein the negative cache node uses the domain name and a record type bitmap as indexes to store the negative response content of the domain name query message, and the record type bitmap is provided with a bit identifier corresponding to the query type; judging whether the query domain name exists in the negative cache node; if the query domain name exists in the negative cache node, calculating a bit identifier corresponding to the query type; judging whether a bit identifier corresponding to the query type exists in the negative cache node; and if the bit identifier corresponding to the query type exists in the negative cache node, returning negative response content of the domain name query message.
According to another aspect of an embodiment of the present application, there is provided an electronic device including: a processor, and a memory storing a program, wherein the program comprises instructions that when executed by the processor cause the processor to perform the method described in the foregoing.
According to another aspect of embodiments of the present application, there is provided a non-transitory machine-readable medium storing computer instructions for causing a computer to perform the method described in the foregoing.
In the embodiment of the application, a domain name query message is received, wherein the domain name query message comprises a query domain name and a query type; querying a negative cache node by using a query domain name, wherein the negative cache node uses the domain name and a record type bitmap as indexes to store negative response contents of domain name query messages, and a bit identifier corresponding to the query type is arranged in the record type bitmap; judging whether the query domain name exists in the negative cache node; if the query domain name exists in the negative cache node, calculating a bit identifier corresponding to the query type; judging whether a bit identifier corresponding to the query type exists in the negative cache node; and if the bit identifier corresponding to the query type exists in the negative cache node, returning the negative response content of the domain name query message. That is, in the embodiment of the present application, the domain name and the bitmap of the record type are used as indexes, the negative acknowledgement content of the domain name query message is stored in the negative cache node, the negative cache node is queried by the domain name query message with the query domain name and the query type as indexes, and when the bit identifiers corresponding to the query domain name and the query type exist in the negative cache node at the same time, the negative acknowledgement content of the domain name query message is returned, so that the technical problems that the domain name in the related art has no negative cache scope is too large, the negative cache node is repeated, and the memory is not occupied are solved, and the technical effects that the domain name has no negative cache scope, and different types of negative caches under the same domain name share the cache content, so that the memory is saved are achieved.
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. It is evident that the drawings in the following description are only some embodiments of the invention, from which other embodiments can be obtained for a person skilled in the art without inventive effort.
FIG. 1 is a schematic diagram of a domain name organization provided in the prior art;
FIG. 2 is a schematic diagram of storing and querying with query domain names and query types as indexes provided in the prior art;
FIG. 3 is a schematic diagram of storing and querying with a domain name and a bitmap of a record type as indexes according to an embodiment of the present application;
fig. 4 is a flowchart of a domain name query method provided in an embodiment of the present application;
FIG. 5 is a schematic diagram of a negative cache query procedure according to an alternative embodiment of the present application;
FIG. 6 is a schematic diagram of a negative cache update procedure according to an alternative embodiment of the present application;
fig. 7 shows a block diagram of a hardware structure of an electronic device.
Detailed Description
Embodiments of the present embodiment will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present embodiments are illustrated in the accompanying drawings, it is to be understood that the present embodiments may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided to provide a more thorough and complete understanding of the present embodiments. It should be understood that the drawings and the embodiments of the present embodiments are presented for purposes of illustration only and are not intended to limit the scope of the embodiments.
First, partial terms or terminology appearing in describing embodiments of the present application are applicable to the following explanation:
DNS: domain name resolution system.
DNS caching: the general internet DNS system includes three roles: client, recursive DNS server, authoritative DNS server. The client initiates a DNS query to the recursive DNS server, which takes the final result by iterating the recursive query to the multi-level authoritative DNS server, and returns a reply to the client. In order to be able to respond to DNS queries of clients faster, query interactions with external authoritative DNS servers are reduced, DNS caching functions are typically implemented on the recursive DNS server side, and intermediate and final answers to iterative recursive queries are cached in memory, i.e. DNS caching.
TTL (Time To Live): the time (in seconds) that the DNS cache survives within the recursive DNS server.
SOA (Start Of Authority) record: a DNS record exists on an area, one area having to have and only one record of this type. The record type data includes a field minimum TTL field, and the smaller value of TTL of the field and the SOA record itself is negative buffer TTL according to DNS protocol.
DNS negative cache (DNS Negative cache): i.e. buffering of DNS negative acknowledgements. DNS negative acknowledgements fall into two categories:
(1) Query domain Name does not exist (Name error): a domain name representing the query does not exist.
(2) Query type does not exist (Data error): a domain name representing a query exists, but no query type of data exists under that domain name.
Optionally, the storage and query logic of the different types of negative caches is as follows:
1. query domain name non-existence negative cache
For example, indexing storage and query caching with < query domain name > has the disadvantage: the scope of negative cache is the whole domain name and even all subdomain names under the domain name. Before the domain name negative cache is not expired, all queries for the domain name, even all queries for all sub-domain names of the domain name, return a negative acknowledgement that the domain name does not exist. The domain name change takes effect slowly.
For another example, indexing stores and query caches with < query domain name, query type > has the disadvantages: independent cache nodes are created for different types of requests of the same domain name, the content of the cache nodes is the same, and memory occupation is large.
2. Query type non-existent negative buffer memory
For example, indexing stores and query caches with < query domain name, query type > has the disadvantage: independent cache nodes are created for different types of requests of the same domain name, the content of the cache nodes is the same, and memory occupation is large.
Further, alternative embodiments of the present application provide a new negative cached store and query logic, as shown in FIG. 3:
(1) negative cache nodes are stored with < domain name, record type bitmap > as an index, wherein the maximum length of the record type bitmap (bitmap) is DNS maximum valid record type 257/8+1=33 bytes.
(2) The negative cache content is an SOA record, and the whole bitmap comprises the query types which share the same negative cache content.
(3) The query domain name is fully matched and the query type negates the hit in the cache bitmap, then the negated cache is hit.
In order to overcome the above-mentioned shortcomings, the embodiments of the present application provide a domain name query method, and fig. 4 is a flowchart of the domain name query method provided in the embodiments of the present application, as shown in fig. 4, where the method includes the following steps:
step S402, receiving a domain name query message, wherein the domain name query message comprises a query domain name and a query type;
the domain name query message refers to a DNS query request indexed by a query domain name and a query type.
Step S404, querying a negative cache node by using the query domain name, wherein the negative cache node uses the domain name and a record type bitmap as indexes to store the negative response content of the domain name query message, and the record type bitmap is provided with a bit identifier corresponding to the query type;
Optionally, the DNS protocol specifies digitally encoded footprints corresponding to different query types, e.g., a is 1, aaaa is 28, ns is 2, soa is 6, and the digitally encoded footprints corresponding to the query types may be used as bit identifiers corresponding to the query types in the record type bitmap. If a, AAAA, negative cache of SOA type exists, then the record type bitmap should be..01000110, the bit identification corresponding to the 1,2,6 position in the record type bitmap is 1.
Because the contents of the different types of negative caches are the same, the record type bitmap can effectively reduce the memory occupation of the different types of DNS negative caches, and can effectively improve the query efficiency of the different types of DNS caches.
Step S406, judging whether the query domain name exists in the negative cache node;
it should be noted that, the recursive DNS server, also referred to as a recursive server, may include one or more cache nodes, where a cache node refers to a cache in the recursive DNS server; the positive caching node is used for caching positive response contents for storing domain name inquiry messages in the recursive DNS server; the negative caching node is a cache in the recursive DNS server for storing negative acknowledgement content of domain name query messages. In addition, the cache contents in the cache nodes can be stored in different index modes according to actual application requirements, so that subsequent cache inquiry is facilitated.
The recursive DNS server can use the caching and recursive queries to quickly obtain the desired DNS record (corresponding to the answer content). When a client sends a DNS query request, a recursive DNS server can firstly query own cache, and if a needed DNS record exists in the cache, the result is directly returned to the client. If the desired DNS record does not exist in the cache, the recursive DNS server may send a DNS query request to an external authoritative DNS server, which may return the desired DNS record to the recursive DNS server.
Step S408, if the query domain name exists in the negative cache node, calculating a bit identifier corresponding to the query type;
the bit is identified as a bit in a record type bitmap.
Step S410, judging whether a bit identifier corresponding to the query type exists in the negative cache node;
step S412, if the bit identifier corresponding to the query type exists in the negative cache node, the negative response content of the domain name query message is returned.
In the embodiment of the application, the domain name and the bitmap of the record type are used as indexes, the negative response content of the domain name query message is stored in the negative cache node, the negative cache node is queried through the domain name query message with the query domain name and the query type as indexes, and when the bit identifiers corresponding to the query domain name and the query type exist in the negative cache node at the same time, the negative response content of the domain name query message is returned, so that the technical problems that the domain name in the related technology is not large in negative cache action domain and the negative cache node is repeated, and the memory is not occupied are solved, the action domain that the domain name is not in negative cache can be reduced, and the different types of negative caches under the same domain name share the cache content, so that the technical effect of saving the memory is achieved.
As an alternative embodiment, the method further comprises: and if the query domain name does not exist in the negative cache node or the bit identifier corresponding to the query type does not exist in the negative cache node, querying the positive cache node by using the domain name query message.
It should be noted that, since different types of positive cache contents are different, the positive cache node stores the positive acknowledgement contents of the domain name query message using the domain name and the record type as indexes. In a specific implementation process, the positive response content of the domain name query message can be stored in the positive cache node by taking the domain name and the record type as indexes.
In the embodiment of the application, if the query domain name does not exist in the negative cache node or the bit identifier corresponding to the query type exists in the negative cache node, the query is required to confirm that the cache node has obtained the corresponding response content.
As an alternative embodiment, querying the positive cache node using the domain name query message includes the following implementation steps:
step 11, judging whether the query domain name and the query type exist in the positive cache node;
and step 13, if the query domain name and the query type exist in the positive cache node, returning the positive response content of the domain name query message.
As an alternative embodiment, the method further comprises:
and step 15, if the query domain name does not exist or the query type does not exist in the positive cache node, sending a domain name query message to the authoritative server, acquiring the response content of the domain name query message, and returning the response content of the domain name query message.
The authoritative server is also called authoritative DNS server. The authoritative DNS server is a server that is able to answer domain name query messages for a domain name directly. It is typically managed by the registrar of the domain name or the domain name owner itself, and is responsible for managing all DNS records under that domain name. When a DNS query request arrives at an authoritative DNS server, it queries the DNS record managed by itself, and then returns the query result (corresponding to the answer content of the domain name query message described above).
Authoritative DNS servers are typically hierarchical, starting from a root domain name server, querying down step by step until an authoritative DNS server is found that can answer the query request. During the query process, the recursive DNS server caches the query results to improve query efficiency.
In the embodiment of the application, if the query domain name exists in the positive cache node and the query type exists, the positive response content of the domain name query message is directly returned; if the affirmation buffer node does not have the inquiry domain name or the inquiry type, the affirmation buffer node needs to send the domain name inquiry information to the authority server, acquire the response content of the domain name inquiry information, and then return the response content of the domain name inquiry information.
Optionally, as shown in fig. 5, the recursive DNS server receives a DNS query request from the client; querying the negative cache using the query domain name; judging whether the query domain name exists in the negative cache; if yes, calculating a query type bit identifier (bit) and responding to whether a record type bitmap (bitmap) is provided with the bit identifier (bit); if yes, using negative buffer response. If the query domain name does not exist in the negative cache or the bit identification (bit) is not set in the response record type bitmap (bitmap), querying the positive cache; judging whether the DNS query request exists in the affirmative cache; if yes, using a positive cache response; if not, initiating a recursive query to an external authoritative DNS server.
Using < domain name, record type bitmap > as index, the shared cache content stores DNS negative caches. The following technical effects can be achieved by such an indexing scheme:
the scope of negative cache of the domain name is reduced, and the domain name is degraded from the absence of the domain name, even the absence of the domain name and the absence of all sub-domain names of the domain name to the absence of specific type data under the domain name, so that the scope of influence of the negative cache is reduced, and the domain name change is accelerated to take effect.
The negative caches with different types of the same domain name can share the cache content, the shared cache TTL is not required to be independently calculated because of different types, the expiration of the negative caches is faster, and the domain name change is more effective.
The shared negative buffer scheme saves more memory than other schemes under more than 2 different types of negative response scenes.
As an optional embodiment, after obtaining the answer content of the domain name query message, the method further includes: updating the cache node based on the answer content of the domain name query message.
When receiving the response content of the domain name query message from the authoritative DNS server, the query result needs to be updated into the cache node so that the query result can be directly returned when the next query is performed, and the query efficiency is improved.
As an optional embodiment, the cache node includes a negative cache node and a positive cache node, and updates the cache node based on the answer content of the domain name query message, including the following specific implementation steps:
step 21, judging whether the response content of the domain name query message is negative response content;
step 23, if the answer content of the domain name query message is negative answer content, updating the negative cache node;
and step 25, if the response content of the domain name query message is not negative response content, updating the positive cache node.
Optionally, the answer content of the domain name query message from the authoritative DNS server is received, including the query domain name, query type, TTL, and resource record.
If the answer content of the domain name query message is negative answer content, adding the bit identification corresponding to the query domain name and the query type into the negative cache node so as to directly return the negative answer content when querying next time, thereby improving the query efficiency.
If the answer content of the domain name query message is positive answer content, the query domain name and the query type are added into the positive cache node, so that the query result can be directly returned when the next query is performed, and the query efficiency is improved.
It should be noted that, the influence of TTL needs to be considered when updating the cache node. If the TTL of the cache record has expired, the cache record needs to be deleted from the cache node to avoid returning an expired query result. Meanwhile, the expired cache records in the cache nodes need to be cleaned regularly so as to ensure the accuracy and reliability of the cache data.
As an alternative embodiment, updating the negative cache node comprises the following implementation steps:
step 31, querying a negative cache node by using the query domain name;
step 33, judging whether negative answer content exists in the negative cache node;
step 35, if the negative cache node has negative response content, calculating a bit identifier corresponding to the query type;
And step 37, updating the record type bitmap of the negative cache node based on the bit identification corresponding to the query type.
It should be noted that, when updating the negative cache node, the influence of the bit identifier corresponding to the query type needs to be considered. If the bit identification corresponding to the query type already exists, updating is not needed; if the bit identification corresponding to the query type does not exist, the bit identification is required to be added into the bitmap of the record type, so that negative response content can be directly returned when the query is performed next time, and the query efficiency is improved. Meanwhile, expired cache records in the negative cache nodes need to be cleaned regularly so as to ensure the accuracy and reliability of the cache data.
As an alternative embodiment, updating the record type bitmap of the negative cache node based on the bit identification corresponding to the query type includes the following implementation steps:
step 41, judging whether the buffer bit identifier in the record type bitmap of the negative buffer node comprises a bit identifier corresponding to the query type;
step 43, if the buffer bit identifier in the record type bitmap of the negative buffer node does not include the bit identifier corresponding to the query type, setting the bit identifier corresponding to the query type as the buffer bit identifier in the record type bitmap of the negative buffer node.
In the embodiment of the application, if the bit identifier corresponding to the query type is already contained in the record type bitmap of the negative cache node, the update operation is not required. If the buffer bit identification in the record type bitmap of the negative buffer node does not comprise the bit identification corresponding to the query type, setting the bit identification corresponding to the query type as the buffer bit identification in the record type bitmap of the negative buffer node.
In addition, after the record type bitmap of the negative cache node is updated, the record type bitmap of the negative cache node contains record type bit identifiers of known query types, so that whether data need to be acquired from the negative cache node is quickly judged in subsequent queries.
As an alternative embodiment, the method further comprises the following specific implementation steps:
step 51, if the negative cache node does not have negative response content, a new negative cache node is created;
step 53, calculating a bit identifier corresponding to the query type;
and step 55, updating the record type bitmap of the new negative cache node based on the bit identification corresponding to the query type.
In order to improve the query efficiency, when processing the domain name query message, if there is no negative cache node of the domain name in the cache, a new negative cache node needs to be created. Meanwhile, a corresponding bit identifier is calculated according to the query type, and then a record type bitmap of the new negative cache node is updated.
Further, when the same domain name query message arrives next time, whether a negative cache node of the domain name exists or not can be searched in the cache, if the negative cache node exists and the bit identifier corresponding to the query type is contained in the record type bitmap, the negative response content can be directly returned, and the domain name query message does not need to be sent to the authoritative DNS server again, so that time and bandwidth resources are saved.
As an alternative embodiment, updating the record type bitmap of the new negative cache node based on the bit identification corresponding to the query type includes: and setting the bit identifier corresponding to the query type as a cache bit identifier in a record type bitmap of the new negative cache node.
When the record type bitmap of the new negative cache node is updated, only the bit identifier corresponding to the query type is required to be set in the record type bitmap of the new negative cache node as the cache bit identifier.
Since the new negative cache node does not have any known record type bit identity applicable to the query type, the bit identity corresponding to the query type needs to be set as the cache bit identity.
In the subsequent query, if the bit identifier corresponding to the query type appears in the record type bitmap of the new negative cache node, the data can be directly obtained from the negative cache node without performing actual data query operation.
Alternatively, as shown in FIG. 6, the recursive DNS server receives a DNS reply (corresponding to the reply content described above) from an external authoritative DNS server; judging whether the answer is negative; if yes, querying a negative cache by using the query domain name; judging whether the domain name exists in the negative cache; if the domain name exists, calculating a bit identifier (bit) according to the query type; if the domain name exists, creating a negative cache node, and calculating a bit identifier (bit) according to the query type; after obtaining the bit identification (bit), judging whether the bit identification (bit) is set in the record type bitmap; and if not, updating the record type bitmap.
According to another aspect of an embodiment of the present application, there is provided a domain name query system, including:
the client is used for sending a domain name query message, wherein the domain name query message comprises a query domain name and a query type;
the recursion server is connected with the client and is used for receiving the domain name inquiry message; querying a negative cache node by using a query domain name, wherein the negative cache node uses the domain name and a record type bitmap as indexes to store negative response contents of domain name query messages, and a bit identifier corresponding to the query type is arranged in the record type bitmap; judging whether the query domain name exists in the negative cache node; if the query domain name exists in the negative cache node, calculating a bit identifier corresponding to the query type; judging whether a bit identifier corresponding to the query type exists in the negative cache node; and if the bit identifier corresponding to the query type exists in the negative cache node, returning the negative response content of the domain name query message.
In the embodiment of the application, the system takes the domain name and the bitmap of the record type as indexes, stores the negative response content of the domain name query message into the negative cache node, queries the negative cache node through the domain name query message taking the query domain name and the query type as indexes, and returns the negative response content of the domain name query message when the bit identifiers corresponding to the query domain name and the query type exist in the negative cache node at the same time, thereby solving the technical problems that the domain name does not have a negative cache scope which is too large and the negative cache node is repeated and the memory is not occupied in the related art, achieving the technical effects of reducing the scope of the domain name which does not have the negative cache, sharing the cache content by different types of negative caches under the same domain name and saving the memory.
The embodiment of the application also provides electronic equipment, which comprises: at least one processor; and a memory communicatively coupled to the at least one processor. The memory stores a computer program executable by the at least one processor, which when executed by the at least one processor is configured to cause an electronic device to perform a method of an embodiment of the present application.
Alternatively, in this embodiment, the above-mentioned computer terminal may be located in at least one network device among a plurality of network devices of the computer network. Such electronic devices include, but are not limited to, computer devices.
Optionally, in this embodiment, the computer device may include: a memory and a processor, the memory storing a computer program; a processor for executing a computer program stored in the memory, the computer program when run causing the processor to perform the method steps of any one of the above.
The memory may be used to store software programs and modules, such as program instructions/modules corresponding to the domain name query method in the embodiment of the present application, and the processor executes the software programs and modules stored in the memory, thereby executing various functional applications and data processing, that is, implementing the domain name query method described above. The memory may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory may further include memory remotely located relative to the processor, which may be connected to the computer terminal via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
Optionally, the processor may call the information and the application program stored in the memory through the transmission device to execute the following steps: receiving a domain name query message, wherein the domain name query message comprises a query domain name and a query type; querying a negative cache node by using a query domain name, wherein the negative cache node uses the domain name and a record type bitmap as indexes to store negative response contents of domain name query messages, and a bit identifier corresponding to the query type is arranged in the record type bitmap; judging whether the query domain name exists in the negative cache node; if the query domain name exists in the negative cache node, calculating a bit identifier corresponding to the query type; judging whether a bit identifier corresponding to the query type exists in the negative cache node; and if the bit identifier corresponding to the query type exists in the negative cache node, returning the negative response content of the domain name query message.
Optionally, in this embodiment, the above processor may further execute program code for: the method further comprises the steps of: if the query domain name does not exist in the negative cache node or the bit identifier corresponding to the query type does not exist in the negative cache node, querying the positive cache node by using the domain name query message, wherein the positive cache node stores the positive response content of the domain name query message by using the domain name and the record type as indexes.
Optionally, in this embodiment, the above processor may further execute program code for: querying the positive cache node using a domain name query message, comprising: judging whether the query domain name and the query type exist in the positive cache node; and if the query domain name and the query type exist in the positive cache node, returning the positive response content of the domain name query message.
Optionally, in this embodiment, the above processor may further execute program code for: the method further comprises the steps of: if the query domain name does not exist or the query type does not exist in the positive cache node, the domain name query message is sent to the authoritative server, the response content of the domain name query message is obtained, and the response content of the domain name query message is returned.
Optionally, in this embodiment, the above processor may further execute program code for: after obtaining the answer content of the domain name query message, the method further comprises: updating the cache node based on the answer content of the domain name query message.
Optionally, in this embodiment, the above processor may further execute program code for: the cache nodes comprise negative cache nodes and positive cache nodes, and the cache nodes are updated based on the response content of the domain name query message, and the method comprises the following steps: judging whether the response content of the domain name query message is negative response content or not; if the response content of the domain name query message is negative response content, updating the negative cache node; and if the response content of the domain name query message is not negative response content, updating the positive cache node.
Optionally, in this embodiment, the above processor may further execute program code for: updating the negative cache node, comprising: querying the negative cache node by using the query domain name; judging whether negative response contents exist in the negative cache node or not; if the negative cache node has negative response content, calculating a bit identifier corresponding to the query type; and updating the record type bitmap of the negative cache node based on the bit identification corresponding to the query type.
Optionally, in this embodiment, the above processor may further execute program code for: updating the record type bitmap of the negative cache node based on the bit identification corresponding to the query type, including: judging whether the cache bit identifier in the record type bitmap of the negative cache node comprises a bit identifier corresponding to the query type; if the buffer bit identification in the record type bitmap of the negative buffer node does not comprise the bit identification corresponding to the query type, setting the bit identification corresponding to the query type as the buffer bit identification in the record type bitmap of the negative buffer node.
Optionally, in this embodiment, the above processor may further execute program code for: the method further comprises the steps of: if the negative cache node does not have negative response content, a new negative cache node is created; calculating a bit identifier corresponding to the query type; and updating the record type bitmap of the new negative cache node based on the bit identification corresponding to the query type.
Optionally, in this embodiment, the above processor may further execute program code for: updating the record type bitmap of the new negative cache node based on the bit identification corresponding to the query type, including: and setting the bit identifier corresponding to the query type as a cache bit identifier in a record type bitmap of the new negative cache node.
The present application also provides a non-transitory machine-readable medium storing a computer program, wherein the computer program, when executed by a processor of a computer, is configured to cause the computer to perform the method of the present application. The non-transitory machine-readable medium described above includes a storage medium.
Alternatively, in this embodiment, the storage medium may be located in any one of the computer terminals in the computer terminal group in the computer network, or in any one of the mobile terminals in the mobile terminal group.
Alternatively, in this embodiment, the storage medium may be used to store the program code corresponding to the domain name query method provided in the foregoing embodiment, where the program code when executed by the processor controls the processor to execute the domain name query method.
Alternatively, in the present embodiment, the above-described storage medium is configured to store program code for performing the steps of: receiving a domain name query message, wherein the domain name query message comprises a query domain name and a query type; querying a negative cache node by using a query domain name, wherein the negative cache node uses the domain name and a record type bitmap as indexes to store negative response contents of domain name query messages, and a bit identifier corresponding to the query type is arranged in the record type bitmap; judging whether the query domain name exists in the negative cache node; if the query domain name exists in the negative cache node, calculating a bit identifier corresponding to the query type; judging whether a bit identifier corresponding to the query type exists in the negative cache node; and if the bit identifier corresponding to the query type exists in the negative cache node, returning the negative response content of the domain name query message.
Optionally, in this embodiment, the storage medium is configured to store program code for further performing the steps of: the method further comprises the steps of: if the query domain name does not exist in the negative cache node or the bit identifier corresponding to the query type does not exist in the negative cache node, querying the positive cache node by using the domain name query message, wherein the positive cache node stores the positive response content of the domain name query message by using the domain name and the record type as indexes.
Optionally, in this embodiment, the storage medium is configured to store program code for further performing the steps of: querying the positive cache node using a domain name query message, comprising: judging whether the query domain name and the query type exist in the positive cache node; and if the query domain name and the query type exist in the positive cache node, returning the positive response content of the domain name query message.
Optionally, in this embodiment, the storage medium is configured to store program code for further performing the steps of: the method further comprises the steps of: if the query domain name does not exist or the query type does not exist in the positive cache node, the domain name query message is sent to the authoritative server, the response content of the domain name query message is obtained, and the response content of the domain name query message is returned.
Optionally, in this embodiment, the storage medium is configured to store program code for further performing the steps of: after obtaining the answer content of the domain name query message, the method further comprises: updating the cache node based on the answer content of the domain name query message.
Optionally, in this embodiment, the storage medium is configured to store program code for further performing the steps of: the cache nodes comprise negative cache nodes and positive cache nodes, and the cache nodes are updated based on the response content of the domain name query message, and the method comprises the following steps: judging whether the response content of the domain name query message is negative response content or not; if the response content of the domain name query message is negative response content, updating the negative cache node; and if the response content of the domain name query message is not negative response content, updating the positive cache node.
Optionally, in this embodiment, the storage medium is configured to store program code for further performing the steps of: updating the negative cache node, comprising: querying the negative cache node by using the query domain name; judging whether negative response contents exist in the negative cache node or not; if the negative cache node has negative response content, calculating a bit identifier corresponding to the query type; and updating the record type bitmap of the negative cache node based on the bit identification corresponding to the query type.
Optionally, in this embodiment, the storage medium is configured to store program code for further performing the steps of: updating the record type bitmap of the negative cache node based on the bit identification corresponding to the query type, including: judging whether the cache bit identifier in the record type bitmap of the negative cache node comprises a bit identifier corresponding to the query type; if the buffer bit identification in the record type bitmap of the negative buffer node does not comprise the bit identification corresponding to the query type, setting the bit identification corresponding to the query type as the buffer bit identification in the record type bitmap of the negative buffer node.
Optionally, in this embodiment, the storage medium is configured to store program code for further performing the steps of: the method further comprises the steps of: if the negative cache node does not have negative response content, a new negative cache node is created; calculating a bit identifier corresponding to the query type; and updating the record type bitmap of the new negative cache node based on the bit identification corresponding to the query type.
Optionally, in this embodiment, the storage medium is configured to store program code for further performing the steps of: updating the record type bitmap of the new negative cache node based on the bit identification corresponding to the query type, including: and setting the bit identifier corresponding to the query type as a cache bit identifier in a record type bitmap of the new negative cache node.
The present application also provides a computer program product comprising a computer program, wherein the computer program, when executed by a processor of a computer, is for causing the computer to perform the method of the present application embodiments.
With reference to fig. 7, a block diagram of an electronic device that may be a server or a client of an embodiment of the present application will now be described, which is an example of a hardware device that may be applied to aspects of the present application. Electronic devices are intended to represent various forms of digital electronic computer devices, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the application described and/or claimed herein.
As shown in fig. 7, the electronic device includes a computing unit 701 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 702 or a computer program loaded from a storage unit 708 into a Random Access Memory (RAM) 703. In the RAM703, various programs and data required for the operation of the electronic device can also be stored. The computing unit 701, the ROM 702, and the RAM703 are connected to each other through a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
A number of components in the electronic device are connected to the I/O interface 705, including: an input unit 706, an output unit 707, a storage unit 708, and a communication unit 709. The input unit 706 may be any type of device capable of inputting information to an electronic device, and the input unit 706 may receive input numeric or character information and generate key signal inputs related to user settings and/or function controls of the electronic device. The output unit 707 may be any type of device capable of presenting information and may include, but is not limited to, a display, speakers, video/audio output terminals, vibrators, and/or printers. Storage unit 708 may include, but is not limited to, magnetic disks, optical disks. The communication unit 709 allows the electronic device to exchange information/data with other devices through a computer network, such as the internet, and/or various telecommunications networks, and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication transceivers and/or chipsets, such as bluetooth devices, wiFi devices, wiMax devices, cellular communication devices, and/or the like.
The computing unit 701 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 701 include, but are not limited to, a CPU, a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 701 performs the various methods and processes described above. For example, in some embodiments, method embodiments of the present application may be implemented as a computer program tangibly embodied on a machine-readable medium, such as storage unit 708. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device via the ROM 702 and/or the communication unit 709. In some embodiments, the computing unit 701 may be configured to perform the methods described above by any other suitable means (e.g., by means of firmware).
A computer program for implementing the methods of embodiments of the present application may be written in any combination of one or more programming languages. These computer programs may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of embodiments of the present application, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable signal medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
It should be noted that the term "comprising" and its variants as used in the embodiments of the present application are open-ended, i.e. "including but not limited to". The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. The references to "one" or "a plurality" of the embodiments of the present application are intended to be illustrative, and not limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be interpreted as "one or more" unless the context clearly indicates otherwise.
User information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) according to the embodiments of the present application are information and data authorized by a user or sufficiently authorized by each party, and the collection, use and processing of relevant data is required to comply with relevant laws and regulations and standards of relevant countries and regions, and is provided with a corresponding operation portal for the user to select authorization or rejection.
The steps described in the method embodiments provided in the embodiments of the present application may be performed in a different order and/or performed in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of protection of the present application is not limited in this respect.
The term "embodiment" in this specification means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive. The various embodiments in this specification are described in a related manner, with identical and similar parts being referred to each other. In particular, for apparatus, devices, system embodiments, the description is relatively simple as it is substantially similar to method embodiments, see for relevant part of the description of method embodiments.
The above examples only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the patent. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application shall be subject to the appended claims.
Claims (13)
1. A domain name query method, comprising:
receiving a domain name query message, wherein the domain name query message comprises a query domain name and a query type;
querying a negative cache node by using the query domain name, wherein the negative cache node uses the domain name and a record type bitmap as indexes to store the negative response content of the domain name query message, and the record type bitmap is provided with a bit identifier corresponding to the query type;
judging whether the query domain name exists in the negative cache node;
if the query domain name exists in the negative cache node, calculating a bit identifier corresponding to the query type;
judging whether a bit identifier corresponding to the query type exists in the negative cache node;
and if the bit identifier corresponding to the query type exists in the negative cache node, returning negative response content of the domain name query message.
2. The method of claim 1, wherein the method further comprises:
and if the query domain name does not exist in the negative cache node or the bit identifier corresponding to the query type does not exist in the negative cache node, querying a positive cache node by using the domain name query message, wherein the positive cache node stores the positive response content of the domain name query message by using the domain name and the record type as indexes.
3. The method of claim 2, wherein querying the positive cache node using the domain name query message comprises:
judging whether the query domain name and the query type exist in the positive cache node;
and if the query domain name and the query type exist in the positive cache node, returning the positive response content of the domain name query message.
4. A method according to claim 3, wherein the method further comprises:
and if the query domain name does not exist or the query type does not exist in the positive cache node, sending the domain name query message to an authoritative server, acquiring the response content of the domain name query message, and returning the response content of the domain name query message.
5. The method of claim 4, wherein after obtaining the answer content of the domain name query message, the method further comprises:
and updating the cache node based on the response content of the domain name query message.
6. The method of claim 5, wherein the cache nodes comprise the negative cache node and a positive cache node, updating the cache nodes based on the answer content of the domain name query message, comprising:
Judging whether the response content of the domain name query message is negative response content or not;
if the response content of the domain name query message is the negative response content, updating the negative cache node;
and if the response content of the domain name query message is not the negative response content, updating the positive cache node.
7. The method of claim 6, wherein updating the negative cache node comprises:
querying the negative cache node using the query domain name;
judging whether the negative cache node has the negative response content or not;
if the negative cache node has the negative response content, calculating a bit identifier corresponding to the query type;
and updating the record type bitmap of the negative cache node based on the bit identifier corresponding to the query type.
8. The method of claim 7, wherein updating the record type bitmap of the negative cache node based on the bit identification corresponding to the query type comprises:
judging whether a cache bit identifier in a record type bitmap of the negative cache node comprises a bit identifier corresponding to the query type;
and if the cache bit identifier in the record type bitmap of the negative cache node does not comprise the bit identifier corresponding to the query type, setting the bit identifier corresponding to the query type as the cache bit identifier in the record type bitmap of the negative cache node.
9. The method of claim 7, wherein the method further comprises:
if the negative cache node does not have the negative response content, a new negative cache node is created;
calculating a bit identifier corresponding to the query type;
and updating the record type bitmap of the new negative cache node based on the bit identifier corresponding to the query type.
10. The method of claim 9, wherein updating the record type bitmap of the new negative cache node based on the bit identification corresponding to the query type comprises:
and setting the bit identifier corresponding to the query type as a cache bit identifier in a record type bitmap of the new negative cache node.
11. A domain name query system, comprising:
the client is used for sending a domain name query message, wherein the domain name query message comprises a query domain name and a query type;
the recursion server is connected with the client and is used for receiving the domain name query message; querying a negative cache node by using the query domain name, wherein the negative cache node uses the domain name and a record type bitmap as indexes to store the negative response content of the domain name query message, and the record type bitmap is provided with a bit identifier corresponding to the query type; judging whether the query domain name exists in the negative cache node; if the query domain name exists in the negative cache node, calculating a bit identifier corresponding to the query type; judging whether a bit identifier corresponding to the query type exists in the negative cache node; and if the bit identifier corresponding to the query type exists in the negative cache node, returning negative response content of the domain name query message.
12. An electronic device, comprising: a processor, and a memory storing a program, wherein the program comprises instructions that when executed by the processor cause the processor to perform the method of any one of claims 1 to 10.
13. A non-transitory machine readable medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1 to 10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310672952.7A CN116405463B (en) | 2023-06-07 | 2023-06-07 | Domain name query method, system, electronic device and non-transitory machine-readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310672952.7A CN116405463B (en) | 2023-06-07 | 2023-06-07 | Domain name query method, system, electronic device and non-transitory machine-readable medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116405463A true CN116405463A (en) | 2023-07-07 |
| CN116405463B CN116405463B (en) | 2023-08-11 |
Family
ID=87020241
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310672952.7A Active CN116405463B (en) | 2023-06-07 | 2023-06-07 | Domain name query method, system, electronic device and non-transitory machine-readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116405463B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103701957A (en) * | 2014-01-14 | 2014-04-02 | 互联网域名系统北京市工程研究中心有限公司 | Domain name server (DNS) recursive method and system thereof |
| CN104301346A (en) * | 2013-07-18 | 2015-01-21 | 政务和公益机构域名注册管理中心 | Caching method of DNS (Domain Name server) with negative existence |
| CN107613040A (en) * | 2017-09-22 | 2018-01-19 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus of domain name system DNS server lookup |
| US20210112034A1 (en) * | 2019-10-15 | 2021-04-15 | Cisco Technology, Inc. | Dynamic discovery of peer network devices across a wide area network |
| CN115858590A (en) * | 2022-12-14 | 2023-03-28 | 上海浦东发展银行股份有限公司 | Domain name query request processing method, computer device, apparatus, medium, and product |
-
2023
- 2023-06-07 CN CN202310672952.7A patent/CN116405463B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104301346A (en) * | 2013-07-18 | 2015-01-21 | 政务和公益机构域名注册管理中心 | Caching method of DNS (Domain Name server) with negative existence |
| CN103701957A (en) * | 2014-01-14 | 2014-04-02 | 互联网域名系统北京市工程研究中心有限公司 | Domain name server (DNS) recursive method and system thereof |
| CN107613040A (en) * | 2017-09-22 | 2018-01-19 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus of domain name system DNS server lookup |
| US20210112034A1 (en) * | 2019-10-15 | 2021-04-15 | Cisco Technology, Inc. | Dynamic discovery of peer network devices across a wide area network |
| CN115858590A (en) * | 2022-12-14 | 2023-03-28 | 上海浦东发展银行股份有限公司 | Domain name query request processing method, computer device, apparatus, medium, and product |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116405463B (en) | 2023-08-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106603394B (en) | Method and device for realizing subscription notification | |
| EP3668063A1 (en) | Domain name resolution method, server and system | |
| CN102984286B (en) | Method and device and system of domain name server (DNS) for buffering updating | |
| CN108429777B (en) | Data updating method based on cache and server | |
| CN106331212A (en) | Domain name server (DNS) cache camping-based domain name resolution method and system | |
| CN103905572A (en) | Domain name resolution request processing method and device | |
| CN111885216B (en) | DNS query method, device, equipment and storage medium | |
| CN116405460A (en) | Domain name resolution method and device for content distribution network, electronic equipment and storage medium | |
| CN113691646A (en) | Domain name service resource access method, device, electronic equipment and medium | |
| CN105592083A (en) | Method and device for terminal to have access to server by using token | |
| CN113055503B (en) | IPv6 webpage link processing method, device, equipment and readable storage medium | |
| CN116405463B (en) | Domain name query method, system, electronic device and non-transitory machine-readable medium | |
| CN111885212B (en) | Domain name storage method and device | |
| CN114124888A (en) | Domain name resolution method and device | |
| CN110995881A (en) | Domain name storage method and device | |
| CN111565195A (en) | Challenge black hole attack defense method of distributed system and distributed system | |
| CN114338630B (en) | Domain name access method, device, electronic equipment, storage medium and program product | |
| CN113285961B (en) | Electric power internal and external network information interaction method based on cache database | |
| EP3288242A1 (en) | Domain name system accessing method and device | |
| CN115086275B (en) | Message processing method, device, medium and electronic equipment | |
| CN110865845B (en) | Method for improving interface access efficiency and storage medium | |
| CN108073660B (en) | Method and system for realizing cache data synchronization | |
| CN113422772B (en) | Private network terminal access processing method and device and electronic equipment | |
| CN118101664A (en) | Block chain load balancing method, device, equipment and storage medium | |
| CN113746901B (en) | Data caching method and system |
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 |