From owner-freebsd-net@FreeBSD.ORG  Tue Oct 12 03:32:10 2010
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1145E1065673
	for <net@freebsd.org>; Tue, 12 Oct 2010 03:32:10 +0000 (UTC)
	(envelope-from egrosbein@rdtc.ru)
Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [62.231.161.221])
	by mx1.freebsd.org (Postfix) with ESMTP id 5449C8FC18
	for <net@freebsd.org>; Tue, 12 Oct 2010 03:32:08 +0000 (UTC)
Received: from eg.sd.rdtc.ru (localhost [127.0.0.1])
	by eg.sd.rdtc.ru (8.14.4/8.14.4) with ESMTP id o9C3W6Ex085258;
	Tue, 12 Oct 2010 10:32:06 +0700 (NOVST)
	(envelope-from egrosbein@rdtc.ru)
Message-ID: <4CB3D6B6.9060001@rdtc.ru>
Date: Tue, 12 Oct 2010 10:32:06 +0700
From: Eugene Grosbein <egrosbein@rdtc.ru>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU;
	rv:1.9.1.10) Gecko/20100712 Thunderbird/3.0.5
MIME-Version: 1.0
To: Hajimu UMEMOTO <ume@freebsd.org>
References: <4CB2AF28.30309@rdtc.ru> <ygemxqlrnuz.wl%ume@mahoroba.org>
In-Reply-To: <ygemxqlrnuz.wl%ume@mahoroba.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: net@freebsd.org
Subject: Re: strange resolver behavour
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 03:32:10 -0000

On 11.10.2010 18:05, Hajimu UMEMOTO wrote:

> egrosbein> Is it a bug in our resolver?
> 
> I think no, host(1) links ISC's resolver, and it doesn't use libc's
> resolver.  I suspect there is some problem in host(1) or ISC's
> resolver.

Is there a command capable of looking up MX records and
linked with libc resolver in base system?

It's a pity if we have no diagnostic utility that behaves just like
ordinary applications like MTA dealing with DNS... How am I supposed
to debug suspected MTA behavior without such utility?

Eugene Grosbein