IP Library Granted Patent US 10,356,097
Granted Patent B2
US 10,356,097 · App. 15/836,685 · Granted Jul 16, 2019

Domain name system and method of operating using restricted channels

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 10,356,097
App. No.
15/836,685
Granted
Jul 16, 2019
Kind
B2
Abstract

A server system for a domain name system (DNS) which operates to concurrently provide both public-facing and restricted channels for receiving and handling Internet Protocol (IP) address requests from a population of computers. The server system implements an alternative DNS request handling process to provide a trusted computer entity with exclusive access to the restricted channels.

Claims (43)

1. A method for resolving domain name service (DNS) requests received from a plurality of channels, the method comprising:

receiving, via a publicly-facing channel, a first DNS request from a first host device;

generating a first response to the first DNS request based on a name and address manager;

transmitting the first response to the first host device;

receiving, via a restricted channel, a second DNS request from a second host device;

generating a second response to the second DNS request based on the name and address manager; and

transmitting the second response to the second host device,

wherein, in response to a detection of a denial of service attack (DOS), the first host device transmits at least one of subsequent DNS requests via the restricted channel, and the method further comprises transmitting responses to the at least one of the subsequent DNS requests via the restricted channel.

2. The method of claim 1 , further comprising: transmitting configuration data to the second host, and wherein the second host, based on the configuration data, configures itself to use the restricted channel to transmit DNS requests.

3. The method of claim 2 , wherein the second host is an entity trusted by the DNS.

4. The method of claim 2 , wherein the configuration data includes an encryption key that is used by the second host communicate requests using the restricted channel.

5. The method of claim 2 , wherein the configuration data is used by the second host to create a persistent point-to-point connection with the DNS using the restricted channel.

6. The method of claim 1 , further comprising dynamically allocating resources to increase or decrease a capacity of the DNS to handle requests from the restricted channel.

7. The method of claim 6 , wherein dynamically allocating resources includes reallocating resources of the DNS server system to handle requests from the public-facing channel towards increasing the capacity to handle requests from the restricted channel.

8. The method of claim 1 , wherein the public channel and the restricted channel each include a set of network ports that are designated for the respective channel.

9. The method of claim 1 , further comprising receiving, via the restricted channel, the first DNS request from the first host device, wherein the first response is transmitted to the first host device via the restricted channel, and wherein the first host device transmits the first DNS request via the restricted channel in response to a detection of a denial of service (DOS) attack.

10. The method of claim 1 , wherein the second host is a server associated with an Internet Service Provider.

11. A server for resolving domain name service (DNS) requests received from a plurality of channels, the server comprising:

a memory to store a set of instructions;

one or more processors configured to:

receive, via a publicly-facing channel, a first DNS request from a first host device;

generate a first response to the first DNS request based on a name and address manager;

transmit the first response to the first host device;

receive, via a restricted channel, a second DNS request from a second host device;

generate a second response to the second DNS request based on the name and address manager; and

transmit the second response to the second host device,

wherein, in response to a detection of a denial of service attack (DOS), the first host device transmits at least one of subsequent DNS requests via the restricted channel, and the one or more processors are further configured to transmit responses to the at least one of the subsequent DNS requests via the restricted channel.

12. The server of claim 11 , further comprising: transmitting configuration data to the second host, and wherein the second host, based on the configuration data, configures itself to use the restricted channel to transmit DNS requests.

13. The server of claim 12 , wherein the second host is an entity trusted by the DNS.

14. The server of claim 12 , wherein the configuration data includes an encryption key that is used by the second host to communicate requests using the restricted channel.

15. The server of claim 12 , wherein the configuration data is used by the second host to create a persistent point-to-point connection with the DNS using the restricted channel.

16. The server of claim 11 , further comprising dynamically allocating resources to increase or decrease a capacity of the DNS to handle requests from the restricted channel.

17. The server of claim 11 , wherein the public channel and the restricted channel each include a set of network ports that are designated for the respective channel.

18. The server of claim 11 , further comprising receiving, via the restricted channel, the first DNS request from the first host device, wherein the first response is transmitted to the first host device via the restricted channel, and wherein the first host device transmits the first DNS request via the restricted channel in response to a detection of a denial of service (DOS) attack.

19. The server of claim 11 , wherein the second host is a server associated with an Internet Service Provider.

20. A non-transitory computer-readable medium to store instructions that, when executed by one or more processors of a server for resolving domain name service (DNS) requests received from a plurality of channels, cause the computer system to perform operations that include:

receiving, via a publicly-facing channel, a first DNS request from a first host device;

generating a first response to the first DNS request based on a name and address manager;

transmitting the first response to the first host device;

receiving, via a restricted channel, a second DNS request from a second host device;

generating a second response to the second DNS request based on the name and address manager; and

transmitting the second response to the second host device,

wherein, in response to a detection of a denial of service attack (DOS), the first host device transmits at least one of subsequent DNS requests via the restricted channel, and the operations further include transmitting responses to the at least one of the subsequent DNS requests via the restricted channel.

Assignments (9)
FIRST LIEN INTELLECTUAL PROPERTY AGREEMENT SUPPLEMENT Recorded Sep 24, 2025
From: DIGICERT, INC.
To: HPS INVESTMENT PARTNERS, LLC, AS COLLATERAL AGENT
Reel/Frame 072947/0203 →
ASSIGNMENT OF SECURITY INTERESTS IN INTELLECTUAL PROPERTY (FIRST LIEN), RECORDED ON JANUARY 23, 2025 AT REEL 069991 FRAME 0390 Recorded Sep 24, 2025
From: UBS AG, STAMFORD BRANCH, AS RESIGNING AGENT
To: HPS INVESTMENT PARTNERS, LLC, AS SUCCESSOR AGENT
Reel/Frame 072928/0289 →
SECOND LIEN INTELLECTUAL PROPERTY SECURITY AGREEMENT SUPPLEMENT Recorded Jul 30, 2025
From: DIGICERT, INC.
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 072295/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 21, 2025
From: VERCARA, LLC
To: DIGICERT, INC.
Reel/Frame 071781/0348 →
SECOND LIEN INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Jan 23, 2025
From: VERCARA, LLC
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 069991/0330 →
FIRST LIEN INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Jan 23, 2025
From: VERCARA, LLC
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 069991/0390 →
CHANGE OF NAME Recorded Mar 21, 2024
From: SECURITY SERVICES, LLC
To: VERCARA, LLC
Reel/Frame 066867/0462 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 30, 2021
From: NEUSTAR, INC.
To: SECURITY SERVICES, LLC
Reel/Frame 057327/0418 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 21, 2018
From: JOFFE, RODNEY LANCE; KING, DAVID LINK
To: NEUSTAR, INC.
Reel/Frame 046169/0131 →