From owner-freebsd-current@FreeBSD.ORG Tue May 18 00:41:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5222A16A4CE for ; Tue, 18 May 2004 00:41:27 -0700 (PDT) Received: from ioskeha.hittite.isp.9tel.net (ioskeha.hittite.isp.9tel.net [62.62.156.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4C9F43D55 for ; Tue, 18 May 2004 00:41:25 -0700 (PDT) (envelope-from clefevre-lists@9online.fr) Received: from pc2k (unknown [81.185.56.16]) by ioskeha.hittite.isp.9tel.net (Postfix) with SMTP id 056F717B5B3; Tue, 18 May 2004 09:42:14 +0200 (CEST) Message-ID: <01f401c43cab$853edc20$7890a8c0@dyndns.org> From: "Cyrille Lefevre" To: "Matthew D. Fuller" , "Christian Hiris" <4711@chello.at> References: <0cc701c43704$fe189fc0$7890a8c0@dyndns.org> <200405110321.i4B3LFGI073037@bunrab.catwhisker.org> <20040511093634.GA41727@gits.dyndns.org> <200405180814.15854.4711@chello.at> <20040518063753.GB2038@over-yonder.net> Date: Tue, 18 May 2004 09:41:23 +0200 Organization: ACME MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: freebsd-current@freebsd.org Subject: Re: bind timeouts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2004 07:41:27 -0000 "Matthew D. Fuller" wrote: > On Tue, May 18, 2004 at 08:14:04AM +0200 I heard the voice of > Christian Hiris, and lo! it spake thus: > > > > As far as i know MX records _must_ have an A record. > > RFC1035 states: > MX records cause type A additional section processing for the host > specified by EXCHANGE. The use of MX RRs is explained in detail > in [RFC-974]. > > RFC974 says: > There is one other special case. If the response contains an > answer which is a CNAME RR, it indicates that REMOTE is actually > an alias for some other domain name. The query should be repeated > with the canonical domain name. > > RFC2821 obsoletes 974, but says substantially the same in regards to > CNAME's. So, by the RFC's it's allowed. > > > For me, I think it's a bad practice. But, hey... not necesserally, an mx could point to a cname which is an rr record :) which could explain why this is allowed. google search : bind "in mx" http://www.zytrax.com/books/dns/ch8/mx.html http://www.zytrax.com/books/dns/ch9/rr.html Cyrille Lefevre. -- home: mailto:cyrille.lefevre@laposte.net