Oracle Exalytics: DNS Lookup With Automount Fails After Creating A Storage Partition

Asset ID:	1-72-1607366.1
Update Date:	2013-12-17
Keywords:

Solution Type Problem Resolution Sure

Solution 1607366.1 : Oracle Exalytics: DNS Lookup With Automount Fails After Creating A Storage Partition

Applies to:

Exalytics In-Memory Machine X2-4 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

Created storage partition on Exalytics server. After rebooting the server, the DNS lookup with automount fails and the server name does not resolve. Mount command from NFS client to NFS server does not work when host name is used.
Then command does work when IP address is used.

Changes

Created new storage partition.

Cause

The resolv.conf file was set incorrectly. "Search" variable included an invalid host name - i.e. "test" and did not include the domain name. The "search" entry needs to include the fully qualified host name including the domain name extension.

Solution

You may resolve this issue by modifying the resolv.conf file to use actual host name and domain.

For example, change the resolv.conf file from:

search test
nameserver 10.128.0.1
nameserver 10.228.1.0

Change resolv.conf file to:

search yourhost.domain <where entry is the actual server/host name followed by the actual domain name>
nameserver 10.128.0.1
nameserver 10.228.1.0

For additional information on resolv.conf, you may wish to consult the Linux man pages.

The following 3rd party blog reference also includes additional hints: http://linuxappsdba.blogspot.com/2009/08/resolvconf-alsowhy.html
Please note that Oracle does not support, or endorse 3rd party blogs, but merely provides this information as an additional resource.

Attachments

This solution has no attachment