DNS is a key element of the Internet and, regularly, we read new bad stories. One of the last one was the&#;x26;#;xc2;&#;x26;#;xa0;Department of Homeland Security&#;x26;#;xc2;&#;x26;#;xa0;warning&#;x26;#;x5b;1&#;x26;#;x5d;&#;x26;#;xc2;&#;x26;#;xa0;&#;x26;#;xc2;&#;x26;#;xa0;about recent DNS hijacking attacks&#;x26;#;x5b;2&#;x26;#;x5d;. Indeed, when you want to visit the website &#;x26;#;39;isc.sans.org&#;x26;#;39;, you must be sure that the visited server will be 204.51.94.153 and not a malicious one controlled by a malicious&#;x26;#;xc2;&#;x26;#;xa0;server. From an end-user point of view, we have to rely on the DNS.&#;x26;#;xc2;&#;x26;#;xa0;it’s not easy to&#;x26;#;xc2;&#;x26;#;xa0;detect unexpected changes but you can implement your own checks to tracks changes for your most visited websites. But from a website owner or network admin perspective, it is indeed a good practice to ensure that DNS servers authoritative for our domain zones are providing the correct information.&#;x26;#;xc2;&#;x26;#;xa0;At the Internet Storm Center, we must be sure that any request to resolve&#;x26;#;xc2;&#;x26;#;xa0;&#;x26;#;39;isc.sans.org&#;x26;#;39; will always return the right IP address!&#;x26;#;xc2;&#;x26;#;xa0;
Continue reading Tracking Unexpected DNS Changes, (Thu, Jan 31st)→