# US 12,192,361 B2 · Shared registration system

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

- Number: US 12,192,361 B2
- Document ID: US12192361B2
- Status: Granted
- Kind: B2
- Application number: 18/099,825
- Filed: 2023-01-20
- Published: 2023-05-18
- Granted: 2025-01-07
- Earliest claimed: 2015-12-28
- Assignees: VeriSign, Inc.
- Applicants: Verisign, Inc.
- Inventors: Burton S. Kaliski, Jr.; Scott Hollenbeck
- Web page: https://patentgrep.com/patent/US12192361B2

## CPC

- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- G06F 21/33: using certificates
- G06F 21/335: {for accessing specific resources, e.g. using Kerberos tickets}
- H04L 9/321: {involving a third party or a trusted authority}
- H04L 61/302: {Administrative registration, e.g. for domain names at internet corporation for assigned names and numbers [ICANN]}
- H04L 61/4511: using domain name system [DNS]
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods for updating a Domain Name System (DNS) registry are disclosed. Embodiments perform operations including maintaining a domain name record of a DNS registrant recorded in a database of the DNS registry by a primary DNS interface. The operations also include receiving a request to update the domain name record of the DNS registrant via a secondary DNS interface. The operations further include modifying the domain name record of the DNS registrant in the DNS database in accordance with the request.

## Claims

### Claim 1

A method of managing a domain name system (DNS) record by a first DNS service provider comprising:
receiving, by the first DNS service provider, an authorization to manage a DNS record associated with a domain name, wherein an indication of the authorization is part of a domain name registration at a registry for the domain name, wherein a second DNS service provider accesses the registry to indicate the authorization for the first DNS service provider to manage the DNS record associated with the domain name;
receiving, by the first DNS service provider and from a registrant, a request to update the DNS record associated with the domain name;
verifying, by the first DNS service provider, that the registrant is authorized to request the update associated with the domain name;
determining, by the first DNS service provider, that the first DNS service provider is authorized to perform the update associated with the domain name; and
updating, by the first DNS service provider, the DNS record associated with the domain name according to the request to update received from the registrant without receiving a request from a registrar to update the DNS record associated with the domain name.

### Claim 2 (depends on 1)

The method of claim 1, wherein the first DNS service provider accesses the registry to update the DNS record associated with the domain name.

### Claim 3 (depends on 1)

The method of claim 1, wherein verifying that the registrant is authorized to request the update associated with the domain comprises: verifying an identification information accompanying the request from the registrant.

### Claim 4 (depends on 3)

The method of claim 3, further comprising:
upon verifying the identification information, sending, by the first DNS service provider, a related action request and an authorization to the second DNS service provider.

### Claim 5 (depends on 4)

The method of claim 4, further comprising:
receiving, by the first DNS service provider, a response from the second DNS service provider regarding whether the authorization was accepted and the related action request was performed.

### Claim 6 (depends on 3)

The method of claim 3, wherein the identification information comprises an authorization token, an assertion from an identity provider, or a digital signature of the registrant.

### Claim 7

A system for managing a domain name system (DNS) record by a first DNS service provider, the system comprising:
a processor;
memory storing instructions that when executed by the processor, cause the processor to perform operations comprising:
receiving, by the first DNS service provider, an authorization to manage a DNS record associated with a domain name, wherein an indication of the authorization is part of a domain name registration at a registry for the domain name, wherein a second DNS service provider accesses the registry to indicate the authorization for the first DNS service provider to manage the DNS record associated with the domain name;
receiving, by the first DNS service provider and from a registrant, a request to update the DNS record associated with the domain name;
verifying, by the first DNS service provider, that the registrant is authorized to request the update associated with the domain name;
determining, by the first DNS service provider, that the first DNS service provider is authorized to perform the update associated with the domain name; and
updating, by the first DNS service provider, the DNS record associated with the domain name according to the request to update received from the registrant without receiving a request from a registrar to update the DNS record associated with the domain name.

### Claim 8 (depends on 7)

The system of claim 7, wherein the first DNS service provider accesses the registry to update the DNS record associated with the domain name.

### Claim 9 (depends on 7)

The system of claim 7, wherein verifying that the registrant is authorized to request the update associated with the domain comprises: verifying an identification information accompanying the request from the registrant.

### Claim 10 (depends on 9)

The system of claim 9, wherein the operations further comprise:
upon verifying the identification information, sending, by the first DNS service provider, a related action request and an authorization to the second DNS service provider.

### Claim 11 (depends on 10)

The system of claim 10, wherein the operations further comprise:
receiving, by the first DNS service provider, a response from the second DNS service provider regarding whether the authorization was accepted and the related action request was performed.

### Claim 12 (depends on 9)

The method of claim 9, wherein the identification information comprises an authorization token, an assertion from an identity provider, or a digital signature of the registrant.

### Claim 13

A non-transitory computer readable media storing instructions for managing a domain name system (DNS) record by a first DNS service provider, wherein, when executed by a processor, the instructions cause the processor to perform operations comprising:
receiving, by the first DNS service provider, an authorization to manage a DNS record associated with a domain name, wherein an indication of the authorization is part of a domain name registration at a registry for the domain name, wherein a second DNS service provider accesses the registry to indicate the authorization for the first DNS service provider to manage the DNS record associated with the domain name;
receiving, by the first DNS service provider and from a registrant, a request to update the DNS record associated with the domain name;
verifying, by the first DNS service provider, that the registrant is authorized to request the update associated with the domain name;
determining, by the first DNS service provider, that the first DNS service provider is authorized to perform the update associated with the domain name; and
updating, by the first DNS service provider, the DNS record associated with the domain name according to the request to update received from the registrant without receiving a request from a registrar to update the DNS record associated with the domain name.

### Claim 14 (depends on 13)

The non-transitory computer readable media of claim 13, wherein the first DNS service provider accesses the registry to update the DNS record associated with the domain name.

### Claim 15 (depends on 13)

The non-transitory computer readable media of claim 13, wherein verifying that the registrant is authorized to request the update associated with the domain comprises: verifying an identification information accompanying the request from the registrant.

### Claim 16 (depends on 15)

The non-transitory computer readable media of claim 15, wherein the operations further comprise:
upon verifying the identification information, sending, by the first DNS service provider, a related action request and an authorization to the second DNS service provide.

### Claim 17 (depends on 16)

The non-transitory computer readable media of claim 16, wherein the operations further comprise:
receiving, by the first DNS service provider, a response from the second DNS service provider regarding whether the authorization was accepted and the related action request was performed.

### Claim 18 (depends on 15)

The non-transitory computer readable media of claim 15, wherein the identification information comprises an authorization token, an assertion from an identity provider, or a digital signature of the registrant.
