# US 2020/0287985 A1 · Enhanced Domain Name System Response Caching

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0287985 A1
- Document ID: US20200287985A1
- Status: Published application
- Kind: A1
- Application number: 16/296,396
- Filed: 2019-03-08
- Published: 2020-09-10
- Earliest claimed: 2019-03-08
- Assignees: Charter Communications Operating, LLC
- Applicants: Charter Communications Operating, LLC
- Inventors: Ashutosh Kumar Sinha; Robert Dianda
- Web page: https://patentgrep.com/patent/US20200287985A1

## CPC

- H04L 61/58: Caching of addresses or names
- G06F 16/24552: {Database cache management}
- H04L 61/4511: using domain name system [DNS]
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Methods and systems for enhanced domain name system (DNS) response caching are described. An enhanced DNS response caching method includes receiving a connection request for a fully qualified domain name (FQDN). A DNS client checks a local cache for a cached resolved domain name corresponding to the FQDN and sends 3300 a query to obtain or refresh the cached resolved domain name if a Time to Live parameter is expired or about to expire. In response to receiving a negative response or no response for the query, the DNS client determines whether an enhanced DNS response caching parameter is enabled. If the enhanced DNS response caching parameter is enabled, the DNS client sends an expired cached resolved domain name to process the connection request.

## Claims

### Claim 1

A method for enhanced domain name system (DNS) response caching, the method comprising:
receiving a connection request for a fully qualified domain name (FQDN);
checking a local cache for a cached resolved domain name corresponding to the requested FQDN;
sending a query to refresh a matching cached resolved domain name;
receiving a negative response or no response for the query;
determining whether an enhanced DNS response caching parameter is enabled by using at least a type of DNS client device; and
sending, to process the connection request, an expired matching cached resolved domain name when the enhanced DNS response caching parameter is enabled.

### Claim 2 (depends on 1)

The method of claim 1, the method further comprising:
storing cached resolved domain names in the cache for time to live values specified in resolved domain name responses.

### Claim 3 (depends on 2)

The method of claim 2, the method further comprising:
maintaining, until a positive response is received, expired cached resolved domain names when the enhanced DNS response caching parameter is enabled.

### Claim 4 (depends on 2)

The method of claim 2, wherein the cached resolved domain names are refreshed when time to live values expire or are about to expire.

### Claim 5 (depends on 1)

The method of claim 1, wherein determination of enhanced DNS response caching parameter enablement uses type of the requested FQDN.

### Claim 6

(canceled)

### Claim 7 (depends on 1)

The method of claim 1, wherein determination of enhanced DNS response caching parameter enablement uses type of requesting device.

### Claim 8 (depends on 1)

The method of claim 1, wherein determination of enhanced DNS response caching parameter enablement uses type of application associated with the requested FQDN.

### Claim 9 (depends on 1)

The method of claim 1, wherein a default setting for the enhanced DNS response caching parameter is enabled for certain application types, certain DNS client device types, certain types of requesting devices, certain FQDN types or combinations thereof.

### Claim 10

A method for processing requests with domain name system (DNS) response failures, the method comprising:
checking for a cached resolved Internet Protocol (IP) address corresponding to a domain name in a request;
determining a type associated with the request by using an application type associated with the request when a response failure occurs for a query related to an identified cached resolved IP address;
setting a field based on the type to permit use of expired identified cached resolved IP address; and
sending the expired identified cached resolved IP address to process the request.

### Claim 11 (depends on 10)

The method of claim 10, the method further comprising:
storing cached resolved IP addresses in the cache for time to live values specified in resolved IP responses.

### Claim 12 (depends on 11)

The method of claim 11, the method further comprising:
not flushing, until a positive response is received, expired cached resolved IP addresses when the field is set.

### Claim 13 (depends on 11)

The method of claim 11, the method further comprising:
renewing the cached resolved IP addresses relative to time to live expiry.

### Claim 14 (depends on 10)

The method of claim 10, wherein determination of the type uses the requested domain name.

### Claim 15 (depends on 10)

The method of claim 10, wherein determination of the type uses type of DNS client device.

### Claim 16

(canceled)

### Claim 17 (depends on 410)

The method of claim 410, wherein determination of the type uses type of requesting device.

### Claim 18 (depends on 10)

The method of claim 10, wherein a default setting for the field is enabled for certain types of applications, certain types of DNS client devices, certain types of FQDNs, certain types of requesting devices or combinations thereof.

### Claim 19

A domain name system (DNS) device comprising:
a DNS client configured to issue DNS queries to DNS servers;
a memory configured to:
store resolved Internet Protocol (IP) addresses;
time to live values associated with the stored resolved IP addresses; and
an enablement flag, wherein setting the enablement flag allows use of stored resolved IP addresses; and
a processor in cooperation with the DNS client and memory configured to:
check for a stored resolved IP address corresponding to a domain name request;
determine a type associated with the domain name request by checking type of requesting device;
set the enablement flag based on the type; and
send an expired identified stored resolved IP address to process the domain name request when a response failure occurs for a query related to the identified stored resolved IP address.

### Claim 20 (depends on 19)

The DNS device of claim 19, the processor further configured to:
not flush, until a positive response is received, expired stored resolved IP addresses when the enablement flag is set.
