Why does no one ever hack a DNS server? It seems a lot of people would be interested in hacking one so they could point google.com to their own malicious domain. Sure, it might be fixed within minutes but given the popularity of google.com you could still infect millions of computers.
>>58492279
Most hackers are kind of good at PCs but still too pleb to do anything too serious or cause massive damage, maybe they could send a fork bomb to people though.
>>58492279
>Why does no one ever hack a DNS server?
How would they?
>>58492793
DDOS the DNS. Makes sense to me.
>>58492279
>Why doesn't everyone do it?
Because it's really, really, really fucking hard, if not impossible. The DNS root servers are what make the World Wide Web work, and they're locked up tighter than your mom's vag.
>>58492793
poison the cache entries
DNS software is usually simple and mature enough to be quite secure.
>>58492279
didn't they ddos dns servers to take down twitter and other sites for a few hours
>>58492807
What do you think the Mirai botnet did? And why do you think it was such a big deal?
How has no one in this thread mentioned DNS amplification attacks?
/g/ is so clueless it hurts
>>58492812
You obviously don't know OP's mom
>>58492893
Because it has nothing to do with the subject of the thread probably
>>58492893
DNS amplification attacks are a form of DDoS
DDoS has already been mentioned in this thread. Learn to read kid
>>58492812
>locked up tighter than your mom's vag.
A Windows XP machine would fit that description
>>58492807
Already happened.
>>58492279
>so they could point google.com to their own malicious domain
You'd have to obtain a new valid certificate/the private keys for google.com or most of users will only see an error page in their chrome and complain about it on facebook.
>>58495347
Not if your own, malicious page doesn't implement SSL
>>58495347
>use your own certificate
>tech illiterate people get some warning they don't read or understand anyway
>click accept
>>58492279
>DNS Server
>Domain Name Server Server
>>58498252
You run the Domain Name Server on a server...
>>58498252
It's Domain Name System
>>58498367
Reminds me of people thinking DVD means "Digital Video Disc"
>>58498367
This
>>58492279
when u say it like this it looks easy, noobs might mistake u that u think about only 1 computer out there
its is a farm of servers and it can get pretty big if u look at root name servers, also there was attack in 2015 on root name servers - 5 million queries per second each, they didnt even lag
>>58492279
it already happened retard
>>58492279
>so they could point google.com to their own malicious domain. Sure, it might be fixed within minutes but given the popularity of google.com you could still infect millions of computers.
What is HSTS?
>>58501657
I don't know. What's HSTS?
>>58492279
Cuz its very hard to do that. Is more easy find a backdoor or a bug in a router or popular device (IoT) and explit that, if the device is a router you just change the dns from there. You can scalate that atack to an entire county or at least a lot of people get affected. And basically u can redirect the traffic wherever you want. Of course you need to manage all the request that your fake dns receive and serve the pages....not easy at all but not impossible