From owner-freebsd-net@FreeBSD.ORG  Tue Oct 12 12:52:05 2010
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 25716106566B;
	Tue, 12 Oct 2010 12:52:05 +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 83F5C8FC18;
	Tue, 12 Oct 2010 12:52:04 +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 o9CCYTFn088870;
	Tue, 12 Oct 2010 19:34:29 +0700 (NOVST)
	(envelope-from egrosbein@rdtc.ru)
Message-ID: <4CB455D5.1080902@rdtc.ru>
Date: Tue, 12 Oct 2010 19:34:29 +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: Doug Barton <dougb@freebsd.org>
References: <4CB2AF28.30309@rdtc.ru>
	<ygemxqlrnuz.wl%ume@mahoroba.org>	<4CB3D6B6.9060001@rdtc.ru>
	<4CB409DA.1060705@FreeBSD.org>
In-Reply-To: <4CB409DA.1060705@FreeBSD.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: freebsd-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 12:52:05 -0000

On 12.10.2010 14:10, Doug Barton wrote:

>> 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?
> 
> Step 1, verify that your authoritative name servers have MX records in 
> the first place. As it turns out, they don't.

That is not my domain and I really don't care about
its MX records/lame delegations/etc.

I care about my resolver behavior.

> 
> The proper tool to use to diagnose DNS problems is dig. It's more 
> complex than the tools that are designed to just give you the answer, 
> but if everything were working right to start with you wouldn't need to 
> diagnose anything. See how that works? :)

Hmm, I don't want to debug DNS problems - indeed, dig is nice tool.
I need to debug system resolver that is different thing, as you know.

Eugene Grosbein