It's fine when it's a non default option. Like use x.x.x.x for DNS, x.x.x.y for DNS+adblocking, x.x.x.z for totalitarian corporate blocklist that doesn't let you do anything fun
replyI believe cloudflare only blocked archive.is on their "Families" filtered dns. I've been using their normal 1.1.1.1 and haven't encountered any blocks.
replyIIRC the block was on archive.today's side as a protest against 1.1.1.1 intentionally not supporting ECS.
replyThis is what I am referring to. But from an end-user side, one option does not work, and one does work. Then I will use the working DNS.
replyYesterday 1.1.1.1 failed to resolved "theinformation.com" (hosted on CF itself!) for many hours, answering NXDOMAIN.
reply