From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WqOAD-0007o6-7P for bitcoin-development@lists.sourceforge.net; Fri, 30 May 2014 14:52:09 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of mckay.com designates 37.1.88.131 as permitted sender) client-ip=37.1.88.131; envelope-from=robert@mckay.com; helo=mail.mckay.com; Received: from mail.mckay.com ([37.1.88.131]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WqOAB-0002Dv-Lf for bitcoin-development@lists.sourceforge.net; Fri, 30 May 2014 14:52:09 +0000 Received: from www-data by mail.mckay.com with local (Exim 4.76) (envelope-from ) id 1WqOA2-0007gQ-Vb; Fri, 30 May 2014 15:51:59 +0100 To: Alex Kotenko X-PHP-Originating-Script: 0:func.inc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Fri, 30 May 2014 15:51:58 +0100 From: Robert McKay In-Reply-To: References: <20140523221726.GA30143@petertodd.org> <20140526163753.GA18693@petertodd.org> Message-ID: <48331d04b68b3d6554b4e59e97ffbafe@webmail.mckay.com> X-Sender: robert@mckay.com User-Agent: Roundcube Webmail/0.5.3 X-Spam-Score: -2.3 (--) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WqOAB-0002Dv-Lf Cc: Bitcoin Dev , Andreas Schildbach Subject: Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 May 2014 14:52:09 -0000 No, I don't think so. The problem is the 'aa' flag is missing (see the 'flags' section in dig). Perhaps if you could suppress the authority records the recursor would give up and just accept the non-authorative answer, but that isn't a good solution even if it might work for some resolvers. Rob On Fri, 30 May 2014 15:13:36 +0100, Alex Kotenko wrote: > Hmm, you might be right, as queries  > dig @node.alexykot.me [8] testnet-seed.alexykot.me [9] > > ​and  > dig @node.alexykot.me [10] -p 18353 testnet-seed.alexykot.me > [11]​ > > ​are giving different authority sections. > > Hmm, but if I setup custom SOA record for it - it should work, > right?  > What SOA name should it be actually, assuming that NS record for > testnet-seed.alexykot.me [12] is pointing at alexykot.me [13]? > > Best regards,  > > Alex Kotenko > > 2014-05-30 14:41 GMT+01:00 Robert McKay : > >> Hi Alex, >> >> I think the problem is with my suggestion to use bind forwarding.. >> basically bind is stripping off the authorative answer bit in the >> reply.. this causes the recursor to go into a loop chasing the >> authority server which again returns a non-authoritve answer with >> itself as the authority again. Im not sure if this can be fixed >> without hacking the bind src, so maybe it wasnt such a great >> suggestion in the first place. Basically I think if bind was >> returning authorative answers it would work, but I cant see any way >> to make that happen in the bind configuration. >> >> Rob >> >> On Fri, 30 May 2014 14:19:05 +0100, Alex Kotenko wrote: >> >>> Hi Peter >>> >>> Ive setup DNS seeds myself a week ago, at >>> testnet-seed.alexykot.me [1] [6] >>> and bitcoin-seed.alexykot.me [2] [7], but there is a problem with >>> DNS >>> settings that we with Andreas couldnt sort out quickly. >>> >>> The problem itself is that I can reach my nameserver and get >>> dnsseed >>> response if I query it directly with >>>  dig @node.alexykot.me [3] [8] testnet-seed.alexykot.me [4] [9] >>> >>>  dig @node.alexykot.me [5] [10] bitcoin-seed.alexykot.me [6] >>> [11] >>> >>> ​But when I try nslookup testnet-seed.alexykot.me [7] [12]​ - >>> it >>> fails.  >>> I guess the problem is in my DNS settings but I cant figure out >>> what >>> is it. >>> >>> ​S o could you share >>> ​how you configured DNS >>>  ​ for your seed >>> ​ to help me debug >>>  ​mine >>> ?  >>> >>> Best regards,  >>> >>> Alex Kotenko >>> >>> ​ > > > Links: > ------ > [1] http://testnet-seed.alexykot.me > [2] http://bitcoin-seed.alexykot.me > [3] http://node.alexykot.me > [4] http://testnet-seed.alexykot.me > [5] http://node.alexykot.me > [6] http://bitcoin-seed.alexykot.me > [7] http://testnet-seed.alexykot.me > [8] http://node.alexykot.me/ > [9] http://testnet-seed.alexykot.me/ > [10] http://node.alexykot.me/ > [11] http://testnet-seed.alexykot.me/ > [12] http://testnet-seed.alexykot.me > [13] http://alexykot.me > [14] mailto:robert@mckay.com