PSQN: iDRAC9 AutoConfig DNS Setting Modified After Applying 6.XX.XX.XX Firmware
Summary: The default values for iDRAC9 DNS settings changed from Disabled to Enabled after applying iDRAC9 6.xx.xx.xx firmware releases from earlier versions.
Symptoms
After updating to iDRAC9 6.xx.xx.xx firmware versions from earlier iDRAC9 3.xx/4.xx/5.xx firmware versions, the iDRAC9 DNS settings will shift from Disabled to Enabled. These settings changes can lead to the iDRAC9 becoming inaccessible by FQDN string. The following DNS settings will shift from Disabled to Enabled after update:
- Auto Config Domain Name
- Use DHCP to Obtain DNS Server Addresses
- Use DHCPv6 to obtain DNS Server Addresses
iDRAC9 UI > iDRAC Settings > Connectivity > Network > Common Settings Example:


iDRAC9 UI > iDRAC Settings > Connectivity > Network > IPv4 Settings Example:


iDRAC9 UI > iDRAC Settings > Connectivity > Network > IPv6 Settings Example:


This behavior is expected when traversing from iDRAC 5.xx.xx.xx firmware to iDRAC 6.xx.xx.xx firmware versions. The default DNS values were modified for Auto Config Domain Name attributes. This was a one-time change to add DNS support for Zero-Touch Deployment by FQDN. The change is captured within several online iDRAC9 6.xx.xx.xx documents.
iDRAC9 6.00.02.00 Release Notes:
iDRAC9 6.00.02.00 Release Notes
- Automation — API and CLI
- Redfish Lifecycle Events (RLCE) in Telemetry
- Added threshold range values to Telemetry Sensor reports
- Added basic memory error information, available through Redfish APIs
- Support for Redfish 2020.3, 2020.4 updates
- Support for additional Redfish 2020.1 and 2020.2 updates
- Added support for CA certificates to the Server Configuration Profiles (SCP)
- Use DHCP to Obtain DNS Server Addresses
- Report
"OS installation complete"status - Added progress bar for Server Configuration Profiles export
- Server HostName included in iDRAC Redfish Events
- Redfish support for property "LastPowerOutputWatts"
- Support for aliasing of Top-Level Redfish URIs
- Support for Zero-Touch Deployment using mDNS
- FQDN support in Zero-Touch Deployment
iDRAC9 6.10.30.00 Release Notes:
iDRAC9 6.10.30.00 Release Notes
iDRAC firmware
- In iDRAC, attaching a folder that is in an NFS share hosted by a Linux-based operating system is not supported.
- In the Lifecycle (LC) interface, It is recommended to avoid performing any operations on media that are mounted as RFS through iDRAC
GUI/RACADM/Redfish. - Updating iDRAC firmware to version 6.xx or later changes the static IPv4 or IPv6 DNS settings. Ensure that you reconfigure the network settings after the upgrade is complete.
iDRAC9 6.xx User Guide:
iDRAC9 User's Guide
Configuring the network settings
To configure the network settings:
Note: For information about the options, see the iDRAC Settings Utility Online Help.
Cause
Resolution
iDRAC9 DNS settings may need to be reverted back to the Disabled setting after updating to iDRAC9 6.xx.xx.xx firmware versions from earlier firmware releases. The iDRAC will still be accessible using remote interfaces through IPv4 or IPv6 addressing. Also, DRACTOOLS RACADM utility can be leveraged through Host Operating System to modify the iDRAC Settings.
#Disable Auto Config Domain Name Example:
racadm>>racadm set idrac.NIC.DNSDomainFromDHCP Disabled [Key=idrac.Embedded.1#NIC.1] Object value modified successfully
#Disable IPv4 Use DHCP To Obtain DNS Server Example:
racadm>>racadm set idrac.ipv4.DNSFromDHCP Disabled [Key=idrac.Embedded.1#IPv4.1] Object value modified successfully
#Disable IPv6 Use DHCP to Obtain DNS Server Example:
racadm>>racadm set idrac.ipv6.dnsfromdhcp6 Disabled [Key=idrac.Embedded.1#IPv6.1] Object value modified successfully