* in the tracker name with nyaa.eu torrents

Well, first of all I've encountered this issue with 3.3 alpha. Not sure if it's just alpha, maybe something more.

On nyaa.eu every single torrent has * before the tracker name (in the client of course), so tracker url is invalid all the time. No, I can't remove it (it comes back) and different torrent editing tools show that there is no * there. It shows just after I add the torrent, in the Advanced menu and also can be seen the usual way.

Strangely, I installed new 3.4 and 3.3 on another system with default settings - no * in the name.

I just don't know what causes it (I have too many settings changed), haven't tested stable builds yet.. But with default setting everything is fine. Even more strange, it's like this in every single torrent from nyaa, even in those added more than a year ago and at that time I used 2.x.

It looks like *http://open.nyaatorrents.info:6544/announce

Anyone with the same issue? Thanks for any info.

P.S And I was curious why my speed from nyaa is so slow..

P.S It looks more like banning of a tracker inside the program itself. I suspect there are more trackers like this. Maybe tpb is among them.

did you purge your settings.dat in the offending client yet?

Yes I did. It works fine with default settings, but after I change something (I have no idea what exactly) it becomes like this.

And it seems I was right. Veeery old torrents in my list with old tpb trackers also have * before the name. Could it be internal tracker ban?

__

Wow it's wierder that I expected. After I deleted the settings file it looked like it was fine, but after I deleted * it came back, but not instantly, but with a slight delay.

I just don't know what to think anymore.

__

I have three explanations as for now.

1. It's a feature which prevents users from pirating

2. It's a bug

3. It's another feature which adds * to every tracker name which is invalid by itself

Just checked up 3.2.1 and..guess what? No * anywhere.

So I guess I should report it in 3.3 and 3.4 threads..

I can clear this up. It's intentional and it's due to open.nyaatorrents.info's DNS records:

MacBook-Pro:~ cbrown$ nslookup -q=txt open.nyaatorrents.info
Server:		10.10.11.29
Address:	10.10.11.29#53

Non-authoritative answer:
open.nyaatorrents.info	text = "BITTORRENT" "UDP:6544" "TCP:6544"

Authoritative answers can be found from:
info	nameserver = b0.info.afilias-nst.org.
info	nameserver = b2.info.afilias-nst.org.
info	nameserver = a0.info.afilias-nst.info.
info	nameserver = d0.info.afilias-nst.org.
info	nameserver = a2.info.afilias-nst.info.
info	nameserver = c0.info.afilias-nst.info.

I'm guessing the sysadmin there either misinterpreted something in BEP 34 or misconfigured the records.

What the response should look like is this (everything in one entry, separated only by spaces):

Non-authoritative answer:
open.nyaatorrents.info	text = "BITTORRENT UDP:6544 TCP:6544"

You should probably alert them of this.

For now you can actually disable this functionality through the advanced settings. The setting is called "use_dns_tracker_prefs".

A better way to indicate that a URL has been banned by the host is probably in order.

Thanks for clearing this up, I will try to contact them.

So 3.2.1 doesn't have this dns feature? I can't find this option there.

__

I've posted this on their forum, but the topic was deleted. Well..at least I've tried.

It's pretty new and intended to prevent DDoS.

You mean making dns server respond with an error? Or adding * before the name?

Looks like I've dug up something unexpectedly big..

The DNS text record functionality is used to determine if a tracker is really a tracker and the preferred method and address for connecting. A site for example could specify that they do not have a tracker.

It does look like they wrote a bad txt record however, based on a glance at that BEP.

Judging by the fact that they deleted my thread, it's either intended or they just don't want to fix it.

Or maybe there is another way of reporting bugs to them, but there are no contact forms, only forum which is almost empty and dead and seems to be supervised by the admin, who deletes everything except a couple of old threads.

Well if they don't want to accept the existance of a bug, let them learn on their own errors, when 3.3 becomes stable and users will start complaining.

Actually, I think they saw your post and silently fixed it before deleting your thread:

MacBook-Pro:~ cbrown$ nslookup -q=txt open.nyaatorrents.info
Server:		10.10.11.29
Address:	10.10.11.29#53

Non-authoritative answer:
open.nyaatorrents.info	text = "BITTORRENT UDP:6544 TCP:6544"

Authoritative answers can be found from:
info	nameserver = b0.info.afilias-nst.org.
info	nameserver = a2.info.afilias-nst.info.
info	nameserver = d0.info.afilias-nst.org.
info	nameserver = b2.info.afilias-nst.org.
info	nameserver = c0.info.afilias-nst.info.
info	nameserver = a0.info.afilias-nst.info.

Does it work properly for you now?

Yeah, now it works correctly. Heh, sometimes it feels like you really can make some things better in this world..