From owner-freebsd-net@FreeBSD.ORG  Tue Oct 12 14:39:33 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 BA5F710656A4
	for <net@freebsd.org>; Tue, 12 Oct 2010 14:39:33 +0000 (UTC)
	(envelope-from smithi@nimnet.asn.au)
Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159])
	by mx1.freebsd.org (Postfix) with ESMTP id 2DBEA8FC17
	for <net@freebsd.org>; Tue, 12 Oct 2010 14:39:32 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o9CEdVwV046340;
	Wed, 13 Oct 2010 01:39:31 +1100 (EST)
	(envelope-from smithi@nimnet.asn.au)
Date: Wed, 13 Oct 2010 01:39:30 +1100 (EST)
From: Ian Smith <smithi@nimnet.asn.au>
To: Tom Evans <tevans.uk@googlemail.com>
In-Reply-To: <AANLkTikKQO+jQy=2pNMngdPGaY1AO7Bqwt-Dd0sK1Ufd@mail.gmail.com>
Message-ID: <20101013010757.N2036@sola.nimnet.asn.au>
References: <4CB2AF28.30309@rdtc.ru> <20101012152857.X2036@sola.nimnet.asn.au>
	<AANLkTikKQO+jQy=2pNMngdPGaY1AO7Bqwt-Dd0sK1Ufd@mail.gmail.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-1241133225-1286894370=:2036"
Cc: dougb@freebsd.org, 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 14:39:33 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1241133225-1286894370=:2036
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT

On Tue, 12 Oct 2010, Tom Evans wrote:
 > On Tue, Oct 12, 2010 at 10:05 AM, Ian Smith <smithi@nimnet.asn.au> wrote:
 > > On Mon, 11 Oct 2010, Eugene Grosbein wrote:
 > >  > Hi!
 > >  >
 > >  > FreeBSD 8.1-STABLE:
 > >  >
 > >  > # host koin-nkz.com.
 > >  > koin-nkz.com has address 62.231.164.101
 > >  > Host koin-nkz.com not found: 3(NXDOMAIN)
 > >  >
 > >  > This domain does not have MX records but NXDOMAIN seems to wrong return
 > >  > code to me. Think about MTA that does look-up for MX first,
 > >  > obtains NXDOMAIN and rejects mail.
 > >
 > > If a domain has no MX server, how's an MTA supposed to do mail with it?
 > >
 > 
 > The same way as has been done since they invented the MX record type -
 > if no MX record exists, fallback to an A record. See RFC 5321, section
 > 5.1.

Well thanks Tom, I did - but which A record?

Taking the '5.3. Master file example' in RFC1035, what is the A response 
for 'ISI.EDU.' where the domain itself has no specific A RR?  Would it 
be that of VENERA.ISI.EDU, or that of the first A listed, ie A.ISI.EDU?

And in either case - assuming a domain without any MX RR as above - why 
would that A response be expected to address a mail server?

cc Doug for obvious reasons, ie I'm likely missing something obvious :)

cheers, Ian

(BTW I'd begun to reply off-list, as neither your private copy nor your 
reply to the list indicated cc'ing the other .. googlemail quaintness?)
--0-1241133225-1286894370=:2036--