Methods and systems for data retrieval
A method for use by a Domain Name System (DNS) resolver includes: obtaining a first identifier that the DNS resolver associates with cache data, the cache data comprising at least a portion of one or more DNS resource records; receiving or obtaining a second identifier that an DNS nameserver associates with current data; determining whether the first identifier corresponds to the second identifier; and performing an action to maintain or update the cache data based on whether the first identifier corresponds to the second identifier.
1 . A computer-implemented method for use by a Domain Name System (DNS) nameserver, the computer-implemented method comprising:
obtaining a first identifier that the DNS nameserver associates with current data, the current data comprising at least a portion of one or more DNS resource records;
receiving or obtaining a second identifier that a DNS recursive resolver associates with cache data;
determining whether the first identifier corresponds to the second identifier; and
sending, from the DNS nameserver to the DNS recursive resolver, an indication to maintain the cache data in response to determining that the first identifier corresponds to the second identifier.
2 . The computer-implemented method of claim 1 , wherein the indication indicates to increase a time-to-live associated with the cache data.
3 . The computer-implemented method of claim 1 , wherein, when the first identifier does not correspond to the second identifier:
sending, to the DNS recursive resolver, an indication to update the cache data; and
sending, to the DNS recursive resolver, at least a portion of the current data or a reference to at least a portion of the current data.
4 . The computer-implemented method of claim 1 , determining the first identifier does not correspond to the second identifier:
sending, to the DNS recursive resolver, an indication to update the cache data; and
sending, to the DNS recursive resolver, at least a portion of the current data, wherein the at least a portion of the current data is sent via a connectionless protocol.
5 . The computer-implemented method of claim 4 , wherein the connectionless protocol is User Datagram Protocol (UDP).
6 . The computer-implemented method of claim 1 , wherein determining whether the first identifier corresponds to the second identifier is in response to a timer expiry.
7 . The computer-implemented method of claim 1 , wherein determining whether the first identifier corresponds to the second identifier is in response to a request from the DNS recursive resolver.
8 . The computer-implemented method of claim 1 , wherein determining that the first identifier corresponds to the second identifier indicates that the current data corresponds to the cache data.
9 . The computer-implemented method of claim 1 , wherein the at least a portion of the one or more DNS resource records comprises information used for DNS Security Extensions (DNSSEC) validation.
10 . The computer-implemented method of claim 9 , wherein the information used for DNSSEC validation comprises a key or a signature.
11 . The computer-implemented method of claim 1 , wherein obtaining the first identifier comprises retrieving the first identifier from memory of the DNS nameserver.
12 . The computer-implemented method of claim 1 , wherein obtaining the first identifier comprises dynamically calculating the first identifier by the DNS nameserver.
13 . The computer-implemented method of claim 1 , wherein the first identifier is derived from the current data and the second identifier is derived from the cache data.
14 . The computer-implemented method of claim 1 , wherein the first identifier comprises a hash of the current data and the second identifier comprises a hash of the cache data.
15 . The computer-implemented method of claim 1 , wherein the first identifier comprises a subset of a hash of the current data and the second identifier comprises a subset of a hash of the cache data.
16 . The computer-implemented method of claim 1 , wherein the first identifier comprises a subset of the current data and the second identifier comprises a subset of the cache data.
17 . The computer-implemented method of claim 1 , wherein the first identifier and the second identifier are each managed by the DNS nameserver, wherein the first identifier is bound to the current data and the second identifier is bound to the cache data.
18 . The computer-implemented method of claim 17 , wherein the DNS nameserver is configured to validate that the first identifier is for the current data, and the DNS nameserver is configured to validate that the second identifier is for the cache data.
19 . The computer-implemented method of claim 1 , wherein the first identifier is a first verifiable instance identifier (VIID) and the second identifier is a second VIID.
20 . The computer-implemented method of claim 19 , wherein
the first VIID and the second VIID are verifiably associated with data instances.
21 . The computer-implemented method of claim 19 , wherein the first VIID and the second VIID are labeled as label VIIDs, wherein the label VIID is a unique identifier assigned to a data instance by an authoritative source.
22 . The computer-implemented method of claim 19 , wherein the first VIID and the second VIID are not cryptographically derived.
23 . The computer-implemented method of claim 1 , the computer-implemented method further comprising:
receiving a request for at least a portion of the current data from the DNS recursive resolver; and
facilitating out-of-band transfer of the at least a portion of the current data to the DNS recursive resolver.
24 . The computer-implemented method of claim 23 , wherein facilitating the out-of-band transfer of the at least a portion of the current data is based at least in part on determining that a size of the at least a portion of the current data exceeds a threshold.
25 . The computer-implemented method of claim 23 , wherein facilitating the out-of-band transfer of the at least a portion of the current data comprises indicating, to the DNS recursive resolver, a reference to an out-of-band source from which to retrieve at least a portion of the current data.
26 . The computer-implemented method of claim 1 , wherein the first identifier comprises a reference to an out-of-band data source from which to receive at least a portion of the current data.
27 . The computer-implemented method of claim 1 , the computer-implemented method further comprising:
receiving a granular request for data from a DNS recursive resolver, the granular request requesting a portion of the current data comprising less than a full resource record (RR) set; and
sending, to the DNS recursive resolver, the portion of the current data or a reference to an out-of-band source from which to retrieve the portion of the current data.
28 . The computer-implemented method of claim 27 , wherein the granular request indicates one or more requested RRs selected from the full RR set.
29 . The computer-implemented method of claim 27 , wherein the granular request indicates one or more requested elements of one or more RRs selected from the full RR set.
30 . The computer-implemented method of claim 1 , wherein the second identifier is received from the DNS recursive resolver.
31 . The computer-implemented method of claim 1 , wherein the current data comprises authoritative data instances, and the cached data comprises cached data instances.
32 . An apparatus for use by a Domain Name System (DNS) nameserver, the apparatus comprising one or more processors and one or more non-transitory computer-readable media storing instructions that, when executed by the one or more processors, cause the apparatus to perform operations comprising:
obtaining a first identifier that the DNS nameserver associates with current data, the current data comprising at least a portion of one or more DNS resource records;
receiving or obtaining a second identifier that a DNS recursive resolver associates with cache data;
determining whether the first identifier corresponds to the second identifier; and
sending, from the DNS nameserver to the DNS recursive resolver, an indication to maintain the cache data in response to determining that the first identifier corresponds to the second identifier.
33 . A system for use by a Domain Name System (DNS) nameserver, the system comprising one or more processors and one or more non-transitory computer-readable media storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
obtaining a first identifier that the DNS nameserver associates with current data, the current data comprising at least a portion of one or more DNS resource records;
receiving or obtaining a second identifier that a DNS recursive resolver associates with cache data;
determining whether the first identifier corresponds to the second identifier; and
sending, from the DNS nameserver to the DNS recursive resolver, an indication to maintain the cache data in response to determining that the first identifier corresponds to the second identifier.
34 . One or more non-transitory computer-readable media for use by a Domain Name System (DNS) nameserver, the one or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause the performance of operations comprising:
obtaining a first identifier that the DNS nameserver associates with current data, the current data comprising at least a portion of one or more DNS resource records;
receiving or obtaining a second identifier that a DNS recursive resolver associates with cache data;
determining whether the first identifier corresponds to the second identifier; and
sending, from the DNS nameserver to the DNS recursive resolver, an indication to maintain the cache data in response to determining that the first identifier corresponds to the second identifier.