US 12,423,157 B2
Systems and methods providing serverless DNS integration
Kyle Andrew Donald Mestery, Woodbury, MN (US); Ian Wells, San Jose, CA (US); and David Delano Ward, Somerset, WI (US)
Assigned to Cisco Technology, Inc., San Jose, CA (US)
Filed by Cisco Technology, Inc., San Jose, CA (US)
Filed on Feb. 6, 2024, as Appl. No. 18/434,276.
Application 18/434,276 is a continuation of application No. 16/518,242, filed on Jul. 22, 2019, granted, now 11,928,514.
Prior Publication US 2024/0176672 A1, May 30, 2024
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 67/53 (2022.01); G06F 9/50 (2006.01); H04L 43/16 (2022.01); H04L 67/1004 (2022.01); H04L 67/1008 (2022.01); H04L 67/1031 (2022.01)
CPC G06F 9/505 (2013.01) [H04L 67/53 (2022.05); H04L 43/16 (2013.01); H04L 67/1004 (2013.01); H04L 67/1008 (2013.01); H04L 67/1031 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method comprising:
receiving, via a computing device managing an application programing interface (API) and from one of an internal client or an external client, a domain name system request;
communicating, from the computing device, the domain name system request to a domain name system;
notifying an orchestrator system of data associated with the domain name system request, wherein the data indicates that the orchestrator system needs to quickly spin up a function associated with an entity comprising one of a virtual machine, one or more containers or a physical node according to: (1) a geographic component which can impact a location of the entity as being closer to an existing function or a client that made the domain name system request and (2) a function distribution algorithm, operated by the orchestrator system, that implements a chosen pattern of distributing functions across nodes based on domain name system requests and system usage;
provisioning, by the orchestrator system and based on the data and the geographic component and the chosen pattern of distributing functions across nodes, the function on the entity;
notifying, by the orchestrator system, a load balancer regarding the entity operating the function, wherein the load balancer is a separate device from the domain name system;
providing a response to the domain name system request;
receiving an API request from one of the internal client or the external client and via the API operating on the computing device;
when the API request is from the external client, routing, via the computing device operating the API, the API request directly to the load balancer and routing, by the load balancer, the API request associated with the domain name system request to the entity; and
when the API request is from the internal client, routing, via the computing device operating the API, the API request from the internal client to the entity.