![]() | This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||
|
Wiki Education Foundation-supported course assignment
editThis article was the subject of a Wiki Education Foundation-supported course assignment, between 26 May 2020 and 3 July 2020. Further details are available on the course page. Student editor(s): Junwei Sheng.
Above undated message substituted from Template:Dashboard.wikiedu.org assignment by PrimeBOT (talk) 18:57, 16 January 2022 (UTC)
DNS Spoofing is not necessarily evil
editThe very first sentence of the article defines DNS Spoofing as a "computer hacking attack". This is not necessarily the case, as users may well want DNS results to be modified by a trusted firewall in order to protect their machines from malicious content. NAT32_Support (talk) 02:34, 7 August 2015 (UTC)
- Have you a reference we can cite? VisSci (talk) 14:30, 13 April 2016 (UTC)
Not Clear
editThe explanation about the poisoning techniques is not clear. Splendour 07:02, 28 June 2006 (UTC)
An example would help greatly. Nikle-on-wikipedia 17:59, 29 December 2006 (UTC)
Invalid Information
editUnder prevention and mitigation it is stated that end-to-end validation can be performed once a connection is setup. This isn't entirely true because DNS uses UDP for many of its queries which is a connectionless protocol there is no transport layer connection set up. However, public/private key transaction signatures can be used to validate queries.
Responding before the real nameserver
editReference to "birthday attack" was removed. A birthday attack applies to a situation where you try something n times and the number of opportunities for success is proportional to n^2 (typically because there is an opportunity for success for each pair of things you try). In this case the number of opportunities for success (fooling the target DNS into believing your answer is the right one) is simply proportional to n (the number of spoof replies you send to it). —Preceding unsigned comment added by 89.241.154.128 (talk) 10:01, 30 July 2008 (UTC)
- This isn't quite correct. Some DNS cache poisoning attacks do use the birthday paradox effect. They send out n requests at the same time along with n spoofed replies. Since the replies are all received at around the same time, you get the n^2 factor increase in success. Wrs1864 (talk) 16:49, 12 September 2008 (UTC)
External links
editI took the liberty of nuking the external links that have been an eyesore for over a year. Some appear to be good reference candidates, so I'm leaving them here. If you use one as a reference (or find one to be useless spammery), please delete it from this post. Krushia (talk) 01:17, 8 February 2013 (UTC)
- BIND 9 DNS Cache Poisoning - Discovered by Amit Klein (Trusteer)
- Predictable transaction IDs in Microsoft DNS server allow cache poisoning
- Microsoft Knowledge Base: How to prevent DNS cache pollution
- SANS DNS cache poisoning update
- DNS Threats & Weaknesses: research and presentations
- Blocking Unwanted Domain Names Creative Usage of the Hosts File
- Dnsstuff.com's DNS Vulnerability Check Test to see if you are Vulnerable
- Steve Gibson of GRC's ISP DNS testing tool Check your ISP's DNS resolvers for vulnerabilities
- Security-Database Tools Watch PorkBind Scanner for 13 DNS Flaws including the DNS Poisoning
- Movie explaining DNS Cache Poisioning
- An Illustrated Guide to the Kaminsky DNS Vulnerability
- US CERT advisory : Multiple DNS implementations vulnerable to cache poisoning
- Secret Geek A-Team Hacks Back, Defends Worldwide Web An article about defending against DNS poisoning
- Brazil ISP servers under Massive DNS cache Poisoning attack
Variants topic
editCan anyone explain why there is a [citation needed] template against These attacks assume that the nameserver for target.example is ns.target.example, which appears simply to be preamble for the examples which follow? VisSci (talk) 12:38, 11 April 2016 (UTC)
- I'm removing it now (albeit 8 years later). You were correct Jtbwikiman (talk) 21:26, 18 July 2024 (UTC)
Domain name spoofing
editFYI, I have created a disambiguation article Domain name spoofing since this is a generic term in common use. At present it contains IDN homograph attack, DNS spoofing and Email spoofing, as well as a see also of mitigation technologies. Please add any relevant articles. --John Maynard Friedman (talk) 18:19, 6 July 2021 (UTC)
- It may be worth noting that your link now points to "Domain Name"... Jtbwikiman (talk) 21:30, 18 July 2024 (UTC)
- Thanks. Further discussion concluded that
the material in this article is better located in the main article and this one changed to redirect there
, which I did. So yes, it now redirects to Domain name#Domain name spoofing. --𝕁𝕄𝔽 (talk) 21:56, 18 July 2024 (UTC)
- Thanks. Further discussion concluded that
DNS race attacks
editIn the "Prevention and Mitigation" section, someone has referred to DNS Spoofing as "DNS Race Attacks". I'm not enough of an expert to make this change, but here's what I propose:
If DNS Race Attack is a legitimate alternate name, then let's add a redirect and modify the article to note this. If instead DNS Race Attack is a different thing from DNS Spoofing, we need to change this text. Jtbwikiman (talk) 21:29, 18 July 2024 (UTC)