# US 2012/0254386 A1 · Transfer of DNSSEC Domains

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

- Number: US 2012/0254386 A1
- Document ID: US20120254386A1
- Status: Published application
- Kind: A1
- Application number: 13/078,643
- Filed: 2011-04-01
- Published: 2012-10-04
- Earliest claimed: 2011-04-01
- Assignees: VeriSign, Inc.
- Inventors: David Smith; James Gould; David Blacka
- Web page: https://patentgrep.com/patent/US20120254386A1

## CPC

- H04L 61/30: Managing network names, e.g. use of aliases or nicknames (name-to-address mapping H04L61/45)
- 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: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods of transferring a DNSSEC enabled domain from a losing hosting provider to a gaining hosting provider are described in which the transfer of the domain may be achieved without disruption to a DNSSEC validation of the domain. Systems and methods, such as those directed to registry and/or registrar servers, may include transferring a DNSKEY or Delegation Signer (DS) record from a gaining hosting provider to a losing hosting provider prior to transferring the domain from the losing hosting provider to the gaining hosting provider. A gaining hosting provider may sign DNS records of the domain with the gaining hosting provider DNSKEY prior to transferring the domain from the losing hosting provider to the gaining hosting provider. Additionally, a registry server, or similar device, may be configured to act as an intermediary between the losing hosting provider and the gaining hosting provider during the transfer process.

## Claims

### Claim 1

A method of transferring a DNSSEC enabled domain from a losing hosting provider to a gaining hosting provider comprising:
receiving a request to transfer the domain from the losing hosting provider to the gaining hosting provider; and
at least one of transferring a DNSKEY or Delegation Signer (DS) record from the gaining hosting provider to the losing hosting provider prior to transferring the domain from the losing hosting provider to the gaining hosting provider, and signing DNS records of the domain with the gaining hosting provider DNSKEY prior to transferring the domain from the losing hosting provider to the gaining hosting provider.

### Claim 2 (depends on 1)

The method of claim 1, wherein the method includes both of transferring a DNSKEY or Delegation Signer (DS) record from the gaining hosting provider to the losing hosting provider prior to transferring the domain from the losing hosting provider to the gaining hosting provider, and signing DNS records of the domain with the gaining hosting provider DNSKEY prior to transferring the domain from the losing hosting provider to the gaining hosting provider.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
transferring hosting of the domain from the losing hosting provider to the gaining hosting provider, wherein the domain hosting is transferred from the losing hosting provider to the gaining hosting provider without interruption to a DNSSEC validation for the domain.

### Claim 4 (depends on 3)

The method of claim 3, wherein the transfer of the hosting of the domain is executed after expiration of a longest TTL of DNS records of the domain.

### Claim 5 (depends on 1)

The method of claim 1, wherein the transfer request is received at the gaining hosting provider.

### Claim 6 (depends on 1)

The method of claim 1, wherein the transfer request is received at the losing hosting provider.

### Claim 7 (depends on 1)

The method of claim 1, wherein the transfer request is received from the registrant of the domain.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
establishing an undelegated DNSSEC enabled zone for the domain at the gaining hosting provider;
determining a TTL for all DNS records published by the losing hosting provider of the domain; and
delegating to the gaining hosting provider's DNSSEC enabled zone after expiration of a longest TTL of the DNS record TTLs.
discontinuing delegation to the losing hosting provider for the DNSSEC enabled zone.

### Claim 9 (depends on 1)

The method of claim 1, wherein the losing hosting provider is supported by a losing registrar and the gaining hosting provider is supported by a gaining registrar, the method further comprising:
receiving the transfer request at the gaining registrar to transfer the domain from the losing registrar to the gaining registrar;
establishing an unpublished DNSSEC enabled zone for the domain at the gaining registrar;
transmitting from the gaining registrar at least one of DNSKEY and Delegation Signer (DS) records for the zone;
receiving domain authorization information for the domain at the gaining registrar;
receiving an initiation request at the gaining registrar to initiate the transfer of the domain; and
after receiving the initiation request, sending a registry request from the gaining registrar to a registry responsible for the domain, the registry request including the domain authorization information.

### Claim 10 (depends on 9)

The method of claim 9, wherein the initiation request is received from the registrant of the domain.

### Claim 11 (depends on 9)

The method of claim 9, wherein the initiation request is received from the losing registrar.

### Claim 12 (depends on 9)

The method of claim 9, wherein the DNSKEY records for the zone include a key-signing key (KSK).

### Claim 13 (depends on 9)

The method of claim 9, further comprising:
the gaining registrar automatically confirming that at least one of (a) the DNSKEY records have been published, and (b) the Delegation Signer (DS) records have been added to the domain by the registry,
wherein, the sending of the registry request is conditioned on the automatic confirmation.

### Claim 14

A method of transferring a DNSSEC enabled domain comprising:
receiving, at a registry responsible for the domain, at least one of DNSKEY and Delegation Signer (DS) records for the domain from a gaining registrar;
providing, from the registry, the at least one of DNSKEY and Delegation Signer (DS) records to a losing registrar;
receiving, at the registry, confirmation that the losing registrar has changed existing DNSSEC data for the domain based on the at least one of DNSKEY and Delegation Signer (DS) records; and
changing address information for the domain at the registry after the confirmation that the existing DNSSEC data for the domain has been changed.

