Sponsored Content
Operating Systems Solaris my sun solaris 10 cannot ping and nslookup other server using hostname. Post 302583655 by npandith on Wednesday 21st of December 2011 02:09:01 AM
Old 12-21-2011
Make a DNS entry in /etc/resolv.conf and make sure you have "dns" word in the /etc/nsswitch.conf next to "hosts" entry.

hosts: dns files
 

10 More Discussions You Might Find Interesting

1. HP-UX

UX 11iV2 - No ping by hostname

Hi. I just installed the HP-UX 11i V2. I have problems with CDE - it is inoperative (after logon there is a message box: messaging system failure - or something like that, it asks to check /etc/hosts and network settings). nslookup works by hostname and IP, hostname shown the correct... (7 Replies)
Discussion started by: netwalker
7 Replies

2. Solaris

cannot ping by hostname

Hi All, My current setup is: 1x Windows Server (Windows 2000 server) 1x Unix Server 2x Windows machine 3x Unix Terminals (Hostnames = A, B and C) Problem The problem iam having is Unix terminal C cannot be ping across by Unix terminal A or B or Unix server by using the hostname. Unix... (1 Reply)
Discussion started by: tlee
1 Replies

3. Solaris

Can't ping using hostname on Solaris 10

I recently installed Solaris 10 on my Sun workstation. I cannot ping using hostname from another computer on the same network. But I can ping using the IP address. Also I can ping other systems using their hostnames. Can anyone give some information regarding how to resolve this issue. (4 Replies)
Discussion started by: alpha123
4 Replies

4. AIX

Ping by hostname

Hello everyone I have a partition with a problem with ping. If I do a ping by ip for example ping 1.1.1.1 I got no problem but If I ping by hostname for example ping partition1 take almost a minute to respond me. I have Aix 5.3 and I have another 19 partitions with no problem. The only... (5 Replies)
Discussion started by: lo-lp-kl
5 Replies

5. Solaris

Sun Server auto ping to 0.0.0.0

Hi All, 3 of my SAP sun server are continuosly pinging to the network address 0.0.0.0. I have no idea how this can happen, but they have something in common. All of them are clustered environment (Veritas Cluster). Anyone can help? rgds, (5 Replies)
Discussion started by: ronny_nch
5 Replies

6. Solaris

Ping Sun Solaris 10 on VmWare

Hi, i installed Sun Solaris 10 on VmWare Workstation 6.5 on my Windwos Vista PC. I would to ping solaris virtual machin froma my pc, but i can't do that. Can help me?! I'm sorry for my bad English. akela87 (2 Replies)
Discussion started by: akela87
2 Replies

7. Solaris

Sun Solaris not able to ping Sun Solaris

I have a Sun Blade 2500 with SUN 5.9 OS installed. I can ping other machines(windowsXP/2003) from my SUN machines but not able to ping each other SUN machines which i have newly installed. (7 Replies)
Discussion started by: z_haseeb
7 Replies

8. UNIX for Advanced & Expert Users

ping by hostname not working

anyone ever seen this problem: I can ping the server by IP address but I can't by hostname. nslookup is working and dns query is ok. # nslookup mwxnsb24 Server: 10.11.49.206 Address: 10.11.49.206#53 Name: mwxnsb24 Address: 10.10.58.175 # ping... (8 Replies)
Discussion started by: linuxgeek
8 Replies

9. HP-UX

nslookup/ping resolve problem 11i v3

I am having a problem with a new server build that has got me completely baffled. This server has a private back end network so the way it is supposed to work is that the server thinks its ip address is 10.131.0.48 but the rest of the world knows it as 199.68.100.100 per DNS. It has to be this way... (2 Replies)
Discussion started by: keelba
2 Replies

10. Solaris

Solaris 9 - Unable to ping a particular server, traceroute also displays * * *

Hi All, I am new to solaris environment and we are using Solaris 9 The problem is am unable to ping a particular server from from one of the solaris server The traceroute also shows only * * * for all the 30 hops I tried to check all the settings like 1) /etc/hosts -> contains the... (17 Replies)
Discussion started by: Sanjay255
17 Replies
NSSWITCH.CONF(5)					      BSD File Formats Manual						  NSSWITCH.CONF(5)

