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 1Wr2WJ-0004RW-Ut for bitcoin-development@lists.sourceforge.net; Sun, 01 Jun 2014 09:57:40 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.220.171 as permitted sender) client-ip=209.85.220.171; envelope-from=alexy.kot.all@gmail.com; helo=mail-vc0-f171.google.com; Received: from mail-vc0-f171.google.com ([209.85.220.171]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wr2WI-0004RI-PN for bitcoin-development@lists.sourceforge.net; Sun, 01 Jun 2014 09:57:39 +0000 Received: by mail-vc0-f171.google.com with SMTP id lc6so3941581vcb.30 for ; Sun, 01 Jun 2014 02:57:33 -0700 (PDT) X-Received: by 10.220.53.72 with SMTP id l8mr24713335vcg.16.1401616653003; Sun, 01 Jun 2014 02:57:33 -0700 (PDT) MIME-Version: 1.0 Sender: alexy.kot.all@gmail.com Received: by 10.58.181.71 with HTTP; Sun, 1 Jun 2014 02:56:52 -0700 (PDT) In-Reply-To: <48331d04b68b3d6554b4e59e97ffbafe@webmail.mckay.com> References: <20140523221726.GA30143@petertodd.org> <20140526163753.GA18693@petertodd.org> <48331d04b68b3d6554b4e59e97ffbafe@webmail.mckay.com> From: Alex Kotenko Date: Sun, 1 Jun 2014 10:56:52 +0100 X-Google-Sender-Auth: ZOGsDy4xqeyohtEMgroklt-o8g4 Message-ID: To: Robert McKay Content-Type: multipart/alternative; boundary=001a11c2cb12b6d3ff04fac34eaa X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (alexy.kot.all[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.3 HTML_FONT_FACE_BAD BODY: HTML font face is not a word -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: 1Wr2WI-0004RI-PN 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: Sun, 01 Jun 2014 09:57:40 -0000 --001a11c2cb12b6d3ff04fac34eaa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable So generally it seems impossible to have both DNS seeds running on same IP address. Too bad. Ok, I'll switch to serving only testnet DNS on this server for now, as this seems to be a much bigger problem than mainnet. Later I might buy second IP to setup mainnet DNS also. Best regards, Alex Kotenko 2014-05-30 15:51 GMT+01:00 Robert McKay : > 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] >> >> =E2=80=8Band >> dig @node.alexykot.me [10] -p 18353 testnet-seed.alexykot.me >> [11]=E2=80=8B >> >> =E2=80=8Bare 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] >>>> >>>> =E2=80=8BBut when I try nslookup testnet-seed.alexykot.me [7] [12]=E2= =80=8B - >>>> >>>> it >>>> fails. >>>> I guess the problem is in my DNS settings but I cant figure out >>>> what >>>> is it. >>>> >>>> =E2=80=8BS o could you share >>>> =E2=80=8Bhow you configured DNS >>>> =E2=80=8B for your seed >>>> =E2=80=8B to help me debug >>>> =E2=80=8Bmine >>>> ? >>>> >>>> Best regards, >>>> >>>> Alex Kotenko >>>> >>>> =E2=80=8B >>>> >>> >> >> 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 >> > > --001a11c2cb12b6d3ff04fac34eaa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
So generally it seems impossible to have both = DNS seeds running on same IP address. Too bad.=C2=A0
Ok, I'll switch to serving only testnet DNS on this server for now, as = this seems to be a much bigger problem than mainnet. Later I might buy seco= nd IP to setup mainnet DNS also.


Best regards,=C2=A0
Alex Kotenko


2014-05-30 15:51 GMT+01:00 Robert McKay = <robert@mckay.com>:
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-author= ative 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=C2=A0
dig @node.alexykot.me= [8]=C2=A0testnet-seed.alexykot.me [9]

=E2=80=8Band=C2=A0
=C2=A0dig @node.alexy= kot.me [10]=C2=A0-p 18353=C2=A0testnet-seed.alexykot.me
[11]=E2=80=8B

=E2=80=8Bare giving different authority sections.

Hmm, but if I setup custom SOA record for it - it should work,
right?=C2=A0
=C2=A0What SOA name should it be actually, assuming that NS record for
testnet-seed.= alexykot.me [12] is pointing at alexykot.me [13]?

Best regards,=C2=A0

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-s= eed.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
=C2=A0dig @node.alexy= kot.me [3] [8] testnet-seed.alexykot.me [4] [9]

=C2=A0dig @node.alexy= kot.me [5] [10] bitcoin-seed.alexykot.me [6]
[11]

=E2=80=8BBut when I try nslookup testnet-seed.alexykot.me [7] [12]=E2=80=8B -

it
fails.=C2=A0
I guess the problem is in my DNS settings but I cant figure out
what
is it.

=E2=80=8BS o could you share
=E2=80=8Bhow you configured=C2=A0DNS
=C2=A0=E2=80=8B for your seed
=E2=80=8B to help me debug
=C2=A0=E2=80=8Bmine
?=C2=A0

Best regards,=C2=A0

Alex Kotenko

=E2=80=8B


Links:
------
[1] http://te= stnet-seed.alexykot.me
[2] http://bi= tcoin-seed.alexykot.me
[3] http://node.alexy= kot.me
[4] http://te= stnet-seed.alexykot.me
[5] http://node.alexy= kot.me
[6] http://bi= tcoin-seed.alexykot.me
[7] http://te= stnet-seed.alexykot.me
[8] http://node.alex= ykot.me/
[9] http://t= estnet-seed.alexykot.me/
[10] http://node.ale= xykot.me/
[11] http://= testnet-seed.alexykot.me/
[12] http://t= estnet-seed.alexykot.me
[13] http://alexykot.me
[14] mailto:robert@mc= kay.com


--001a11c2cb12b6d3ff04fac34eaa--