Sponsored Content
Operating Systems AIX AIX NFS Server and NFS Client Post 302960158 by MichaelFelt on Wednesday 11th of November 2015 01:22:38 PM
Old 11-11-2015
The two common ways for modfying search order is to use either the environment NSORDER or an entry in /etc/netsvc.conf.

e.g., I usually set
hosts=local4,bind4

in /etc/netsvc.conf

the 4 specifies to only check for IP4 addresses resolution, a 6 would search only IP6, and no number searches IP4 then IP6 space.

If nothing is set, the default is equivalent to
hosts=bind,nis,local (or maybe it is nis,bind,local I have not even tried to use nis in 15 to 20 years - so I forget ;-| )

Having bind first - when a default is defined, but network is not working - can slow a reboot a long time. Setting the timeout and retry in either /etc/environment via environment variables, or in /etc/resolv.conf - can shorten this drastically.

While I have never used it myself - I expect that any bind/dns setting you can use on a POSIX system, such as Solaris - should work in the same way on AIX.
 

9 More Discussions You Might Find Interesting

1. Linux

NFS Server FC7 Solaris client problems!

Hi, my problem is that I am not able to grand the nfs directory on a Fedora 7 server to a standard solaris client. I always got the messages no permission. Important: No change on the client (Solaris) is possible! So I am not able to change the NFS Version on the client side to force the... (3 Replies)
Discussion started by: joerg
3 Replies

2. UNIX for Advanced & Expert Users

Determining IP address of NFS server on client

Hi. We use an Isilon cluster system to provide our NAS. The Isilon uses a round-robin DNS setup to spread mount requests across the many nodes of the cluster. When a node needs work, the filesystems that are mounted to it need to be moved to other nodes prior to shutting the node down. I... (2 Replies)
Discussion started by: rascalrick
2 Replies

3. Solaris

Solaris 9 as a nfs client -- centos as a nfs server.

Hello, I have a centos as nfs server, its name is centos_A. After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/* But, My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies

4. AIX

can not mount from aix client to linux nfs server

Hi, I am trying to mount a nfs folder from AIX client to Linux NFS Server, but I got the following error: # mount 128.127.11.121:/aix /to_be_del mount: 1831-010 server 128.127.11.121 not responding: RPC: 1832-018 Port mapper failure - RPC: 1832-008 Timed out mount: retrying... (1 Reply)
Discussion started by: victorcheung
1 Replies

5. Red Hat

Memory problems in NFS client server

Hi all, i have some doubts in a situation that i fail to get an answer in Google. I have a solaris 10 nfs server and 5 centos 6.0 nfs clients. The problem/situation is that in the clients the free memory is "disappearing" along the time (passing to used)..and it gets free if i umount the... (5 Replies)
Discussion started by: blast
5 Replies

6. Solaris

Can't access NFS Share on Solaris Server from a Linux Client

Hi, I am trying to access a NFS shared directory on Solaris 10 Server from a client which is RHEL 4 Server. On the NFS Server, in /etc/dfs/, I added following line to dfstab file. & then ran the following On the client machine, while running the mount command, I am... (0 Replies)
Discussion started by: SunilB2011
0 Replies

7. AIX

AIX NFS Client Logging

My AIX NFS client failed to mount a Windows server NFS service today. Is NFS client logging enabled by default on AIX? If not, is there a way to enable NFS client logging on AIX6.1. Thanks. (0 Replies)
Discussion started by: famasutika
0 Replies

8. Shell Programming and Scripting

Mount NFS Share On NFS Client via bash script.

I need a help of good people with effective bash script to mount nfs shared, By the way I did the searches, since i haven't found that someone wrote a script like this in the past, I'm sure it will serve more people. The scenario as follow: An NFS Client with Daily CRON , running bash script... (4 Replies)
Discussion started by: Brian.t
4 Replies

9. Solaris

Solaris 10 NFS client cannot mount a share from a Windows server

I have a Solaris 10 server, I'm trying to mount a share from a Windows nfs server. If I add this entry (tst-walnut:/test_sap_nfs - /majid nfs - yes rw,soft) to my /etc/vfstab, then I can mount, but when I create a file by root:root, the file owner changes to... (1 Reply)
Discussion started by: Hiroshi
1 Replies
HOST.CONF(5)                                                Linux System Administration                                               HOST.CONF(5)

NAME
host.conf - resolver configuration file DESCRIPTION
The file /etc/host.conf contains configuration information specific to the resolver library. It should contain one configuration keyword per line, followed by appropriate configuration information. The following keywords are recognized: trim This keyword may be listed more than once. Each time it should be followed by a list of domains, separated by colons (':'), semi- colons (';') or commas (','), with the leading dot. When set, the resolver library will automatically trim the given domain name from the end of any hostname resolved via DNS. This is intended for use with local hosts and domains. (Related note: trim will not affect hostnames gathered via NIS or the hosts(5) file. Care should be taken to ensure that the first hostname for each entry in the hosts file is fully qualified or unqualified, as appropriate for the local installation.) multi Valid values are on and off. If set to on, the resolver library will return all valid addresses for a host that appears in the /etc/hosts file, instead of only the first. This is off by default, as it may cause a substantial performance loss at sites with large hosts files. reorder Valid values are on and off. If set to on, the resolver library will attempt to reorder host addresses so that local addresses (i.e., on the same subnet) are listed first when a gethostbyname(3) is performed. Reordering is done for all lookup methods. The default value is off. ENVIRONMENT
The following environment variables can be used to allow users to override the behavior which is configured in /etc/host.conf: RESOLV_HOST_CONF If set, this variable points to a file that should be read instead of /etc/host.conf. RESOLV_MULTI Overrides the multi command. RESOLV_REORDER Overrides the reorder command. RESOLV_ADD_TRIM_DOMAINS A list of domains, separated by colons (':'), semicolons (';') or commas (','), with the leading dot, which will be added to the list of domains that should be trimmed. RESOLV_OVERRIDE_TRIM_DOMAINS A list of domains, separated by colons (':'), semicolons (';') or commas (','), with the leading dot, which will replace the list of domains that should be trimmed. Overrides the trim command. FILES
/etc/host.conf Resolver configuration file /etc/resolv.conf Resolver configuration file /etc/hosts Local hosts database NOTES
The following differences exist compared to the original implementation. A new command spoof and a new environment variable RESOLV_SPOOF_CHECK can take arguments like off, nowarn, and warn. Line comments can appear anywhere and not only at the beginning of a line. Historical The nsswitch.conf(5) file is the modern way of controlling the order of host lookups. In glibc 2.4 and earlier, the following keyword is recognized: order This keyword specifies how host lookups are to be performed. It should be followed by one or more lookup methods, separated by com- mas. Valid methods are bind, hosts, and nis. RESOLV_SERV_ORDER Overrides the order command. Since glibc 2.0.7, the following keywords and environment variable have been recognized but never implemented: nospoof Valid values are on and off. If set to on, the resolver library will attempt to prevent hostname spoofing to enhance the security of rlogin and rsh. It works as follows: after performing a host address lookup, the resolver library will perform a hostname lookup for that address. If the two hostnames do not match, the query fails. The default value is off. spoofalert Valid values are on and off. If this option is set to on and the nospoof option is also set, the resolver library will log a warn- ing of the error via the syslog facility. The default value is off. spoof Valid values are off, nowarn, and warn. If this option is set to off, spoofed addresses are permitted and no warnings will be emit- ted via the syslog facility. If this option is set to warn, the resolver library will attempt to prevent hostname spoofing to enhance the security and log a warning of the error via the syslog facility. If this option is set to nowarn, the resolver library will attempt to prevent hostname spoofing to enhance the security but not emit warnings via the syslog facility. Setting this option to anything else is equal to setting it to nowarn. RESOLV_SPOOF_CHECK Overrides the nospoof, spoofalert, and spoof commands in the same way as the spoof command is parsed. Valid values are off, nowarn, and warn. SEE ALSO
gethostbyname(3), hosts(5), nsswitch.conf(5), resolv.conf(5), hostname(7), named(8) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2017-09-15 HOST.CONF(5)
All times are GMT -4. The time now is 07:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy