From owner-freebsd-stable Tue Jul 22 18:16:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA13205 for stable-outgoing; Tue, 22 Jul 1997 18:16:55 -0700 (PDT) Received: from mail.adc.iii.org.tw (mail.adc.iii.org.tw [140.92.75.200]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA13187 for ; Tue, 22 Jul 1997 18:16:46 -0700 (PDT) Received: from francis (francis.adc.iii.org.tw [140.92.75.109]) by mail.adc.iii.org.tw (8.8.6/8.8.5) with ESMTP id IAA24304 for ; Wed, 23 Jul 1997 08:51:39 +0800 (CST) Message-ID: <33D55B3D.1C4B9ADF@adc.iii.org.tw> Date: Wed, 23 Jul 1997 09:15:41 +0800 From: "Francis W.S. Yeh" Organization: Avionics Development Center/Institute for Information Industry X-Mailer: Mozilla 4.01 [en] (WinNT; I) MIME-Version: 1.0 To: stable@freebsd.org Subject: Bug report X-Priority: 3 (Normal) Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dear Sir: Here is a situation I met on our FreeBSD 2.2.2R (prior to 2.2-970625-RELENG) that I consider a bug. A transcript of the commands that shows this problem is listed below: ------------------------------------------------------------------- mail2[francis]:~> nslookup www.bcc.com.tw Server: mail.adc.iii.org.tw Address: 140.92.75.200 Non-authoritative answer: Name: BCC_WWW.BCC.COM.TW Address: 203.69.33.1 Aliases: www.bcc.com.tw mail2[francis]:~> ping www.bcc.com.tw ping: unknown host www.bcc.com.tw mail2[francis]:~> ------------------------------------------------------------------- On another FreeBSD 2.2.2R system in the same IP subnet which serves as our name server, the same problem exists. However, on two other systems in the same IP subnet with the same DNS settings, the situation does not occur. One of them is a Sun Ultra1 running Solaris 2.5.1. The other one is a Windows NT workstation 4.0 Chinese edition Pentium PC. I posted the problem on a news group for FreeBSD which is local to our country a few days ago and got some response. Another one with a FreeBSD 2.2.2R, a FreeBSD 2.2-970625-RELENG and an older FreeBSD system responded with similar observation. He found the same problem on his FreeBSD 2.2.2R and 2.2-970625-RELENG systems but the older system works well. Some one suggests that the problem is related to the other FQDN of www.bcc.com.tw, i.e. BCC_WWW.BCC.COM.TW, for it has a '_' in its host name. According to RFC1034, '_' is not said to be an allowable label character. However, I still wonder why this happens: (1) Why does nslookup works while ping fails? (2) Why does other systems works (including older version of FreeBSD) while FreeBSD 2.2.2R and later fails? Thanks for all your excellent works. Regards. -- Francis Wu-Sung Yeh Avionics Development Center / Institute for Information Industry 4F, 134, Section 3, Min-Sheng East Road, Taipei, Taiwan, R.O.C. Tel: 886-2-718-9123 ext.134 Fax: 886-2-545-3950