Hmm, you might be right, as queries
dig @node.alexykot.me testnet-seed.alexykot.me
​and
dig @node.alexykot.me -p 18353 testnet-seed.alexykot.me​

​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 is pointing at alexykot.me?


Best regards,
Alex Kotenko


2014-05-30 14:41 GMT+01:00 Robert McKay <robert@mckay.com>:

> 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. I'm not sure if this can be fixed without hacking the bind src, so
> maybe it wasn't such a great suggestion in the first place. Basically I
> think if bind was returning authorative answers it would work, but I can't
> 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 [6]
>> and bitcoin-seed.alexykot.me [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 [8] testnet-seed.alexykot.me [9]
>>
>>  dig @node.alexykot.me [10] bitcoin-seed.alexykot.me [11]
>>
>> ​But when I try nslookup testnet-seed.alexykot.me [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
>> ​
>>
>