NAME
nsswitch.conf -- name-service switch configuration file DESCRIPTION
The nsswitch.conf file specifies how the nsdispatch(3) (name-service switch dispatcher) routines in the C library should operate. The configuration file controls how a process looks up various databases containing information regarding hosts, users (passwords), groups, etc. Each database comes from a source (such as local files, DNS, NIS, and cache), and the order to look up the sources is specified in nsswitch.conf. Each entry in nsswitch.conf consists of a database name, and a space separated list of sources. Each source can have an optional trailing criterion that determines whether the next listed source is used, or the search terminates at the current source. Each criterion consists of one or more status codes, and actions to take if that status code occurs. Sources The following sources are implemented: Source Description files Local files, such as /etc/hosts, and /etc/passwd. db Local database. dns Internet Domain Name System. ``hosts'' and 'networks' use IN class entries, all other databases use HS class (Hesiod) entries. nis NIS (formerly YP) compat support '+/-' in the ``passwd'' and ``group'' databases. If this is present, it must be the only source for that entry. cache makes use of the nscd(8) daemon. Databases The following databases are used by the following C library functions: Database Used by group getgrent(3), getgrent_r(3), getgrgid_r(3), getgrnam_r(3), setgrent(3), endgrent(3) hosts getaddrinfo(3), gethostbyaddr(3), gethostbyaddr_r(3), gethostbyname(3), gethostbyname2(3), gethostbyname_r(3), getipnodebyaddr(3), getipnodebyname(3) networks getnetbyaddr(3), getnetbyaddr_r(3), getnetbyname(3), getnetbyname_r(3) passwd getpwent(3), getpwent_r(3), getpwnam_r(3), getpwuid_r(3), setpwent(3), endpwent(3) shells getusershell(3) services getservent(3) rpc getrpcbyname(3), getrpcbynumber(3), getrpcent(3) proto getprotobyname(3), getprotobynumber(3), getprotoent(3) netgroup getnetgrent(3), setnetgrent(3), innetgr(3) Status codes The following status codes are available: Status Description success The requested entry was found. notfound The entry is not present at this source. tryagain The source is busy, and may respond to retries. unavail The source is not responding, or entry is corrupt. Actions For each of the status codes, one of two actions is possible: Action Description continue Try the next source return Return with the current result Format of file A BNF description of the syntax of nsswitch.conf is: <entry> ::= <database> ":" [<source> [<criteria>]]* <criteria> ::= "[" <criterion>+ "]" <criterion> ::= <status> "=" <action> <status> ::= "success" | "notfound" | "unavail" | "tryagain" <action> ::= "return" | "continue" Each entry starts on a new line in the file. A '#' delimits a comment to end of line. Blank lines are ignored. A '' at the end of a line escapes the newline, and causes the next line to be a continuation of the current line. All entries are case-insensitive. The default criteria is to return on ``success'', and continue on anything else (i.e, [success=return notfound=continue unavail=continue tryagain=continue]). Cache You can enable caching for the particular database by specifying ``cache'' as the first source in the nsswitch.conf(5) file. You should also enable caching for this database in nscd.conf(5). If for the particular query ``cache'' source returns success, no further sources are queried. On the other hand, if there are no previously cached data, the query result will be placed into the cache right after all other sources are processed. Note, that ``cache'' requires nscd(8) daemon to be running. Compat mode: +/- syntax In historical multi-source implementations, the '+' and '-' characters are used to specify the importing of user password and group informa- tion from NIS. Although nsswitch.conf provides alternative methods of accessing distributed sources such as NIS, specifying a sole source of ``compat'' will provide the historical behaviour. An alternative source for the information accessed via '+/-' can be used by specifying ``passwd_compat: source''. ``source'' in this case can be 'dns', 'nis', or any other source except for 'files' and 'compat'. Notes Historically, many of the databases had enumeration functions, often of the form getXXXent(). These made sense when the databases were in local files, but do not make sense or have lesser relevance when there are possibly multiple sources, each of an unknown size. The inter- faces are still provided for compatibility, but the source may not be able to provide complete entries, or duplicate entries may be retrieved if multiple sources that contain similar information are specified. To ensure compatibility with previous and current implementations, the ``compat'' source must appear alone for a given database. Default source lists If, for any reason, nsswitch.conf does not exist, or it has missing or corrupt entries, nsdispatch(3) will default to an entry of ``files'' for the requested database. Exceptions are: Database Default source list group compat group_compat nis hosts files dns passwd compat passwd_compat nis services compat services_compat nis FILES
/etc/nsswitch.conf The file nsswitch.conf resides in /etc. EXAMPLES
To lookup hosts in cache, then in /etc/hosts and then from the DNS, and lookup user information from NIS then files, use: hosts: cache files dns passwd: nis [notfound=return] files group: nis [notfound=return] files The criteria ``[notfound=return]'' sets a policy of "if the user is notfound in nis, do not try files." This treats nis as the authoritative source of information, except when the server is down. NOTES
If system got compiled with WITHOUT_NIS you have to remove 'nis' entries. FreeBSD's Standard C Library (libc, -lc) provides stubs for compatibility with NSS modules written for the GNU C Library nsswitch interface. However, these stubs only support the use of the ``passwd'' and ``group'' databases. SEE ALSO
nsdispatch(3), nscd.conf(5), resolv.conf(5), nscd(8), ypbind(8) HISTORY
The nsswitch.conf file format first appeared in FreeBSD 5.0. It was imported from the NetBSD Project, where it appeared first in NetBSD 1.4. AUTHORS
Luke Mewburn <lukem@netbsd.org> wrote this freely distributable name-service switch implementation, using ideas from the ULTRIX svc.conf(5) and Solaris nsswitch.conf(4) manual pages. BSD
December 25, 2013 BSD
All times are GMT -4. The time now is 11:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy