News for hackers. Stuff that matters.
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by sgbeal on Sunday March 22, 2026 @05:54AM (#47475926)
> 1.1.1.2 is their malware-blocking DNS, and 1.1.1.3 is their parental-controls DNS. ...

TIL, thank you. Time to go tweak my pi-hole server...

Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by arvid-lind on Sunday March 22, 2026 @06:01AM (#47475957)
I'm just curious, given all the other options that respect your privacy and don't put data collection at the center of their business model, why do you use Cloudflare on your pi-hole?
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by sgbeal on Sunday March 22, 2026 @06:57AM (#47476254)
> why do you use Cloudflare on your pi-hole?

Because "if it ain't broke, don't fix it." i'm not one of those users who want to endlessly tweak their ad blocker. i want to set it up, clicking as few checkboxes as necessary to get it going, and then leave it. However, (now) knowing that Cloudflare filters different only each of their servers, i'm incentivized to go tweak a number in the config (as opposed to researching the pros and cons of every possible provider, a detail i truly have no interest in pursuing).

Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by OJFord on Sunday March 22, 2026 @12:32PM (#47479226)
If you mean you had 1.1.1.2 as a secondary, and don't want it to have a different configuration, you can use 1.0.0.1 along with 1.1.1.1 instead.
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by sgbeal on Sunday March 22, 2026 @02:20PM (#47480477)
> If you mean you had 1.1.1.2 as a secondary, and don't want it to have a different configuration, you can use 1.0.0.1 along with 1.1.1.1 instead.

i had no clue which one was active. It was, for me, just a checkbox at the time. This thread prompted me to go check and tweak appropriately.

Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by daymanstep on Sunday March 22, 2026 @06:27AM (#47476087)
Which options respect your privacy?
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by diarrhea on Sunday March 22, 2026 @07:57AM (#47476596)
I use unbound (recursive resolver), and AdGuard Home as well (just forwards to unbound). Unbound could do ad-blocking itself as well, but it's more cumbersome than in AGH. So I use two tools for the time being.

The upside is there's no single entity receiving all your queries. The downside is there's no encryption (IIRC root servers do not support it), so your ISP sees your queries (but they don't receive them).

Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by travoc on Sunday March 22, 2026 @06:48AM (#47476192)
AdGuard DNS servers are excellent.
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by nom on Sunday March 22, 2026 @06:59AM (#47476268)
quad9
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by dannyfritz07 on Sunday March 22, 2026 @08:36AM (#47476880)
I'll throw https://nextdns.io into the mix. Been very happy with it. Supports DOH, block lists, among a plethora of other features.
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by ranger_danger on Sunday March 22, 2026 @10:04AM (#47477674)
The ones where you don't send a single company all of your queries
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by TZubiri on Sunday March 22, 2026 @07:10AM (#47476318)
what is the vector here? dns traffic is practically anonymous, there would have to be some very specific and purposeful trickery going on to link dns traffic to an identity. It sounds like something more hypothetical than a tangible threat model
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by hirako2000 on Sunday March 22, 2026 @07:44AM (#47476517)
It isn't anonymous. DNS server resolve, IP addresses by hostnames. It cannot then inspect further traffic but it certainly can log your IP address and all URL's a given IP ever hit.

Since ISP know your identity, and all it takes is to (request and get) the DNS logs and ISP servitude for all sort of questionable information, you as an identity are giving away all sites domains you visit.

Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by sgbeal on Sunday March 22, 2026 @09:01AM (#47477072)
> It cannot then inspect further traffic but it certainly can log your IP address and all URL's a given IP ever hit.

Correction: they can log host names/IPs, not URLs. The path of any given URL is part of the HTTP header, invisible to onlookers (assuming HTTP and assuming HTTPS is uncracked).

Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by hirako2000 on Sunday March 22, 2026 @02:20PM (#47480469)
I can't edit. That is correct. URLs can't be known to a DNS server. Just the hostname and IP.
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by UqWBcuFx6NV4r on Sunday March 22, 2026 @10:49AM (#47478104)
Hi. If your response involves explaining the very very basics of DNS to someone that clearly knows what DNS is, please consider the possibility that you may have misunderstood them instead of lecturing them on the basics of ubiquitous internet technologies.
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by hirako2000 on Sunday March 22, 2026 @02:19PM (#47480456)
I didn't mean to offense. It did seem OP didn't get the IP can be logged, either that or how an IP can reveal identity.
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by TZubiri on Sunday March 22, 2026 @04:02PM (#47481528)
Considering that the DNS in question is third-party, that is, it's independent from the ISP. Then the DNS and the ISP will not share data with each other on a routine basis, which would make this concern negligible for every day traffic.

So to simplify, the DNS provider has a map of IPs to Domains visited, while the other hand an ISP has a map of IP addresses to identities.

To even cross-reference the data, the ISP and the DNS provider would need to partner, and violate their privacy guarantees.

At the very least it's obvious that using a separate DNS provider than your ISP's provides additional anonimity by decentralizing your traffic. Although this comes with a tradeoff, having 2 providers increases the odds of partial leaks.

This analysis is so overkill for your personal traffic that it borders tinfoil territory, if we are in a professional setting and are discussing the competitive data of a company or that of thousands of users, then this level of scrutiny is merited, but as-is, separating your DNS provider from your ISP is already very marginal and a bit paranoid. Evaluating the DNS providers to such an extent that a huge security company with good legal standing would somehow qualify as unsafe, for the traffic of one user, I stress, is paralyzingly over-engineering the security of an infrastructure that has already been secured such that users don't need to know what a DNS and how to configure it in order to have safe and private internet.

Imagine going to the bank and asking the teller for a withdrawal but not disclosing the amount and coming up with a mechanism to withdraw without anyone from the bank knowing what you withdrew. Sure, it increases your security, but also come on, what are we doing here?

Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by arvid-lind on Sunday March 22, 2026 @08:48AM (#47476967)
> A Cloudflare Ray ID is an identifier given to every request that goes through Cloudflare.

https://developers.cloudflare.com/fundamentals/reference/clo...

if you think a little creatively about how this information could be used by an organization that was created at the insistence of the United States Department of Homeland Security, then you're on the right track.

Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by acdha on Tuesday March 24, 2026 @08:20AM (#47501574)
This is a silly conspiracy theory: the ray ID references the specific CDN edge server which processed your request.

Even the request ID is not what you’re implying: that’s unique for a single request, but it’s not public and anyone who has your HTTPS payload has equivalent tracking capabilities.

Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by mat_b on Sunday March 22, 2026 @12:43PM (#47479349)
I did some experimenting recently and I'm quite convinced that when I use Comcasts DNS they are selling it to advertisers. I've switched to 1.1.1.1 simply because it annoys me that Comcast is doing this.
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by edoceo on Sunday March 22, 2026 @01:59PM (#47480236)
How could that experiment work?
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by fn-mote on Sunday March 22, 2026 @07:53PM (#47483660)
Resolve the hostnames but don’t visit the sites. RefrigeratorFixit.com, StoveBrand.com, ConsumerReports.org.

See that you start getting ads for kitchen appliances.

Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by UqWBcuFx6NV4r on Sunday March 22, 2026 @10:41AM (#47478010)
Privacy nuts are almost uniquely unable to comprehend that someone else on earth may possible have priorities that differ from theirs.
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by arvid-lind on Sunday March 22, 2026 @11:05AM (#47478291)
that's an observation, I guess... OP set up a pi-hole so it's not a stretch they would do a quick search for "free privacy dns". you make it sound like it takes some kind of reprioritization, why?
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by philipallstar on Sunday March 22, 2026 @12:41PM (#47479333)
Strong counter-evidence: they ask why.
Re:Cloudflare flags archive.today as "C&C/Botnet"; no longer... by TZubiri on Sunday March 22, 2026 @07:08AM (#47476306)
Today we are one of the lucky 10k