Sponsored Content
Operating Systems Solaris unable to ping a host in another domain Post 302254372 by incredible on Tuesday 4th of November 2008 08:38:14 AM
Old 11-04-2008
You will have to add the hostname/Ip in your /etc/hosts file.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unable to ping host

Hi, dear all, I am rather new to Unix and have this problem where I cant seem to ping from 1 host to another. The scenerio is as follows: - 1 QNX host->Eth->1 SCO host the SCO host is configured with it's IP the QNX host is configured with another IP both in the same domain, ie, 172.20.3.XX... (3 Replies)
Discussion started by: gavon
3 Replies

2. IP Networking

QNX host cannot ping SCO host, vice versa

The problem I am facing now is that the QNX host could not ping the SCO host and vice versa. They are in the same domain, ie, 172.20.3.xx. As I am very new to Unix, I guess I must have missed out some important steps. Pls help... Thanx alot (2 Replies)
Discussion started by: gavon
2 Replies

3. UNIX for Dummies Questions & Answers

Host file and domain name

Hi all, I've got a question, it's probably a basic problem, but as i'm new to unix thought i'd try this forum out. The problem is, i'm trying to use to alias entries on the hosts file, which point to an NT IIS Server. The DNS server is a unix sun solaris. On the sun, i've filled in the... (2 Replies)
Discussion started by: nickad
2 Replies

4. Solaris

PING - Unknown host 127.0.0.1, Unknown host localhost - Solaris 10

Hello, I have a problem - I created a chrooted jail for one user. When I'm logged in as root, everything work fine, but when I'm logged in as a chrooted user - I have many problems: 1. When I execute the command ping, I get weird results: bash-3.00$ usr/sbin/ping localhost ... (4 Replies)
Discussion started by: Przemek
4 Replies

5. IP Networking

Unable to ping freebsd machine using fully qualified domain name

hi all. am unable to ping a freebsd machine using fully qualified domain name from a windows machine. i have already set the fqdn for the machine. plz advise me. thanks. (2 Replies)
Discussion started by: coolatt
2 Replies

6. Solaris

Unable to ping Solaris VM from Xp host

Hi All, I am using Vmware Workstation 6.0.3 build-80004. Guest OS: Solaris 10 Host OS : Win XP I am getting request time out when i am trying to ping from XP ( cmd line) to Solaris VM - I have assigned IP 192.168.50.5 in Solaris VM ( Hostname: Tower1) and it is in UP status. ... (4 Replies)
Discussion started by: saurabh84g
4 Replies

7. IP Networking

ping can not recognize host but host command can

Hi, I have a weird problem. when ever I do ping command like for example ping unix.comI get the following message: # ping unix.com ping: unknown host unix.com but when I use host the computer is able to know the host. # host unix.com unix.com has address 81.17.242.186 unix.com mail is... (2 Replies)
Discussion started by: programAngel
2 Replies

8. Linux

Unable to ping Linux guest from win7 host

Hi, I am using win7 on my PC and installed VMware on it on which i am running linux I am unable to ping my linux guest from my win machine, but i can ping my windows host from linux guest : Below is my system configuration Linux root@localhost ~]# ifconfig eth0 Link... (9 Replies)
Discussion started by: chander_1987
9 Replies

9. Solaris

Network issue on multinic. Unable to ping a host from One NIC but other works

Dear, I hope you all will be ok. I have an issue with Solaris box running on x86 Blade. I am unable to ping a node neither traceroute. I am able to do traceroute from oce0:6 port which have IP and subnet of same type which oce0:1 has. details are as follows: Problem: root@rinams02:/#... (3 Replies)
Discussion started by: khaniqshahid
3 Replies

10. IP Networking

Ping domain indicates the external ip address and not the local ip

when i execute from local machine ping domainname i get the external ip address but i am on local dns and i expect the local ip address.. using nslookup : no problem so i cannot find why... thanks (2 Replies)
Discussion started by: activedms
2 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 keywords recognized are order, trim, multi, nospoof, and reorder. These keywords are described below. 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. trim This keyword may be listed more than once. Each time it should be followed by a single domain name, with the leading dot. When set, the resolv+ 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 host- names gathered via NIS or the hosts file. Care should be taken to ensure that the first hostname for each entry in the hosts file is fully qualified or non-qualified, as appropriate for the local installation.) multi Valid values are on and off. If set to on, the resolv+ 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. nospoof Valid values are on and off. If set to on, the resolv+ 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, resolv+ will perform a hostname lookup for that address. If the two hostnames do not match, the query will fail. spoofalert If this option is set to on and the nospoof option is also set, resolv+ will log a warning of the error via the syslog facility. The default value is off. reorder Valid values are on and off. If set to on, resolv+ 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. FILES
/etc/host.conf Resolver configuration file /etc/resolv.conf Resolver configuration file /etc/hosts Local hosts database SEE ALSO
gethostbyname(3), hostname(7), resolv+(8), named(8) Debian GNU/Linux 1997-01-02 HOST.CONF(5)
All times are GMT -4. The time now is 07:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy