2010-03-14, 01:26 AM
[20:42:20] <BDRyan> [10:41:13 PM] <TofuYoshi> how exactly was it "attacked"? <-- Massive distributed denial of service (DDoS) attack on the nameservers that are responsible for telling other computers on the internet how to find and connect to the site
[20:42:31] <TofuYoshi> ahh
[20:42:33] <TofuYoshi> DDoS
[20:43:30] <TofuYoshi> the purpose of which being?
[20:43:44] <TofuYoshi> just to screw over others?
[20:44:43] <BDRyan> Pretty much. It's an indirect way of denying service to probably hundreds of sites by preventing the one thing that tells you where those sites are from speaking to your computer about information on the site's location on the net.
[20:53:54] <BDRyan> I'd give an alternate host off my own domains as a temporary measure but that would break the forums since a lot of that stuff does rely on the domain being what's set in settings, etc
[21:00:20] <BDRyan> Because the webserver isn't listening for requests on my domain name. It wants to hear requests for southperry.net
[21:00:53] <BDRyan> Same thing for the IP deal
[21:01:07] <BDRyan> It doesn't want to hear requests for the IP, 'cause it has no idea what you want from it.
[21:02:30] <BDRyan> Here's how this fits in here. With the DNS nameservers that control the records for southperry.net (as well as probably hundreds, if not more, other sites) being under attack, there is literally no way to provide the webserver at that IP the request it wants - DNS is required.
[20:42:31] <TofuYoshi> ahh
[20:42:33] <TofuYoshi> DDoS
[20:43:30] <TofuYoshi> the purpose of which being?
[20:43:44] <TofuYoshi> just to screw over others?
[20:44:43] <BDRyan> Pretty much. It's an indirect way of denying service to probably hundreds of sites by preventing the one thing that tells you where those sites are from speaking to your computer about information on the site's location on the net.
[20:53:54] <BDRyan> I'd give an alternate host off my own domains as a temporary measure but that would break the forums since a lot of that stuff does rely on the domain being what's set in settings, etc
[21:00:20] <BDRyan> Because the webserver isn't listening for requests on my domain name. It wants to hear requests for southperry.net
[21:00:53] <BDRyan> Same thing for the IP deal
[21:01:07] <BDRyan> It doesn't want to hear requests for the IP, 'cause it has no idea what you want from it.
[21:02:30] <BDRyan> Here's how this fits in here. With the DNS nameservers that control the records for southperry.net (as well as probably hundreds, if not more, other sites) being under attack, there is literally no way to provide the webserver at that IP the request it wants - DNS is required.