* Agenda What is the DNS ? Poisoning the cache Short term solution Long term solution
* a hierarchical naming system built on a distributed database for computers, services, or any resource connected to the Internet or a private network
* Zone * Nameserver * Authoritative Nameserver * Resolver * Recursive Nameserver * Resource Record * Delegation
A simple DNS query
What's in a DNS packet?
The packet in the step 7
What's in the cache?
* Step 1: * Guessing the Query ID and Port Number * Step 2: * Flooding the target nameserver
* Version 1
* Version 2
* Maximise the amount of randomness randomizing the Port Number and Query ID Even patched servers may still be vulnerable if an intervening firewall performs Port Address Translation in a way that un-randomizes the source ports * Disable open recusive name servers If you must run a recursive name server, limit access to only those computers that need it. (e.g. your customers)
DNSSEC is the current answer to this problem