DNS cache poisoning, the Internet attack from 2008, is back from the dead

Re:DNS cache poisoning, the Internet attack from 2008, is ba... by kordlessagain on Thursday November 12, 2020 @12:24PM (#25072100)

8.8.8.8 and 8.8.4.4 are your DNS server friends and probably hardened against this, at least I hope they are.

[ Parent | on HN ]

Re:DNS cache poisoning, the Internet attack from 2008, is ba... by reco on Thursday November 12, 2020 @12:44PM (#25072393)

Yeah, let me feed all my internet browsing data directly to google. No thanks.

[ Parent | on HN ]

Re:DNS cache poisoning, the Internet attack from 2008, is ba... by Lammy on Thursday November 12, 2020 @01:22PM (#25072899)

A local caching Unbound instance is your DNS friend, never Google or Cloudflare or any other large infrastructure company.

[ Parent | on HN ]

Re:DNS cache poisoning, the Internet attack from 2008, is ba... by tptacek on Thursday November 12, 2020 @01:43PM (#25073197)

If your goal is to maximize the amount of information DNS reveals about your Internet usage, to the maximum number of DNS authority servers, running your own local Unbound instance is definitely a good way to accomplish that.

[ Parent | on HN ]

Re:DNS cache poisoning, the Internet attack from 2008, is ba... by Lammy on Thursday November 12, 2020 @01:53PM (#25073362)

I just have it set up to forward most zones to my ISP DNS, but you could just as easily do that with 8.8.8.8 or whatever and still minimize the number of requests you make to them. you’ll notice the lower latency too.

[ Parent | on HN ]