# US 2022/0286431 A1 · Dns resolver-assisted domain name-based access control

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

- Number: US 2022/0286431 A1
- Document ID: US20220286431A1
- Status: Published application
- Kind: A1
- Application number: 17/194,622
- Filed: 2021-03-08
- Published: 2022-09-08
- Earliest claimed: 2021-03-08
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Adam Gregory Winn; Jeffrey Gino Fanelli; Brian Levin
- Web page: https://patentgrep.com/patent/US20220286431A1

## CPC

- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L 61/4511: using domain name system [DNS]
- H04L 61/5007: Internet protocol [IP] addresses
- H04L 63/0263: {Rule management}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L 61/2503: Translation of Internet protocol [IP] addresses
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A domain name system (DNS) resolver includes a processor and a non-transitory computer-readable media storing instructions that, when executed by the processor, causes the processor to perform operations including receiving, from a client device, a request for an internet protocol (IP) address associated with a domain name, determining the IP address associated with the domain name, sending first data defining the IP address associated with the domain name to the client device, and sending second data defining the IP address associated with the domain name to a firewall device, the second data including an identification of the client device.

## Claims

### Claim 1

A domain name system (DNS) resolver comprising:
a processor; and
a non-transitory computer-readable media storing instructions that, when executed by the processor, causes the processor to perform operations comprising:
receiving, from a client device, a request for an internet protocol (IP) address associated with a domain name;
determining the IP address associated with the domain name;
sending first data defining the IP address associated with the domain name to the client device; and
sending second data defining the IP address associated with the domain name to a firewall device, the second data including an identification of the client device.

### Claim 2 (depends on 1)

The DNS resolver of claim 1, wherein the second data defining the IP address associated with the domain name is sent to the firewall device based at least in part on the receiving, from the client device, the request for the IP address associated with the domain name.

### Claim 3 (depends on 1)

The DNS resolver of claim 1, wherein sending the second data further includes sending at least one additional IP address associated with the domain name, the additional IP address being associated with a subdomain under the domain name.

### Claim 4 (depends on 1)

The DNS resolver of claim 1, wherein the domain name is a fully qualified domain name (FQDN).

### Claim 5 (depends on 1)

The DNS resolver of claim 1, the operations further comprising receiving, from the client device, a notification of an association between the client device and the firewall device, wherein the sending of the second data to the firewall device is performed based at least in part on an identification by the client device of the firewall device in the notification.

### Claim 6 (depends on 1)

The DNS resolver of claim 1, wherein the DNS resolver and the firewall device are executed within a cloud computing-based network infrastructure.

### Claim 7

A domain name system (DNS) server, comprising:
a DNS resolver;
a firewall device communicatively coupled to the DNS resolver;
a processor; and
a non-transitory computer-readable media storing instructions that, when executed by the processor, causes the processor to perform operations comprising:
with the DNS resolver:
receiving, at the DNS resolver, an access policy associated with the firewall device based at least in part on a creation of the access policy at the firewall device;
receiving, from a client device, a request for an internet protocol (IP) address associated with a domain name;
determining the IP address associated with the domain name;
sending first data defining the IP address associated with the domain name to the client device;
sending second data defining the IP address associated with the domain name to the firewall device, the second data including an identification of the client device;
with the firewall device:
generating a domain name registry (DNR) entry of the second data defining the IP address associated with the domain name including the identification of the client device;
receiving a data packet from the client device addressed to the IP address based at least in part on the sending of the first data defining the IP address associated with the domain name to the client device;
inspecting the data packet for the IP address; and
determining that the IP address matches the domain name within the DNR entry.

### Claim 8 (depends on 7)

The DNS server of claim 7, the operations further comprising restricting the data packet from transmission to the IP address based at least in part on the IP address matching the domain name within the DNR entry.

### Claim 9 (depends on 7)

The DNS server of claim 7, wherein the sending of the second data defining the IP address associated with the domain name is sent to the firewall device based at least in part on the receiving, from the client device, the request for the IP address associated with the domain name.

### Claim 10 (depends on 7)

The DNS server of claim 7, wherein sending the second data further includes sending at least one additional IP address associated with the domain name, the additional IP address being associated with a subdomain under the domain name.

### Claim 11 (depends on 7)

The DNS server of claim 7, wherein the domain name is a fully qualified domain name (FQDN).

### Claim 12 (depends on 7)

The DNS server of claim 7, the operations further comprising, with the DNS resolver, receiving, from the client device, a notification of an association between the client device and the firewall device,
wherein the sending of the second data to the firewall device is performed based at least in part on an identification by the client device of the firewall device in the notification.

### Claim 13 (depends on 7)

The DNS server of claim 7, wherein the DNS server including the DNS resolver and the firewall device includes a cloud computing-based network infrastructure.

### Claim 14

A non-transitory computer-readable medium storing instructions that, when executed, causes a processor to perform operations, comprising, with a firewall device communicatively coupled to a DNS resolver:
generating a domain name registry (DNR) entry of first data defining an internet protocol (IP) address associated with a domain name based at least in part on a DNS query request from a client device, the first data defining the internet protocol (IP) address associated with the domain name being sent from the DNS resolver;
receiving a data packet from the client device addressed to the IP address;
inspecting the data packet for the IP address; and
determining that the IP address matches the domain name within the DNR entry.

### Claim 15 (depends on 14)

The non-transitory computer-readable medium of claim 14, the operations further comprising:
receiving an access policy, the access policy identifying the domain name; and
sending the access policy to the DNS resolver.

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the access policy is at least one of a layer-3 access policy and a layer-4 access policy.

### Claim 17 (depends on 14)

The non-transitory computer-readable medium of claim 14, the operations further comprising restricting the data packet from transmission to the IP address based at least in part on the IP address matching the domain name within the DNR entry.

### Claim 18 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein the receiving the data packet from the client device is based at least in part on the DNS resolver sending second data defining the IP address associated with the domain name to the client device.

### Claim 19 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein:
the domain name is a fully qualified domain name (FQDN), and
the first data further includes at least one additional IP address associated with the domain name, the additional IP address being associated with a subdomain under the domain name.

### Claim 20 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein the DNS resolver and firewall device are executed within a cloud computing-based network infrastructure.
