IP Library Granted Patent US 11,848,911
Granted Patent B2
US 11,848,911 · App. 18/079,040 · Granted Dec 19, 2023

Federated DNS caching

Inventors: Michael Feldpusch (Westminster, CO); Dan Luther (Claremore, OK)
Assignee: Level 3 Communications, LLC
H04L61/58H04L61/4511H04L61/5076
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,848,911
App. No.
18/079,040
Granted
Dec 19, 2023
Kind
B2
Abstract

Systems and methods are provided for distributing a domain name service (DNS) response cache in a DNS resolving system on a network. The systems and methods described herein may improve response times for client queries and also protect the DNS resolving system from DNS related cyber attacks.

Claims (37)

1. A method, comprising:

receiving a Domain Name Service (DNS) query from a client device;

providing the DNS query to a DNS resolver;

causing the DNS resolver to determine that the hostname associated with the DNS query is not stored in a resolver cache of the DNS resolver;

providing the DNS query to a DNS recursive server, the DNS recursive server being associated with the DNS resolver and another DNS resolver and communicatively coupled to an authoritative DNS server; and

causing the DNS resolver to determine whether the hostname associated with the DNS query is stored in a recursor cache of the DNS recursive server.

2. The method of claim 1 , further comprising causing the resolver cache of the DNS resolver to be updated with the hostname associated with the DNS query.

3. The method of claim 1 , further comprising causing the DNS resolver to provide a response to the client device, the response including the hostname associated with the DNS query.

4. The method of claim 1 , further comprising causing the DNS recursive server to provide the DNS query to the authoritative DNS server based on a determination that the hostname associated with the DNS query is not stored in the recursor cache of the DNS recursive server.

5. The method of claim 4 , further comprising causing the recursor cache of the DNS recursive server to be updated based, at least in part, on a response to the DNS query provided by the authoritative DNS server.

6. The method of claim 5 , further comprising causing the resolver cache of the DNS resolver to be updated based, at least in part, on the response to the DNS query provided by the authoritative DNS server.

7. The method of claim 1 , wherein the recursor cache is larger than the resolver cache.

8. The method of claim 1 , wherein a time-to-live of entries in the recursor cache is longer than a time-to-live of entries in the resolver cache.

9. A system, comprising:

a Domain Name Service (DNS) resolver having a resolver cache; and

a DNS recursive server having a recursor cache, the DNS recursive server communicatively coupled to the DNS resolver and an authoritative DNS server, the DNS recursive server operable to:

receive a DNS query from the DNS resolver based on the DNS resolver determining that a hostname associated with a received DNS query is not stored in the resolver cache;

determine that the hostname associated with the DNS query is stored in a recursor cache of the DNS recursive server; and

provide the hostname associated with the DNS query to the DNS resolver.

10. The system of claim 9 , wherein the DNS recursive server is further operable to provide the DNS query to the authoritative DNS server based on determining that the hostname associated with the DNS query is not stored in the recursor cache of the DNS recursive server.

11. The system of claim 10 , wherein the DNS recursive server is further operable to store the hostname associated with the DNS query in the recursor cache when the hostname associated with the DNS query is received from the authoritative DNS server.

12. The system of claim 9 , wherein the recursor cache is larger than the resolver cache.

13. A system, comprising:

a processor; and

a memory coupled to the at least one processor and storing instructions that, when executed by the processor, perform operations, comprising:

receiving a Domain Name Service (DNS) query from a client device;

providing the DNS query to a DNS resolver;

causing the DNS resolver to determine that a hostname associated with the DNS query is not stored in a resolver cache of the DNS resolver;

providing the DNS query to a DNS recursive server, the DNS recursive server being associated with the DNS resolver and another DNS resolver and communicatively coupled to an authoritative DNS server; and

causing the DNS resolver to determine whether the hostname associated with the DNS query is stored in a recursor cache of the DNS recursive server.

14. The system of claim 13 , further comprising instructions for causing the resolver cache of the DNS resolver to be updated with the hostname associated with the DNS query.

15. The system of claim 13 , further comprising instructions for causing the DNS resolver to provide a response to the client device, the response including the hostname associated with the DNS query.

16. The system of claim 13 , further comprising instructions for causing the DNS recursive server to provide the DNS query to the authoritative DNS server based on a determination that the hostname associated with the DNS query is not stored in the recursor cache of the DNS recursive server.

17. The system of claim 16 , further comprising instructions for causing the recursor cache of the DNS recursive server to be updated based, at least in part, on a response to the DNS query provided by the authoritative DNS server.

18. The system of claim 17 , further comprising instructions for causing the resolver cache of the DNS resolver to be updated based, at least in part, on the response to the DNS query provided by the authoritative DNS server.

19. The system of claim 13 , wherein the recursor cache is larger than the resolver cache.

20. The system of claim 13 , wherein the DNS resolver and the another DNS resolver are communicatively coupled to the DNS recursive server but not to the authoritative DNS server.

Assignments (3)
NOTICE OF GRANT OF SECURITY INTEREST IN INTELLECTUAL PROPERTY (SECOND LIEN) Recorded Nov 4, 2024
From: LEVEL 3 COMMUNICATIONS, LLC; GLOBAL CROSSING TELECOMMUNICATIONS, INC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 069295/0749 →
NOTICE OF GRANT OF SECURITY INTEREST IN INTELLECTUAL PROPERTY (FIRST LIEN) Recorded Nov 4, 2024
From: LEVEL 3 COMMUNICATIONS, LLC; GLOBAL CROSSING TELECOMMUNICATIONS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 069295/0858 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 13, 2022
From: FELDPUSCH, MICHAEL; LUTHER, DAN
To: LEVEL 3 COMMUNICATIONS, LLC
Reel/Frame 062065/0441 →