Noob question.
If wikileaks had hosted their own DNS, would it be correct to say that nobody would be have been able to shut down (excluding the DDOS attacks) the wikileaks.org domain name like EveryDNS did?
|
Noob question. If wikileaks had hosted their own DNS, would it be correct to say that nobody would be have been able to shut down (excluding the DDOS attacks) the wikileaks.org domain name like EveryDNS did? | |||
|
feedback
|
See the FAQ for guidance on how to improve it.
|
Not in that way, anyway. EveryDNS shut them down for TOS violations. By self-hosting they couldn't be shut down for DNS TOS violations, though they could be shut down for violating the TOS of the hosting provider. | |||
|
feedback
|
|
The registrar who controls the .com/.net/.org registry can also yank the whole domain name too. | |||
|
feedback
|
|
Not really. The DNS server will have to be in somebody's datacenter and attached to somebody's network. If the authorities asked for the DNS server to be shut down and the admin refused, they would just keep "going up the chain" so to speak until somebody did. They'd ask the datacenter to take it offline, and if they didn't comply they'd get the datacenter's internet provider to shut the whole datacenter off. The datacenter would ordinarily comply, as they have far too much to risk by not taking it offline - they'd probably be liable for hundreds of thousands of pounds in SLA breaches if their entire datacenter was taken offline. | ||||
|
feedback
|
|
Technically by doing this they will eliminate some of the targets i.e. DNS hosting company, however they still have to bass through the Root DNS servers owned and operated by ICANN , as most ISP's get their dns info from the root servers they can "remove" the domain. They could instead switch to an IP address instead of using a domain name or just start another "internet". | |||
|
feedback
|
webmasters.stackexchange.comis probably a better fit. – JP19 Jan 13 '11 at 16:36