Kaminsky suggests long-term fix will still have to be determined, but patch now, or pay soon

TalkBack 2 of 26:

Next »

« Previous

• Thread View
• Flat View

He explained...

He said it was part of the way the protocol works. The way it comes across to me is that, when you respond with a legitimate A record, for say www.google.com, and you include a legitimate NS record, say ns1.google.com, you are now overriding whatever the cache says. That's one of the big problems with things as I see it.

Dan explained it's part of how stuff really works, part of that recursion in DNS. Basically, the DNS server got a valid response from you on www.google.com, why not believe that you also know about ns1.google.com?? And, since the cache nameserver value could have changed, I think this is part of the recursion method that allows systems to stay up to date.

-Nate

Posted by: nmcfeters   Posted on: 07/24/08 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Virtualization: Architectural Considerations And Other Evaluation Criteria VMware Of the many approaches to x86 systems virtualization available in the ... Download Now
• Three Steps You Need to Know to Stop Data Loss Varonis Sensitive data exposed to misuse or loss... it is the stuff of nightmares ... Download Now
• The Impact of Virtualization Software on Operating Environments VMware Today's use of virtualization technology allows IT professionals to ... Download Now