Discuss mailing list

[Evaggelos Balaskas <Evaggelos AT Balaskas.gr>]

seems weird, cause

# dig any +trace torrentz.eu @87.98.175.85

returns results without any problem,

...
torrentz.eu.            600     IN      A       185.87.146.4
torrentz.eu.            600     IN      A       185.87.146.3
torrentz.eu.            86400   IN      SOA     name1.torrentz.eu. 
root.torrentz.eu.
2015031602 7200 3600 1209600 3600
torrentz.eu.            86400   IN      NS      name3.torrentz.eu.
torrentz.eu.            86400   IN      NS      name4.torrentz.eu.
torrentz.eu.            86400   IN      NS      name1.torrentz.eu.
torrentz.eu.            86400   IN      NS      name2.torrentz.eu.
torrentz.eu.            86400   IN      MX      1 cnnt.pl.
torrentz.eu.            86400   IN      TXT     "v=spf1 mx -all"

;; Received from 185.87.146.2#53(name3.torrentz.eu)


but indeed this:
# dig a +short torrentz.eu @87.98.175.85

does not return anything !


On 11/11/2015 09:23 μμ, Hopping Harry wrote:
> A site which is currently up and running is not being resolved by several
> OpenNIC DNS servers.
> 
> The site in question:
> 
> torrentz.eu
> 
> A few examples of OpenNIC DNS servers not resolving it (there are likely
> more):
> 
> 87.98.175.85
> 87.98.242.252
> 5.9.49.12
> 
> It's easy to see that the site is running just fine if you use some other,
> external DNS servers... including good old smelly Google.
> 
> I sincerely hope it's a technical glitch and not deliberate blocking. Having
> people switch from ISP to public DNS servers to access otherwise censored
> content, and find that public DNS is also censoring it, would kind of defeat
> the purpose... :/
> 
> Thank you very much.
> 
> 
> 
> 
> 
> --------
> You are a member of the OpenNIC Discuss list. 
> You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org
> 

-- 
Evaggelos Balaskas - Unix System Engineer
PGP: 0x1c8968af8d2c621f