Changing a Redis Software Cluster Name and Licensing Considerations

Redis Software uses the cluster name, also known as the cluster fully qualified domain name (FQDN), as the cluster’s permanent identity. This identity is used for licensing, DNS, endpoint generation, and core cluster operations. After a Redis Software cluster is created, its cluster name cannot be changed.

This is important when planning new deployments, requesting licenses, or setting up production, disaster recovery, standby, or passive clusters. The license must match the cluster name or FQDN used by the cluster. Updating DNS records or changing external references does not change the cluster identity used by Redis Software.

This article explains how Redis Software uses the cluster name, why it cannot be renamed after creation, and what options are available if a cluster was created with the wrong name or requires a different identity.

Quick Fix

Prerequisites

Before troubleshooting a cluster naming or licensing issue, collect the following:

• Product type:

  • Redis Software

  • Redis Enterprise for Kubernetes

• Current cluster name or FQDN

• Current license status

• Intended cluster name or FQDN

• Whether production data exists on the cluster

• Any license validation error messages

Can a Redis Software Cluster Name Be Changed?

No.

A Redis Software cluster name is defined during cluster creation and cannot be modified later. The cluster name is part of the cluster's identity and is used by Redis Software for:

• License validation

• DNS integration

• Database endpoint generation

• Node communication

• Cluster management operations

Changing DNS records, load balancer names, or client connection strings does not change the cluster name stored within Redis Software.

If the cluster was created with an incorrect name and that name must be changed, the supported approach is to deploy a new cluster using the correct name and migrate workloads to the new cluster.

How Cluster Names Affect Licensing

Redis Software licenses are issued for a specific cluster identity.

When a license is uploaded, Redis validates:

• Cluster name or FQDN

• Activation date

• Expiration date

• Licensed capacity

• Licensed features

If the cluster name in the license does not match the actual cluster name, the license will not activate.

To verify the current cluster identity:

1. Sign in to Cluster Manager.

2. Navigate to Cluster > Configuration > General > License.

3. Review the cluster name and license details.

You can also verify the license information through the REST API:

GET /v1/license

If the cluster name is correct but the license was issued for the wrong name, request a corrected license. Rebuilding the cluster is not required in this scenario.

When Is a Rebuild Required?

A rebuild is only required when the cluster itself was created with the wrong name and must permanently use a different name.

Examples include:

• The production cluster was deployed with an incorrect FQDN.

• Corporate naming standards changed after deployment.

• The cluster was created using a temporary name that is no longer acceptable.

In these situations:

1. Deploy a new cluster using the desired name.

2. Obtain a license issued for the new cluster name.

3. Migrate or recover databases using supported methods.

4. Redirect clients to the new endpoints.

Disaster Recovery and Standby Clusters

Redis Software licenses cannot be freely moved between clusters.

Each Redis Software cluster requires its own license, including:

• Production clusters

• Disaster recovery clusters

• Passive clusters

• Cold standby clusters

If you are deploying a DR or standby environment, request a separate license for that cluster rather than attempting to reuse the production license.

Redis Enterprise for Kubernetes Considerations

Redis Enterprise for Kubernetes uses the Redis Enterprise Cluster (REC) resource as the cluster identity source.

For licensing purposes, the REC identity is typically based on the REC name and namespace rather than a customer-facing ingress hostname or load balancer name.

If the REC identity changes, a new license may be required.

To verify the REC configuration:

kubectl get rec -A
kubectl describe rec <REC_NAME> -n <namespace>

If the license was issued for a different REC identity, request a corrected license.

Troubleshooting

License Is Rejected After Upload

Check:

• Cluster name matches the license

• Activation date has started

• Expiration date has not passed

• Licensed capacity is sufficient

• License content was copied completely

If the cluster name and license do not match, request a corrected license.

DNS Was Changed but Licensing Still Fails

Changing DNS records does not rename a Redis Software cluster.

Verify the actual cluster name in Cluster Manager or through:

GET /v1/license

The license must match the cluster identity configured in Redis Software.

Existing Databases Work but Administrative Changes Fail

This commonly indicates an expired license.

Existing databases continue serving traffic after license expiration, but database-level administrative operations are restricted until a valid license is installed.

Examples include:

• Creating databases

• Modifying database configuration

• Changing database security settings

Verify the current license status before troubleshooting other components.

When to Contact Redis

Contact Redis Support or your Redis account team if:

• The license was issued for the wrong cluster name or FQDN.

• The cluster was created with the wrong name and contains production data.

• A license continues to fail after validating the cluster identity.

• You need a separate license for a DR or standby cluster.

• The cause of the licensing issue is unclear.

Provide:

• Product type

• Current cluster name or FQDN

• Intended cluster name or FQDN

• Current license status

• Exact error message

• Relevant screenshots or command output

Related Articles

• Understanding Redis Software Trial Licenses and Temporary Licenses

• Does Uploading a New Redis License Require Downtime or a Restart?

• Troubleshooting Redis License Activation and Update Failures