# US 2022/0286515 A1 · Policy-based connection provisioning using domain name system (dns) requests

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

- Number: US 2022/0286515 A1
- Document ID: US20220286515A1
- Status: Published application
- Kind: A1
- Application number: 17/826,003
- Filed: 2022-05-26
- Published: 2022-09-08
- Earliest claimed: 2020-06-30
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Paul Quinn; Kyle Andrew Donald Mestery
- Web page: https://patentgrep.com/patent/US20220286515A1

## CPC

- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- H04L 41/0894: Policy-based network configuration management
- H04L 41/5058: {Service discovery by the service manager}
- H04L 61/4511: using domain name system [DNS]
- H04L 67/1001: for accessing one among a plurality of replicated servers
- H04L 2101/668: Internet protocol [IP] address subnets
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Techniques for policy-based connection provisioning using Domain Name System (DNS) requests are described herein. The techniques may include receiving policy data associated with one or more headend nodes that manage connections to computing resources. Additionally, the techniques may include receiving a DNS request from a client device to establish a connection between the client device and a first headend node of the one or more headend nodes. The DNS request may include an attribute associated with the client device. A provisioning service may determine that the connection should be established between the client device and the first headend node based at least in part on evaluating the attribute with respect to the policy data. Additionally, the techniques may include sending an internet protocol (IP) address, which is associated with the first headend node, to the client device to facilitate establishment of the connection.

## Claims

### Claim 1

A policy service associated with a cloud-delivered virtual private network (VPN) service, the policy service 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 policy service to perform operations comprising:
receiving policy data associated with one or more headend nodes of the cloud-delivered VPN service that manage connections to backend computing resources;
receiving a policy query from a domain name system (DNS) server associated with the cloud-delivered VPN service, the policy query including at least a DNS request and an indication of a client device that sent the DNS request;
based at least in part on evaluating an attribute associated with the client device with respect to the policy data, determining that a communication connection is to be established between the client device and a first headend node of the one or more headend nodes to provide the client device with access to a backend computing resource; and
causing an indication of an internet protocol (IP) address associated with the first headend node to be sent to the client device to facilitate establishment of the communication connection.

### Claim 2 (depends on 1)

The policy service of claim 1, wherein causing the indication of the IP address to be sent to the client device comprises sending the IP address to the DNS server.

### Claim 3 (depends on 1)

The policy service of claim 1, the operations further comprising determining the attribute associated with the client device based at least in part on the policy query including the indication of the client device.

### Claim 4 (depends on 1)

The policy service of claim 1, wherein the policy data comprises at least one of a type associated with respective ones of the one or more headend nodes, a size associated with respective ones of the one or more headend nodes, or capabilities associated with respective ones of the one or more headend nodes.

### Claim 5 (depends on 1)

The policy service of claim 1, wherein the attribute associated with the client device is an identifier associated with the client device.

### Claim 6 (depends on 1)

The policy service of claim 1, wherein the attribute associated with the client device is an identifier associated with a user of the client device.

### Claim 7 (depends on 1)

The policy service of claim 1, wherein the attribute associated with the client device is at geographic location associated with the client device.

### Claim 8 (depends on 6)

The policy service of claim 6, wherein determining that the communication connection is to be established between the client device and the first headend node is based at least in part on a determination that the first headend node is within a threshold proximity of the geographic location.

### Claim 9 (depends on 1)

The policy service of claim 1, the operations further comprising:
receiving telemetry data indicating a capacity of the backend computing resource;
determining that the capacity is less than a threshold capacity; and
wherein the determining that the communication connection is to be established between the client device and the first headend node is further based at least in part on the capacity being less than the threshold capacity.

### Claim 10 (depends on 1)

The policy service of claim 1, wherein the communication connection between the client device and the first headend node is a VPN connection.

### Claim 11

One or more non-transitory computer-readable media storing instructions that, when executed, cause one or more processors perform operations comprising:
receiving policy data associated with one or more headend nodes of a virtual private network (VPN) headend service, the one or more headend nodes configured to manage connections to backend computing resources;
receiving a policy query from a domain name system (DNS) server associated with the VPN headend service, the policy query including at least a DNS request and an indication of a client device that sent the DNS request;
based at least in part on evaluating an attribute associated with the client device with respect to the policy data, determining that a communication connection is to be established between the client device and a first headend node of the one or more headend nodes; and
causing an indication of an internet protocol (IP) address associated with the first headend node to be sent to the client device to facilitate establishment of the communication connection.

### Claim 12 (depends on 11)

The one or more non-transitory computer-readable media of claim 11, wherein causing the indication of the IP address to be sent to the client device comprises sending the IP address to the DNS server.

### Claim 13 (depends on 11)

The one or more non-transitory computer-readable media of claim 11, the operations further comprising determining the attribute associated with the client device based at least in part on the policy query including the indication of the client device.

### Claim 14 (depends on 11)

The one or more non-transitory computer-readable media of claim 11, wherein the communication connection between the client device and the first headend node is a VPN connection that provides the client device with access to one or more of the backend computing resources.

### Claim 15 (depends on 11)

The one or more non-transitory computer-readable media of claim 11, wherein the policy data comprises at least one of a type associated with respective ones of the one or more headend nodes, a size associated with respective ones of the one or more headend nodes, or capabilities associated with respective ones of the one or more headend nodes.

### Claim 16 (depends on 11)

The one or more non-transitory computer-readable media of claim 11, wherein the attribute associated with the client device is at least one of an identifier associated with the client device, an identifier associated with a user of the client device, or a geographic location associated with the client device.

### Claim 17 (depends on 11)

The one or more non-transitory computer-readable media of claim 11, wherein determining that the communication connection is to be established between the client device and the first headend node is based at least in part on a determination that the first headend node is within a threshold proximity of the geographic location.

### Claim 18

A method comprising:
receiving, from a domain name system (DNS) server associated with a virtual private network (VPN) headend service, a policy query including an indication of a client device that sent a DNS request;
based at least in part on the policy query, evaluating an attribute associated with the client device with respect to a policy associated with a headend node of the VPN headend service;
determining, based at least in part on evaluating the attribute with respect to the policy, that a communication connection is to be established between the client device and the headend node; and
causing an indication of an internet protocol (IP) address associated with the headend node to be sent to the client device to facilitate establishment of the communication connection.

### Claim 19 (depends on 18)

The method of claim 18, further comprising:
evaluating the attribute with respect to another policy associated with another headend node of the VPN headend service; and
wherein determining that the communication connection is to be established between the client device and the headend node is further based at least in part on a determination that the headend node is a greater node for establishing the communication connection with than the other headend node.

### Claim 20 (depends on 18)

The method of claim 18, wherein the communication connection between the client device and the headend node is a VPN connection that provides the client device with access to one or more backend computing resources.
