Okay thanks for the clarification. That's definitely a DNS resolver problem then. I'm not sure why your resolver doesn't like animetosho.org though. If you're willing to post the resolver address, I can try running a few queries to see if I can identify anything.
Regardless, try using another resolver like Google DNS or OpenDNS, and see if that helps.
"Wait, so you mean tracing to the IP works even when you're getting the 'unable to resolve' error?" Yep, it may look weird but yes. Tracing using the site did not work but tracing using the IP address works. ^^;;
No configuration done. :)
And I only have problems accessing this site. As for the other sites (google, facebook, manga sites etc), I can access them normally.
Yes, I also got that error message for animetosho.org every time I cannot access the site.
Tracing using both IP addresses work. The values given by >tracert animetosho.org (which I got earlier when I can still access the main site) and tracert 95.215.44.142 are the same.
Wait, so you mean tracing to the IP works even when you're getting the 'unable to resolve' error?
I am not sure what necessary information will I give (without compromising privacy
It's unlikely that the DNS server will reveal anything about you, but if you're worried, just post the first two numbers (there should be four, separated by dots for each IP). But if you've never configured it yourself, my guess is that it's probably pointing to your router (usually a 192.168.x.x address), which probably passes it on to your ISP's resolver.
If my assumptions are correct, I think your issue may be related to your ISP's DNS resolver acting intermittently. Do you get similar issues to any other website? Perhaps you can try using Google's Public DNS resolver to see if things work better: https://developers.google.com/speed/pu...docs/using
Yes, I also got that error message for animetosho.org every time I cannot access the site. As for the DNS server, I am kind of noob when it comes to networking stuff so I am not sure what necessary information will I give (without compromising privacy ... ^^;;;) but I can see a value under DNS Server thingy when I entered "ipconfig /all".
Tracing using both IP addresses work. The values given by >tracert animetosho.org (which I got earlier when I can still access the main site) and tracert 95.215.44.142 are the same.
Unable to resolve target system name mirror.animetosho.org.
Do you get that error for animetosho.org as well? Do you happen to know what DNS resolver/server you're using? You may be able to find it using the command ipconfig /all (look for the line "DNS Servers" on your network adapter)
When you're unable to access this site, does tracing the IP directly work? You can use the following commands to test: tracert 95.215.44.142 tracert 23.226.143.217
Unfortunately, the problem is still occurring on my side. It took a lot of reloads before I manage to enter this site. ^^;; In fact, this is already a lucky case for me to access this site during this time because in the past 2-3 weeks, around this time, I cannot enter the site at all. ^^;;
Also, at this time, I cannot access the mirror site as well without using a proxy. >tracert mirror.animetosho.org Unable to resolve target system name mirror.animetosho.org.
* Note: This was also the error message I received when I initially accessed animetosho.org.
FYI, I was able to access the site normally during the time when some did not able to access the site for 3-4 days. If there were problems, it was just minor ... I guess?
Oh I see. :) So far I can access the mirror site so it's good. I'll just leave a comment in case #1 and #2 are not working for me (and miracles happen to access this page. xD).
Yours is the second case I've heard of recently. A few suggestions when you can't get thru:
1. go to the AT mirror site, if you can: https://mirror.animetosho.org/ . Leave a note if you can't get there either. 2. See if you can get here via a proxy. Here's a proxy that I've used recently https://1freeproxyserver.com/ 3. Run a tracert (command prompt/dos box) and see what you see, or report it here. For privacy, don't include the hops close to home.
admin provided some more detailed tests a few pages back in feedback when other people had similar problems
Recently, I am having problems accessing this site. Something like it "cannot connect to the server" and the site fails to load no matter how many times I reload it. And it happens during weekends. It also occurs in weekdays but less frequent.
I wonder if anyone experiences this problem as well. Before (until around start of February I think?), I do not have these problems. ^^;;
Can someone help with these 2 torrents? I cant find them here, and they already exist on TT so I can't put them there to be fetched by the AT bot, and I can't connect to any seeds on them (if there are any).
"I hereby grant my soul, monies, personal belongings, ideas, services, children and goldfish to the site owner. Either that, or I promise to do so sometime in the future."
erm....I don't have goldfish, but would you accept something of equivalent exchange? Like my piranhas!!
Jheberg doesn't use an account on turbobit so files only last for 7 days. It looks like multiup uploads using their own account so files stay online for a max of 45 days if not caught. Hopefully that will be long enough of a time frame for you.
It'd be helpful (thanks for the offer), though it's still probably nice to have something in the AT script in case anyone else does the same.
In essence, they'd just need to maintain the same info hash value across their torrents. One could do this by creating the torrents in the same application, or just using a .torrent file editor to edit the trackers (which should be faster as it doesn't need to rehash the content).
Unfortunately, SallySubs' submissions use completely different piece sizes (and hence BTIH) and arrangements (it looks like they're created with different applications), so not just the tracker is different. As far as BitTorrent is concerned, torrents with different BTIH's are completely different, and the deduplication strategy here is based off that. This means that even if you add trackers to your torrent manually, you can't see peers that the other torrent file has.
(torrents can have different trackers and maintain the same BTIH)
I may try to invent some heuristic to deal with this, possibly only apply it to SallySubs. It's not exactly a trivial problem to solve though. Thanks for pointing it out nonetheless.
Comment in Feedback 24/02/2015 19:00 — Anonymous: "Anonymouse&cat"
I noticed some torrents get added twice, like "[SallySubs] Ryuugajou Nanana no Maizoukin - Vol.05". I think the first set is from a tracker and the second do another. If there's a duplicate check in place, since the 2 .torrent are different they will appear as different despite having the same content. Probably it's nyaa "fault" (they edit the traker in the torrent), but it's a waste of space and time. Now, your choice to fix or not. ;)
"watakushi.pw" is the website info they put in their Nyaa listings, for whatever reason. AT just extracts the info they provide, so they'll need to make those changes.
When clicking website for watakushi releases it redirects to watakushi.pw instead of watakushi-fansub.blogspot.com.Just wanted to report even if it is a very minor bug.
I don't know how or where do I say it, but I'd like to thank the admins for keeping the constant updates and the great work up to date, I left the site for few weeks and I really had fun rolling over 15 pages to cover what I missed :)
Oh I see what you mean. Yeah, that was removed since it was highly inaccurate relatively often. It may be brought back later if I can get it to be more reliable. No worries though, thanks for bringing it up.
Haha lol. There used to be a group name mentioned in each listing, like HorribleSubs, or FFF, guess its not there now. Ignore my message sir. Sorry for the trouble.
No. You can download from Ulozto for free. Look for the yellow button in the middle, fill in the captcha and click "download". (I've got your IRC message)
06/03/2015 22:34 — admin