### Claim 15 (depends on 14)

The method of claim 14, wherein the registry confirms that the losing registrar has changed the existing DNSSEC data for the domain.

### Claim 16 (depends on 14)

The method of claim 14, wherein the registry receives the confirmation that the losing registrar has changed the existing DNSSEC data for the domain from the gaining registrar.

### Claim 17 (depends on 14)

The method of claim 14, further comprising:
determining a longest TTL for all DNS records of the domain prior to initiating transfer request to registry;
after expiration of the longest TTL, sending an initiation request from the registry to the losing registrar to request authorization information for the domain; and
after receiving the authorization information from the losing registrar, communicating the authorization information from the registry to the gaining registrar.

### Claim 18

A hosting provider server system comprising:
a processor; and
a storage medium including instructions for configuring the processor to perform steps including,
receiving a request to transfer a DNSSEC-enabled domain from a losing hosting provider to a gaining hosting provider; and
at least one of transferring a DNSKEY or Delegation Signer (DS) record from the gaining hosting provider to the losing hosting provider prior to transferring the domain from the losing hosting provider to the gaining hosting provider, and signing DNS records of the domain with the gaining hosting provider DNSKEY prior to transferring the domain from the losing hosting provider to the gaining hosting provider.

### Claim 19 (depends on 18)

The system of claim 18, further comprising instructions for:
transferring hosting of the domain from the losing hosting provider to the gaining hosting provider, wherein the domain hosting is transferred from the losing hosting provider to the gaining hosting provider without interruption to a DNSSEC validation for the domain.

### Claim 20 (depends on 19)

The system of claim 19, wherein the transfer of the hosting of the domain is executed after expiration of a longest TTL of DNS records of the domain.

### Claim 21 (depends on 18)

The system of claim 18, further comprising instructions for:
establishing an undelegated DNSSEC enabled zone for the domain at the gaining hosting provider;
determining a TTL for all DNS records of the domain; and
delegating the DNSSEC enabled zone after expiration of a longest TTL, of the DNS record TTLs.

### Claim 22 (depends on 18)

The system of claim 18, wherein the DNSKEY records include a key-signing key (KSK).

### Claim 23 (depends on 18)

The system of claim 18, wherein the losing hosting provider is supported by a losing registrar and the gaining hosting provider is supported by a gaining registrar, further comprising instructions for steps of:
receiving the transfer request at the gaining registrar to transfer the domain from the losing registrar to the gaining registrar;
establishing an unpublished DNSSEC enabled zone for the domain at the gaining registrar;
transmitting from the gaining registrar at least one of DNSKEY and Delegation Signer (DS) records for the zone;
receiving domain authorization information for the domain at the gaining registrar;
receiving an initiation request at the gaining registrar to initiate the transfer of the domain; and
after receiving the initiation request, sending a registry request from the gaining registrar to a registry responsible for the domain, the registry request including the domain authorization information.

### Claim 24 (depends on 23)

The system of claim 23, further comprising instructions for steps of:
the gaining registrar automatically confirming that at least one of (a) the DNSKEY records have been published, and (b) the Delegation Signer (DS) records have been added to the domain by the registry; and
wherein the sending of the registry request is conditioned on the automatic confirmation.

### Claim 27 (depends on 18)

The system of claim 18, further comprising instructions for steps of:
receiving the domain transfer request at the gaining hosting provider;
establishing an undelegated DNSSEC enabled zone for the domain at the gaining hosting provider;
transmitting at least one of DNSKEY and Delegation Signer (DS) records for the undelegated zone from the gaining hosting provider to at least one of a registrant of the domain, a registry of the domain, and the losing hosting provider.

### Claim 28 (depends on 27)

The system of claim 27, wherein the DNSKEY records for the undelegated zone include a key-signing key (KSK).

### Claim 29

A registry server system comprising:
a processor; and
a storage medium including instructions for configuring the processor to perform steps including,
receiving, at a registry responsible for a DNSSC-enabled domain, at least one of DNSKEY and Delegation Signer (DS) records for the domain from a gaining registrar;
providing, from the registry, the at least one of DNSKEY and Delegation Signer (DS) records to a losing registrar;
receiving, at the registry, confirmation that the losing registrar has changed an existing DNSSEC data for the domain based on the at least one of DNSKEY and Delegation Signer (DS) records; and
changing address information for the domain at the registry after the confirmation that the existing DNSSEC data for the domain has been changed.

### Claim 30 (depends on 29)

The system of claim 29, wherein the registry confirms that the losing registrar has changed the existing DNSSEC data for the domain.

### Claim 31 (depends on 29)

The system of claim 29, wherein the registry receives the confirmation that the losing registrar has changed the existing DNSSEC data for the domain from the gaining registrar.

### Claim 32 (depends on 29)

The system of claim 29, further comprising instructions for steps of:
determining a longest TTL for all DNS records of the domain;
after expiration of the longest TTL, sending an initiation request from the registry to the losing registrar to request authorization information for the domain; and
after receiving the authorization information from the losing registrar, communicating the authorization information from the registry to the gaining registrar.
