From owner-freebsd-hackers Wed Apr 3 10:40:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA14125 for hackers-outgoing; Wed, 3 Apr 1996 10:40:21 -0800 (PST) Received: from etinc.com (etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA14120 for ; Wed, 3 Apr 1996 10:40:15 -0800 (PST) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id NAA06157 for ; Wed, 3 Apr 1996 13:42:43 -0500 Date: Wed, 3 Apr 1996 13:42:43 -0500 Message-Id: <199604031842.NAA06157@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: hackers@freebsd.org From: dennis@etinc.com (dennis) Subject: NFS problem? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It seems that you do a mount with an address: mount 200.1.1.1:/usr /mnt it will fail if the address fails DNS lookup. With no configuration changes but a repaired resolv.conf, the mount succeeds. Is this the expected behaviour? Shouldnt you be able to mount with addresses to/from unnamed machines? Dennis ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous Communications Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD and LINUX