How To Fix Dns Server Recursive Query Cache Poisoning Weakness. I found our dns server cached a list of ns records (name servers )for this domain. The remote name server allows recursive queries to be performed by the host running nessusd.
Can anyone tell what the results means and how to fix it or further troubleshooting? The weakness in this argument is that even if you do mask your dns queries (the isp doesn't know you. ‣ a question is sent out, and the querying ‣ if a name server provides both recursive and authoritative name service, a successful attack on the recursive portion can store bad data that is.
Dns cache poisoning attacks refer to polluting this very cache existing on intermediary servers.
How do i verify that my isp or my own recursive resolvers are free from dns cache poisoning bug that is promised full disclosure of the flaw by dan on august 7 at the black hat conference? I'm trying to see how we solve the unencrypted unbound recursive queries out to the internet from the router. Resolving fix dns complications from time to time normally takes a certain amount of endurance, but is usually anything you can normally do on your own dns server without having phoning technological assistance fix dns. I have the internal network on a nat setup with dns (allow remote requests on).
Tidak ada komentar:
Posting Komentar