Avamar: How to modify the Domain Name System (DNS) on an Avamar grid

Summary: This article provides the steps required to modify the Domain Name System (DNS) server IP address or search criteria on Avamar grids.

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.

Instructions

Prerequisites:

1. Log in to the Avamar Utility Node or Single Node as admin.

2. Ensure that no grid maintenance is running using the following command:

status.dpn 
 

Example outputs:

Maintenance is not running:

Last checkpoint: cp.20260319130756 finished Thu Mar 19 09:08:16 2026 after 00m 20s (OK)
Last GC: finished Thu Mar 19 08:00:55 2026 after 00m 06s >> recovered 0.00 KB (OK)
Last hfscheck: finished Thu Mar 19 09:07:52 2026 after 06m 36s >> checked 1717 of 1717 stripes (OK)
 

Checkpoint (CP) is running:

Checkpoint in progress: cp.20260320002416 started Thu Mar 19 20:24:16 2026 >> completed 78 of 5268 stripes (so far)
 

Checkpoint validation (aka hfscheck) is running:

Hfscheck in progress: started Thu Mar 19 20:25:42 2026 >> checked 321 of 5265 stripes (hfscheck)
 

Garbage collection (GC) is running:

GC in progress: started Thu Mar 19 17:30:16 2026 >> recovered 0.00 KB (so far) 
 

3. Take a checkpoint:

mccli checkpoint create --override_maintenance_scheduler
 

Sample output:

0,22624,Starting to create a server checkpoint
 
4. Monitor the checkpoint to completion using one of the following commands: 
  • status.dpn
  • avmaint cpstatus
 

5. Verify that checkpoint has been successfully created using the cplist command:

Example and Sample output:

cplist 
cp.20260319130055 Thu Mar 19 09:00:55 2026   valid rol ---  nodes   3/3 stripes   5268
cp.20260319130756 Thu Mar 19 09:07:56 2026   valid --- ---  nodes   3/3 stripes   5268
cp.20260320002416 Thu Mar 19 20:24:16 2026   valid --- ---  nodes   3/3 stripes   5268
 

Update DNS settings in /etc/resolv.conf:

6. Elevate to root privilege.

7. Make a backup copy of the existing resolv.conf file on the Avamar Utility Node or Single Node, and verify that it has been successfully created:

cp -pv /etc/resolv.conf /etc/x-resolv.conf.`date +%Y%m%d`
 

Sample output:

'/etc/resolv.conf' -> '/etc/x-resolv.conf.20260319'
 

8. Edit the resolv.conf file and apply the required changes.

Sample file content:

domain company.com
search company.com
nameserver 10.1.2.3
nameserver 10.1.2.4
 

9. For a multinode grid, or a single node grid with an accelerator, distribute the new resolv.conf file to the other nodes:

a. Load the root ssh keys per Avamar: How to Log in to an Avamar Server and Load Various Keys

b. Distribute the file to all nodes:

mapall --user=root --all+ copy /etc/resolv.conf
 

Sample output:

Using /usr/local/avamar/var/probe.xml
/bin/tar czhf /tmp/.mapall40488 /etc/resolv.conf
/bin/tar: Removing leading `/' from member names
(0.s) scp -q  -o GSSAPIAuthentication=no /tmp/.mapall40488 root@192.168.255.1:.
(0.s) ssh  -x  -o GSSAPIAuthentication=no root@192.168.255.1 'tar xzf .mapall40488; rm -f .mapall40488'
(0.0) scp -q  -o GSSAPIAuthentication=no /tmp/.mapall40488 root@192.168.255.2:.
(0.0) ssh  -x  -o GSSAPIAuthentication=no root@192.168.255.2 'tar xzf .mapall40488; rm -f .mapall40488'
(0.1) scp -q  -o GSSAPIAuthentication=no /tmp/.mapall40488 root@192.168.255.3:.
(0.1) ssh  -x  -o GSSAPIAuthentication=no root@192.168.255.3 'tar xzf .mapall40488; rm -f .mapall40488'
(0.2) scp -q  -o GSSAPIAuthentication=no /tmp/.mapall40488 root@192.168.255.4:.
(0.2) ssh  -x  -o GSSAPIAuthentication=no root@192.168.255.4 'tar xzf .mapall40488; rm -f .mapall40488'
(0.3) scp -q  -o GSSAPIAuthentication=no /tmp/.mapall40488 root@192.168.255.5:.
(0.3) ssh  -x  -o GSSAPIAuthentication=no root@192.168.255.5 'tar xzf .mapall40488; rm -f .mapall40488'
 

c. Backup the existing resolv.conf file on all nodes:

mapall --user=root --all+ cp -pv /etc/resolv.conf /etc/x-resolv.conf.`date +%Y%m%d`
 
Sample output:
Using /usr/local/avamar/var/probe.xml
(0.s) ssh -q  -x  -o GSSAPIAuthentication=no root@192.168.255.1 'cp -pv /etc/resolv.conf /etc/x-resolv.conf.20260319'
'/etc/resolv.conf' -> '/etc/x-resolv.conf.20260319'
(0.0) ssh -q  -x  -o GSSAPIAuthentication=no root@192.168.255.2 'cp -pv /etc/resolv.conf /etc/x-resolv.conf.20260319'
'/etc/resolv.conf' -> '/etc/x-resolv.conf.20260319'
(0.1) ssh -q  -x  -o GSSAPIAuthentication=no root@192.168.255.3 'cp -pv /etc/resolv.conf /etc/x-resolv.conf.20260319'
'/etc/resolv.conf' -> '/etc/x-resolv.conf.20260319'
(0.2) ssh -q  -x  -o GSSAPIAuthentication=no root@192.168.255.4 'cp -pv /etc/resolv.conf /etc/x-resolv.conf.20260319'
'/etc/resolv.conf' -> '/etc/x-resolv.conf.20260319'
(0.3) ssh -q  -x  -o GSSAPIAuthentication=no root@192.168.255.5 'cp -pv /etc/resolv.conf /etc/x-resolv.conf.20260319'
'/etc/resolv.conf' -> '/etc/x-resolv.conf.20260319'
 

d. Replace the updated resolv.conf file in the /etc directory on all nodes:

mapall --user=root --all+ 'cp /root/etc/resolv.conf /etc/resolv.conf'
 

Sample output:

Using /usr/local/avamar/var/probe.xml
(0.s) ssh  -x  -o GSSAPIAuthentication=no root@192.168.255.1 'cp /root/etc/resolv.conf /etc/resolv.conf'
(0.0) ssh  -x  -o GSSAPIAuthentication=no root@192.168.255.2 'cp /root/etc/resolv.conf /etc/resolv.conf'
(0.1) ssh  -x  -o GSSAPIAuthentication=no root@192.168.255.3 'cp /root/etc/resolv.conf /etc/resolv.conf'
(0.2) ssh  -x  -o GSSAPIAuthentication=no root@192.168.255.4 'cp /root/etc/resolv.conf /etc/resolv.conf'
(0.3) ssh  -x  -o GSSAPIAuthentication=no root@192.168.255.5 'cp /root/etc/resolv.conf /etc/resolv.conf'

Additional Information

Caution: This article should only be used to update the DNS server IP address or search domains.

If the Avamar IP address or Fully Qualified Domain Name (FQDN) must be updated, contact the Dell Technologies Professional Services team for assistance.

Affected Products

Avamar, Avamar Server
Article Properties
Article Number: 000014348
Article Type: How To
Last Modified: 20 Mar 2026
Version:  7
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.