Geek Answers Handbook

DNS redirects tracker.thepiratebay.org to 127.0.0.1

I tried ping "tracker.thepiratebay.org" and for some reason, DNS returns 127.0.0.1 I get 0% packet loss, but obviously it doesn’t fit the correct website.

My college uses a local DNS server, but I don’t think there is a problem, because I asked a friend outside my college and he reported the same results.

Can anyone confirm this result? And if so, is there a reason? Also, can I somehow access the real website? (So, someone who can give me an ip site will be appreciated)

(Btw, "http://tracker.thepiratebay.org/announce" is one of the standard trackers used by torrents downloaded from The Pirate Bay.)

EDIT: I tried using google search instead of my own, and that also returns 127.0.0.1 Can there be a possible explanation that the site no longer exists? or will not exist, return some other identifiable result?

+8
dns hosts
source share
3 answers

From Wikipedia:

 The Pirate Bay used to run a tracker, but has since disabled it, although the website remains as a torrent index.

Also a quick nslookup tracker.thepiratebay.org confirms your problem.

+4
source share

Yes.

This is as simple as making whois on thepiratebay.org , and you will get a list of name servers registered for the domain (excerpt):

Name Server: NS0.THEPIRATEBAY.ORG
Name Server: NS1.THEPIRATEBAY.ORG
Name Server: NS2.THEPIRATEBAY.ORG
Name Server: NS3.THEPIRATEBAY.ORG
Name Server: NS4.THEPIRATEBAY.ORG

Request one of the responsible name servers to verify that this is not a bad configuration on your local computer or your DNS.
192.121.86.162 is the IP ns0.thepiratebay.org :

 dig @192.121.86.162 tracker.thepiratebay.org

@ indicates that dig should make a direct request to a specific server. This can be blocked, so it may not be absolutely 100% reliable, but in any case:

 ;  > DiG 9.6-ESV-R4> @ 192.121.86.162 tracker.thepiratebay.org
 ;  (1 server found)
 ;;  global options: + cmd
 ;;  Got answer:
 ;;  - >> HEADER ;;  QUESTION SECTION:
 ; tracker.thepiratebay.org.  In a

 ;;  ANSWER SECTION:
 tracker.thepiratebay.org.  3600 IN A 127.0.0.1

 ;;  AUTHORITY SECTION:
 thepiratebay.org.  86400 IN NS ns0.thepiratebay.org.
 thepiratebay.org.  86400 IN NS ns1.thepiratebay.org.
 thepiratebay.org.  86400 IN NS ns2.thepiratebay.org.
 thepiratebay.org.  86400 IN NS ns3.thepiratebay.org.
 thepiratebay.org.  86400 IN NS ns4.thepiratebay.org.

 ;;  ADDITIONAL SECTION:
 ns0.thepiratebay.org.  86400 IN A 192.121.86.162
 ns1.thepiratebay.org.  86400 IN A 109.201.134.21
 ns2.thepiratebay.org.  86400 IN A 109.201.131.4
 ns3.thepiratebay.org.  86400 IN A 217.75.120.120
 ns4.thepiratebay.org.  86400 IN A 194.71.107.1

 ;;  Query time: 14 msec
 ;;  SERVER: 192.121.86.162 # 53 (192.121.86.162)
 ;;  WHEN: Tue Jan 24 21:00:34 2012
 ;;  MSG SIZE rcvd: 228

The important part is

 tracker.thepiratebay.org. 3600 IN A 127.0.0.1
+3
source share

Run nslookup and see which server returns the address 127.0.0.1. On Windows, you do this by running nslookup tracker.thepiratebay.org from the command line.

The address 127.0.0.1 is also known as the loopback address, however you allow tracker.thepiratebay.org allow the loopback address, so you cannot easily reach it. A response from nslookup will tell you exactly who is blocking it.

0
source share

More articles:


All Articles