WikiLeaks.org domain killed

reply to post by XPLodER


I was wondering when this would happen ...

sh-3.2# dig __._

; DiG 9.4.3-P3 __._
;; global options: printcmd
;; Got answer:
;; ->>HEADER

Cached here

webcache.googleusercontent.com...:cablegate....__._/cable/1979/08/79TEHRAN8980.html

Why does it say TEHRAN?? Any body know?

Edit to Add: nevermind ..this stoped also...sorry

lets follow each other into the dark.. "No that is not my heart."

The good intention.. Ended up bending, beyond the backs of men.. Since it is us that want what we can never have..



when you let it go.. It..
Crumbles in your hands.. It didn't end the way he meant...

lessened learned for some.. And for others its the end of the meant..

Originally posted by Joehio
Doesn't it make you feel better? The pigs have won tonight. They can all sleep soundly. And everything is all right.

We're pretty much approaching the time to cut their throats and bleed them to death so we can finally have a roast.

A roast of justice.


They should have put all the info on torrents all over the net instead of releasing a few dozens documents per day.

I'm curious aswell.

Heres what it says exactly.

cablegate. wikileaks. org/ cable/ 1979/ 08/ 79TEHRAN8980. html

reply to post by davespanners


thanks for the explination
i woundered how a dns server could be overloaded by handing out dns records
but i guess if enough volume happens the server will be overloaded and unable to reply to new record requests

so these botneting idiots are attacking huh
wounder if they can be prosicuted for ddos attacks

go wiki

xp thanks dave

reply to post by INEDI


Oh, I bet it is the tag for either the first or last cable in the cache.
Just a guess.
But better get them while you can...If you want them.

reply to post by Zeptepi


can you relink the cashed info the links not workin for ma
xp

reply to post by davespanners

Most of the big ISP's provide cached DNS services rather than recursively querying from the root block. It looks like the records were pulled for good. As a simple test I queried against the open Verizon DNS servers (dig @4.2.2.1 __._) ... same thing.

reply to post by NewWorldDisorder


Or it just takes one person with XERXES.
Jester has been claiming that he's responsible and if you look at timing and tweets, he probably was at least for some of it.
Of course when I tried to mention this days ago I got accused of spouting garbage and told to shut up.
www.infosecisland.com...

unfortunately for the world goobermints they can never stop the flow of information. too many options.

one goes down, 1000 goes up. they created the web and their treachery. now they can eat shhhht and enjoy it

reply to post by XPLodER


Sorry ...It is now dead also

reply to post by Xtraeme


my countrys dns server information
is coming back cant resolve
interesting that untill wiki threatened to release bank emails
they still had mx dns rev look up
now looks like this is more than ddos
although might have a hardware ddos disconnect unit
how long can the bot netters keep up an attack?
xp

reply to post by hadriana


any more info on this jester
guy
just asking
xp

The goverment is trying to shut down from this video proof I got from this site Link to video click here but it wont be completely shut down.

reply to post by XPLodER

The way it looks at the moment this isn't just a DDOS. The A pointer records were purged and have apparently propagated to other cached DNS boxes (that usually takes a day or so). It's not like Wikileaks was using something cheap and mutable like DynDNS.

IDK if anyone has downloaded this yet but It's ALWAYS a good idea to have insurance!!
twitter.com...

46.59.1.2...

This link is up for me.

reply to post by Xtraeme


so 24 -36 hours to propagate
worldwide
does anyone know if wiki has
a back up dns server (private)
if so dont post it here
message me
xp

reply to post by hadriana


thats just the main site
the cables site is still offline
xp