3 ms·
I think saying "google.ps was hacked" is a perfectly reasonable way to describe what happened.
by baddox 13y ago
I think saying "google.ps was hacked" is a perfectly reasonable way to describe what happened.
- UVB-76 13y agoThat implies the site itself was hacked, when it was not. It appears the .ps domain registry was hacked.
- reflectiv 13y agoI don't agree at all, the system which was hacked is not in Google's control at all, even though it does depend on it for DNS SOA. Every site depends on root DNS servers to do their job right...the root for .ps was hacked...that's what happened here...google was affected, but not hacked.
- dsl 13y agoYou are using these words, but I don't think you know what they mean. The SOA record is almost irrelevant in this case, unless you are seeing some trickery where they set high TTLs or something to keep the "hack" around longer after it has been corrected. There is only one root (which is kinda what makes it a root) - and in this case the root servers are doing their job just fine. DNS is hardly even involved. As far as I can tell this was simply a compromise of the web UI that allows for the management of domains under the .ps ccTLD. Probably just another sloppy front end developer.
- reflectiv 13y agoForgive me, it has been several years since I dealt with DNS authority, however it still does not change the argument that it was not google who was 'hacked'...the title of this post is just blatantly wrong.