You are troubleshooting the Oracle Solaris11 Automated Installer (AI), which is not connecting with the IPS software repository. Which three steps will help determine the cause of DNS name…

Question

Options

• AVerify the contents of /etc/resolve.conf.
• BRun netstat -nr to verify the routing to the DNS server.
• CPing the IP address of the IPS server to verify connectivity.
• DOn the installation server, verify that the menu.1st file for the client points to a valid boot arc hive.
• ERun df -k to verify that the boot directory containing the boot archive is loopback mounted under
• FRun the command /sbin/dhcpinfo DNSserv to ensure that the DHCP server providing the DNS

• A
  76% (26)
• C
  15% (5)
• D
  3% (1)
• E
  6% (2)

Explanation

When the AI installer cannot resolve DNS names to reach the IPS repository, you must trace the full DNS configuration chain: A checks /etc/resolv.conf (likely a typo for resolv.conf) to confirm nameserver entries and search domains are correctly defined; B uses netstat -nr to verify the routing table has a valid path to reach the DNS server's network; and F runs /sbin/dhcpinfo DNSserv to confirm the DHCP server is actually supplying a valid DNS server address to the client, which is the most common root cause in automated installs.

Distractors explained:

• C pings the IPS server by IP address, which bypasses DNS entirely - it tests raw connectivity but tells you nothing about name resolution failure
• D checks the GRUB menu.lst file, which is a boot configuration concern, not a DNS or network issue
• E runs df -k to check mounted filesystems, which is also unrelated to DNS resolution

Memory tip: Think of DNS as a 3-layer problem - "Config → Route → Source": you must have the right config file (A), a route to reach the server (B), and a valid source providing the DNS info via DHCP (F). If any layer breaks, resolution fails.

No community discussion yet for this question.