From owner-freebsd-questions Tue Mar 25 13:40:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA11765 for questions-outgoing; Tue, 25 Mar 1997 13:40:55 -0800 (PST) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA11754; Tue, 25 Mar 1997 13:40:51 -0800 (PST) Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id NAA04303; Tue, 25 Mar 1997 13:40:50 -0800 Date: Tue, 25 Mar 1997 13:40:50 -0800 From: "Jin Guojun[ITG]" Message-Id: <199703252140.NAA04303@george.lbl.gov> To: bugs@freebsd.org Subject: Re: /etc/hosts no longer used for rexec() ? Cc: questions@freebsd.org Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk % more /etc/host.conf # $Id: host.conf,v 1.2 1993/11/07 01:02:57 wollman Exp $ # If that doesn't work, then try the /etc/hosts file hosts # Default is to use the nameserver first bind # If you have YP/NIS configured, uncomment the next line # nis I guess it is a bug in somewhere I do not know. ping and telnet work well under such circumstance. However, rsh, rcp, rlogin etc. do NOT work if DNS is not reachable. It may be the rexec() 's problem. I am sure they tried to talk to DNS even though my /etc/host.conf is correct. The tcpdump shows that these program try to talk to DNS regardless the /etc/hosts and /etc/host.conf. So, I changed the Subject. -Jin } Look into /etc/host.conf } Word 'hosts' must appear BEFORE 'bind' in this file } } On Tue, 25 Mar 1997, Jin Guojun[ITG] wrote: } } > Date: Tue, 25 Mar 1997 10:03:57 -0800 } > From: "Jin Guojun[ITG]" } > To: questions@freebsd.org } > Cc: bugs@freebsd.org } > Subject: /etc/hosts no longer used for both 2.1.7 and 2.2 ? } > } > } > It seems that /etc/hosts is no longer used by FreeBSD design. } > Is this a bug or intended to do in this way? The FreeBSD seems intend to } > use DNS all the time, regardless the content of the /etc/hosts. } > } > Would some one please tell me if any way to force FreeBSD to use /etc/hosts } > to do the name resolving? } > The problem is that the DNS may taken down for service or un-reachable due to } > some network problem; then all machines will hang until DNS come back, which } > is real painful when this happened and the /etc/hosts cannot be used for } > backup. If the /etc/hosts has been intended to put out of service, it may be } > concerned as a bug because there is no way to guarantee all DNS up all the tim } e. } > } > Thanks for help in advance, } > } > -Jin }