From owner-freebsd-current Mon Apr 24 12:38:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA14313 for current-outgoing; Mon, 24 Apr 1995 12:38:10 -0700 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA14307 for ; Mon, 24 Apr 1995 12:38:09 -0700 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.11/8.6.9) with SMTP id MAA18981 for ; Mon, 24 Apr 1995 12:38:06 -0700 Message-Id: <199504241938.MAA18981@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: current@FreeBSD.org Subject: Resolver wierdness Date: Mon, 24 Apr 1995 12:38:06 -0700 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk I have the following for my resolv.conf: domain CS.Berkeley.EDU nameserver 128.32.42.47 nameserver 128.32.136.9 nameserver 128.32.136.12 search CS.Berkeley.EDU EECS.Berkeley.EDU CSUA.Berkeley.EDU Berkeley.EDU HIP.Berk eley.EDU Recently the first server's named died so I began to resolve through 128.32.136.9. The funny thing was that during that time, lookups for non-fully-qualified hostnames would fail for say a telnet or a ping, but nslookup would resolve them fine. Does any one know why? As soon as the first DNS machine got its named restarted, all resolving occured normally. __ Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ==============================================