One Article Review
| Source |  AlienVault Blog |
|---|---|
| Identifiant | 528806 |
| Date de publication | 2018-03-19 13:00:00 (vue: 2018-03-19 13:00:00) |
| Titre | DNS Poisoning and How To Prevent It |
| Texte |
DNS poisoning. Simply the name conjures up the kind of thoughts that keep network admins up at night. What if my RNDC key gets leaked? Could there be a rogue DHCP server within my perimeter? Are the Lizard Squad planning an attack on for Christmas?
Much of what we know now about DNS, address protocol, and packet priority is being redefined with the recent 'Net Neutrality' legislation. Instead of becoming a party to the hoopla that is partisan politics surrounding THAT issue, let me assure you there are many different mitigation strategies for not only securing your own network against DNS poisoning, but also working towards a harmonious kum-by-ah solution that in the end, may end up resolving (pun intended) the DNS plight. So, let's silence the alerting system, and get down to what DNS poisoning is, why it's still around, and one of the best ways to solve it.
Why is DNS Poisoning Possible?
The first thing to understand about DNS 'poisoning' is that the purveyors of the Internet were very much aware of the problem. Essentially, DNS requests are "cached", or stored, into a database which can be queried in almost real-time to point names like 'hotmail.com' or 'google.com' to their appropriate IP addresses. Can you imagine having to remember a string of numbers instead of a fancy name to get to your desired WWW (or GOPHER - if that's your thing) resources? 321.652.77.133 or 266.844.11.66 or even 867.53.0.9 would be very hard to remember. [Note: I have obfuscated REAL IP addresses with very fake ones here. Always trying to stay one step ahead of the AI Armageddon. Real IP addresses end with the numerical value of '255' within each octet.]
No, remembering strings of numbers would be next to impossible. But thankfully, and all because of Al Gore (sarcasm) we have the DNS mechanism that gives us [relatively] easy names to remember how to get to our favorite resources.
DNS basically runs the Internet. Without it, only the most uber-geeky of computer scientists would be able to traverse it. Strings of numbers are just simply not how humans identify information. They help, but in reality, words and language are what separate us from our impending robotic overlords.
It's because of this, that as the Internet began to grow, the DNS (Domain Name System) was created. To help us get from one side of the world to the other, with little angst. However, due to the limitations of computing (especially storage and bandwidth) at the time, the early versions of DNS simply used a "distributed" text file for name resolution. Think "blockchain" for EVERY SINGLE HOST that existed on the 'Net back then. It was a nicer and friendlier place, and that system worked well. Until it didn't, and some nice folks at ARIN and ICANN came along and began the system we use today: DNS.
In its simplest explanation, DNS takes a name (e.g. yahoo.com) and looks at the locally configured 'Nameservers' for the "answer" to the question: 'What is the IP address of yahoo.com?'. Once an answer is found, it is passed back to the client requesting it, and the routing and magic of the TCP protocol kicks into gear, and the peasants rejoice. Except there are sometimes problems that arise that cause the peasants to NOT rejoice, and for network engineers to curse the vile notion of DNS. You see, since DNS arose during a time where "real-time" anything was not technically possible; to aid performance and allow for USABLE networks, DNS answers were logged into a locally stored 'cache' or database o |
| Envoyé | Oui |
| Condensat | 'close 'root there *all* @acuralegend accessed acuralegend@gmail admin allowed also always answer any are attack become better bit block boring business but cache came can case check clearer clients cluster com commonly compromised computing connected consider consuming control core costs could covered create creating critical database dhcp different disable dns does doesn't domains don't down duration easily email: embrace end especially even except family feel file find finite firewall flaws forward forwarders free frequently from frustrating functioning going having here hosted hot how i've i/o ideal impact important increase incredibly infrastructure inherit internet isp issues it's its just keys landscape latency lazy learn level like likely local localized longer lose low maintain make many matter mention minutes more much must network not notice often once one only option other over own people performance permeate poison poisoned poisoning poor port practices present prevent problem professional proper properly protocols providing ptr reach real really requests resolution resources results revolve rndc rogue routing sacrifice security see server servers servers' set short shorter should simply smtp some something spot structure stub surface surprised table talk technical tedious ter testing than them those time time' too tracking traffic ttl's twitter use users using value values verified very wan way well when which will within works world your zones |
| Tags | Guideline |
| Stories | Yahoo Uber |
| Notes | |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.