If you are reading this page, then you probably know that Indymedia is down due to the
primary nameservers being changed from NS2.RISEUP.NET and NS.LACKOF.ORG
to NS1.BADWHOISSHUTDOWN.COM and NS2.BADWHOISSHUTDOWN.COM. People
are presently investigating this change, however it is probably related to an ICANN whois data
"inaccuracy" report (which, unfortunately, is a known tool that trolls have successfully used in the past
to get sites they don't like taken down).
This page will be updated when more information becomes available.
This section hopes to provide informative instructions on how to recover the indymedia.org
zone while this mess gets sorted out.
If you run your own nameserver like BIND, then it is very easy. Just add the following to your
named.conf:
zone "indymedia.org" {
type forward;
forwarders {
// ns2.riseup.net, ns.lackof.org
204.13.164.8; 204.13.164.202;
};
};
Save the config file and restart BIND. Provided that you are resolving your DNS through this BIND
instance, indymedia.org should now be available to you. You may need to flush your DNS cache if your
operating system has one. For example, on Windows, this can be done by doing ipconfig /flushdns
in a Command Prompt.
If you run your own Unbound resolver, then it is very easy. Just add the following to your
/etc/unbound/unbound.conf:
forward-zone: name: "indymedia.org" # ns2.riseup.net forward-addr: 204.13.164.8 # ns.lackof.org forward-addr: 204.13.164.202
Save the config file and restart Unbound. Provided that you are resolving your DNS through this Unbound
instance, indymedia.org should now be available to you. You may need to flush your DNS cache if your
operating system has one. For example, on Windows, this can be done by doing ipconfig /flushdns
in a Command Prompt.
It has been reported that OpenDNS is working at present. This is probably because the DNS cache has not yet expired. To enable your computer for OpenDNS, go to the OpenDNS website, which has useful instructions for setting up your computer to use their nameservers.
You can also add the IPs for nameservers to your DNS server list, which are 204.13.164.8, and
204.13.164.202. This should work on most platforms without causing problems.
(note: In Windows, to add more than 2 nameservers, the options to do so are under your Network Adapter's
"TCP/IP advanced settings.")
On the imc-tech-emerg list. We are also
discussing the issue on IRC in #tech.
/server 209.51.169.94 6667 for non-SSL, and /server 209.51.169.94 +6697 for SSL.
Most clients support SSL in the format previously mentioned and SSL is recommended when connecting to the IRC server.
The webchat interface is available, but you will need to accept the SSL certificate.
Refer people to this page if they ask why Indymedia is down.
Whatever you do, please avoid doing anything involving Dotster. Right now doing anything that could be construed as harmful or illegal towards Dotster is probably counter-productive, as amongst other reasons, there may be legal efforts involved to recover the domain name from them, so as a result we really don't particularly want to be doing anything that would jeopardize the situation. People are already reportedly in communication with Dotster about this problem.
Mention the change on #tech on the IRC server and I will try to update it as soon as I notice it.
Prefixing your message with "nenolod:" will get my attention more quickly.