Which three steps will help determine the cause of DNS name resolution failure?

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 resolution failure?

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 resolution failure?

A.
Verify the contents of /etc/resolve.conf.

B.
Run netstat-nr to verify the routing to the DNS server.

C.
Ping the IP address of the IPS server to verify connectivity.

D.
On the installation server, verify that the menu.1st file for the client points to a valid boot arc
hive.

E.
Run df-k to verify that the boot directory containing the boot archive is loopback mounted under
/etc/netboot.

F.
Run the command /sbin/dhcpinfo DNSserv to ensure that the DHCP server providing the DNS
server information.

Explanation:
Check DNS
* (A) Check whether DNS is configured on your client by verifying that a non-empty
/etc/resolv.conf file exists.
* (F) If /etc/resolv.conf does not exist or is empty, check that your DHCP server is providing DNS
server information to the client:
# /sbin/dhcpinfo DNSserv
If this command returns nothing, the DHCP server is not set up to provide DNS server information
to the client. Contact your DHCP administrator to correct this problem.
* (B) If an /etc/resolv.conf file exists and is properly configured, check for the following possible
problems and contact your system administrator for resolution:
**The DNS server might not be resolving your IPS repository server name.
**No default route to reach the DNS server exists.
Reference: Installing Oracle Solaris 11 Systems, Client Installation Fails



Leave a Reply 7

Your email address will not be published. Required fields are marked *


AG

AG

Check DNS

Check whether DNS is configured on your client by verifying that a non-empty /etc/resolv.conf file exists.

If /etc/resolv.conf does not exist or is empty, check that your DHCP server is providing DNS server information to the client:

# /sbin/dhcpinfo DNSserv

If this command returns nothing, the DHCP server is not set up to provide DNS server information to the client. Contact your DHCP administrator to correct this problem.

If an /etc/resolv.conf file exists and is properly configured, check for the following possible problems and contact your system administrator for resolution:

The DNS server might not be resolving your IPS repository server name.

No default route to reach the DNS server exists (netstat -rn)

Marangani

Marangani

Correct are A, C, F.

Hosam Al Ali

Hosam Al Ali

Sorry- A, B, F