Operational Defect Database
BugZero found this defect 98 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Hewlett Packard Enterprise | a00137748en_us
Advisory: HP-UX 11.31 - HPE System Management Homepage (SMH) Clears BIND Zone Configuration Due To Invalid Network Number(s)
Last update date:
2/12/2024
Affected products:
HPE System Management Homepage Software
Affected releases:
HPE System Management Homepage Software
Fixed releases:
No fixed releases provided.
Description:
Info
The HPE System Management Homepage (SMH) does not report an error when a user requests to create a zone with invalid network numbers. During execution of the user request, the SMH call to hosts_to_named(1M) returns an error, but SMH does not handle the error properly. Consequently, any existing BIND zone configuration is cleared. When a 4 octet value is set (for example, 192.168.1.0) in "Network Number(s)" in SMH, no error is reported even though this value is invalid. This can be observed when performing the following: Launch smh(1). Go through the following menus n - Networking and Communications s - Network Services Configuration d - DNS (BIND) l - DNS Local Name Server On the DNS setting menu, choose "Add Master/Slave Information…" from the Action list. In the sub window, put any domain name and an incorrect "Network Number(s)" and leave other parameters as is. ----------------------------------------------------------------------- Name Server Type: [ Master ->] Domain: test.com Network Number(s): 192.168.1.0 <-- Set wrong value (4 octet) … ------------------------------------------------------------------------ Choose "Yes" at the confirmation pop-up. After that, no zone information is displayed on the DNS setting menu. Also, no errors are reported.
Scope
Any HPE Integrity system with HP-UX 11.31 1805 (or later) and running the following: SMH A.3.2.12.02 (or later) HPUX-NameServer C.9.11.1.2.0 (or later)
Resolution
To recover, perform the following to restore the existing BIND zone configuration and to add any new zone(s) with valid network numbers. Move all temporary files to a temporary directory. The files can be used as reference to re-create the entries. # mv /var/sam/dns/primary.<domain name> /tmp NOTE : The invalid entry corrupts existing entries in /etc/named.conf and those will have to be re-created based on primary.<domain name> file. NOTE 1 : SMH will also remove all valid files in /etc/named.data/ when UI is exited. Re-create existing BIND zone(s) through SMH again. Or, recover configuration files under /etc/named.data from backup. e.g. /etc/named.data/db.<new_domain> /etc/named.data/db.127.0.0 /etc/named.data/db.<IP> /etc/named.data/boot.sec.save /etc/named.data/conf.sec.save /etc/named.data/boot.sec /etc/named.data/named.conf /etc/named.conf Create any new BIND zone needed with valid values, i.e. no more than 3 octets (xxx.xxx.xxx) Verify BIND zone configuration in the SMH user interface. # unset DISPLAY # smh -> n - Networking and Communications -> s - Network Services Configuration -> d - DNS (BIND) -> l - DNS Local Name Server After successful creation of the BIND zone(s), the temporary files moved away can be removed. If there is still some issue with the zone creation, contact your HPE support representative and keep the temporary files for reference. Contact your local country HPE Customer Support or log a case via the HPE Support Center RECEIVE PROACTIVE UPDATES : Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively in your e-mail through HPE Support Alerts. Sign up for Support Alerts at the following URL: HPE Email Preference Center NAVIGATION TIP: For hints on navigating HPE.com to locate the latest drivers, patches and other support software downloads, refer to the Navigation Tips document. SEARCH TIP: For hints on locating similar documents on HPE.com, refer to the Search Tips document.
