<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>FlowDNS: Correlating Netflow and DNS Streams at Scale · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2211.05682/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2211.05682/feed.xml" rel="self" type="application/rss+xml" /><item><title>FlowDNS: Correlating Netflow and DNS Streams at Scale — mentioned by nobody9999</title><link>https://news.ycombinator.com/item?id=44222225</link><guid isPermaLink="false">urn:hackerpapers:mention:2211.05682:44222225</guid><pubDate>Mon, 09 Jun 2025 07:36:42 GMT</pubDate><description>&lt;p&gt;&amp;gt;DNS over HTTPS exclusively exists because stuff like Pi-hole started eating into Ad Revenue for Google. That&amp;#x27;s why this &amp;quot;feature&amp;quot; is so hard to disable in the browsers as well. Exactly. Which is why I point my Pi-Hole at my own recursive resolver. Can my ISP see those queries? Sure. Are they using transparent proxies to redirect my queries to their resolvers? No. Is my ISP cataloguing all my recursive resolutions? Maybe. But probably not. Theoretically, they could, but mirroring all the traffic to storage for tens of millions of customers seems exorbitant, unnecessary and wasteful. More…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2211.05682/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.NI</category></item></channel></rss>
