From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eyas.biff.org.uk (eyas.biff.org.uk [IPv6:2001:41c8:1:519c::20]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 89D0121F14E for ; Thu, 6 Feb 2014 02:53:34 -0800 (PST) Received: from cl-1441.lon-02.gb.sixxs.net ([2a01:348:6:5a0::2]:42082 helo=central.thekelleys.org.uk) by eyas.biff.org.uk with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1WBMaJ-0007s7-VK; Thu, 06 Feb 2014 10:53:32 +0000 Received: from spike.thekelleys.org.uk ([192.168.0.193]) by central.thekelleys.org.uk with esmtpa (Exim 4.72) (envelope-from ) id 1WBMaJ-0004hh-5Q; Thu, 06 Feb 2014 10:53:31 +0000 Message-ID: <52F369AA.5060809@thekelleys.org.uk> Date: Thu, 06 Feb 2014 10:53:30 +0000 From: Simon Kelley User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120726 Icedove/3.0.11 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Toke_H=F8iland-J=F8rgensen?= References: <87a9e6xcae.fsf@alrua-x1.kau.toke.dk> <87ob2lmqny.fsf@toke.dk> <52F29645.6010001@thekelleys.org.uk> <874n4dwcdb.fsf@alrua-x1.kau.toke.dk> <52F2BA80.9010202@thekelleys.org.uk> <87iossvgw4.fsf@alrua-x1.kau.toke.dk> In-Reply-To: <87iossvgw4.fsf@alrua-x1.kau.toke.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: cerowrt-devel@lists.bufferbloat.net Subject: Re: [Cerowrt-devel] Fwd: [Dnsmasq-discuss] Testers wanted: DNSSEC. X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Feb 2014 10:53:34 -0000 On 06/02/14 07:28, Toke Høiland-Jørgensen wrote: > Simon Kelley writes: > >> That's straightforward. Dnsmasq gets a query for >> 62.75.115.213.in-addr.arpa, sends it upstream, gets an answer which >> isn't signed, and determines that it's insecure, then returns the >> answer. > > Right, that's what I thought. So everything is working as it should? :) > > -Toke Everything is working as I would expect it to. If that's correct or not depends on how well I've understood the standard, and is a a whole different question :-) Cheers, Simon.