Date: Tue, 22 Jul 1997 23:45:20 -0400 From: "Gary Palmer" <gpalmer@FreeBSD.ORG> To: "Francis W.S. Yeh" <francis@mail.adc.iii.org.tw> Cc: stable@FreeBSD.ORG Subject: Re: Bug report Message-ID: <8342.869629520@orion.webspan.net> In-Reply-To: Your message of "Wed, 23 Jul 1997 09:15:41 %2B0800." <33D55B3D.1C4B9ADF@adc.iii.org.tw>
next in thread | previous in thread | raw e-mail | index | archive | help
"Francis W.S. Yeh" wrote in message ID <33D55B3D.1C4B9ADF@adc.iii.org.tw>: > 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? The block on _'s in domain names isn't in the nameserver, but in the resolver library. nslookup doesn't use the resolver library, but `ping', `traceroute' et al do. The resolver in 2.2 and later was upgraded to a newer release of BIND, which contained the stricter checks. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8342.869629520>