Data Domain - Changing Data Domain Hostname

Summary: This article provides step-by-step instructions for changing the Fully Qualified Domain Name (FQDN) of a Data Domain system. This process is typically required when an organization undergoes a domain name change due to a merger, acquisition, or rebranding initiative. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Instructions

When changing the Fully Qualified Domain Name (FQDN) of a Data Domain system, consider the following best practices: 

  • Do not include underscores in the hostname, as they are incompatible with certain browsers.
  • Reconfigure Common Internet File System (CIFS) authentication and replication after changing the hostname or domain name.

Reconfigure CIFS authentication

  1. Document current Domain Name System (DNS), Domain Controllers, and Active Directory Realm:
# net show DNS

# cifs show config

 

  1. Change the domain name and hostname:
# net set domainname <new-domain.com>

# net set hostname <new-hostname.new-domain.com>

 

  1. Ensure that DNS records are updated for both forward and reverse lookups.
  2. If the system is joined to the domain, update the Data Domain record in the Domain Controller.
  3. Update Media Server/Storage Node Configuration to reflect the new hostname.

 

Regenerate Certificates and Trust

After updating the hostname, it is essential to ensure that all certificates reflect the new hostname. If you are using internally generated self-signed certificates, you can seamlessly regenerate both the Host and CA certificates using non-disruptive commands:

# adminaccess certificate show

# adminaccess certificate generate self-signed-cert

# adminaccess certificate generate self-signed-cert regenerate-ca

 

Important: Regenerating the host certificate does not impact mutual trust. However, regenerating the CA certificate breaks existing trust relationships and requires re-establishment.

 

To re-establish mutual trust, follow these steps:

  1. Document the current trust configuration:
# adminaccess trust show

 

  1. Delete the old trust relationship:
# adminaccess trust del host <hostname of other DD/DDMC> type mutual

 

  1. Establish a new mutual trust:
# adminaccess trust add host <hostname of other DD/DDMC> type mutual

 

  1. Restart http services:
# adminaccess disable http
# adminaccess disable https
# adminaccess enable https
# adminaccess enable http

 

Reconfigure Replication Contexts

If replication is configured, update the hostname in each replication context:

# replication show config

# replication modify <destination> {source-host | destination-host} <new-host-name>

 

Example:

# replication modify mtree://test2.tech.local source-host NewHostname.tech.local

# replication modify mtree://test1.tech.local/backup/drCOMMVAULT destination-host test2.tech.local

 

If the issue continues after following the steps outlined in this article, contact your designated support provider to initiate a service request.

 

Affected Products

Data Domain

Products

Data Domain
Article Properties
Article Number: 000056665
Article Type: How To
Last Modified: 23 Oct 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.