From: Robert McKay <robert@mckay•com>
To: Alex Kotenko <alexykot@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
Andreas Schildbach <andreas@schildbach•de>
Subject: Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again
Date: Fri, 30 May 2014 15:51:58 +0100 [thread overview]
Message-ID: <48331d04b68b3d6554b4e59e97ffbafe@webmail.mckay.com> (raw)
In-Reply-To: <CALDj+BZSYojZ1kQqb_5zrpjc=5E94bbZ7a0PG4bkZx38J0zHWQ@mail.gmail.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-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
next prev parent reply other threads:[~2014-05-30 14:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 22:17 Peter Todd
2014-05-25 19:12 ` Andreas Schildbach
2014-05-25 20:02 ` Tim
2014-05-26 16:37 ` Peter Todd
2014-05-26 22:12 ` Andreas Schildbach
2014-05-26 22:39 ` Peter Todd
2014-05-26 23:19 ` Andreas Schildbach
2014-05-30 9:43 ` Peter Todd
2014-05-30 13:19 ` Alex Kotenko
2014-05-30 13:41 ` Robert McKay
2014-05-30 14:13 ` Alex Kotenko
2014-05-30 14:51 ` Robert McKay [this message]
2014-05-30 15:24 ` Pieter Wuille
2014-05-30 15:40 ` Andreas Schildbach
2014-05-30 15:54 ` Robert McKay
2014-05-30 15:59 ` Pieter Wuille
2014-05-30 16:03 ` Gregory Maxwell
2014-06-01 9:56 ` Alex Kotenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48331d04b68b3d6554b4e59e97ffbafe@webmail.mckay.com \
--to=robert@mckay$(echo .)com \
--cc=alexykot@gmail$(echo .)com \
--cc=andreas@schildbach$(echo .)de \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox