From owner-freebsd-questions@FreeBSD.ORG Sat Jan 31 10:38:05 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2787416A4CE for ; Sat, 31 Jan 2004 10:38:05 -0800 (PST) Received: from cheyenne.wixb.com (cheyenne.wixb.com [65.43.82.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAEEF43D48 for ; Sat, 31 Jan 2004 10:38:03 -0800 (PST) (envelope-from jbronson@lonebandit.com) Received: from thinkpad.lonebandit.com (thinkpad.wixb.com [10.43.82.5]) by cheyenne.wixb.com (8.12.11/8.12.11) with ESMTP id i0VIc3CP015876; Sat, 31 Jan 2004 12:38:03 -0600 (CST) Message-Id: <6.0.2.0.2.20040131123020.00b531b8@cheyenne.wixb.com> Date: Sat, 31 Jan 2004 12:38:03 -0600 To: freebsd-questions@freebsd.org From: "J.D. Bronson" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: finger information X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2004 18:38:05 -0000 (I dont run finger to the outside..only within the machine itself). I am running 4.9 and noticed that finger will not resolve internal IPs whereas it will resolve external IPs sorta... For example: # finger testacct Login: testacct Name: Test Account Directory: /home/testacct Shell: /bin/tcsh On since Sat Jan 31 11:39 (CST) on ttyp0 from 207.227.112.116 No Mail. No Plan. ..but when 'testacct' logs out, the finger information will then reveal the NAME of the IP... # finger testacct Login: testacct Name: Test Account Directory: /home/testacct Shell: /bin/tcsh Last login Sat Jan 31 11:39 (CST) on ttyp1 from karliscool.cyberly No Mail. No Plan. However on internal telnets within the lan, the live and stale finger information only show the IP...it never resolves. I run my own DNS and know BIND -very- well. I dont believe that this is a DNS issue and nslookup on the LAN IPs all resolves forward/reverse just fine. Any thoughts? -- J.D. Bronson - "LoneBandit" Aurora Health Care // Information Services // Milwaukee, WI USA Office: 414.978.8282 // Email: jd@aurora.org // Pager: 414.314.8282