In 2023 operations for the .GOV TLD transitioned from Verisign to Cloudflare (opens in new tab)

By making it hard just to hijack a crucial TLD and transfer it over to an potential adversary without the cooperation of multiple trusted parties? It seems to me this is DNSSEC working as designed, and being remarkably flexible in doing so. Sometimes things _should_ be difficult to do.

Verisign sold its CA back in 2010.

this holds true for a quantitative comparison. thou, i suspect that domain to be unusually influential

Not that I stay up at night worrying about Cloudflare, but Cloudflare is literally the Man In The Middle between the user and the instances running at AWS, GCP, or Azure.

Those are all part of the DNS.

Look at the amount of coders who can struggle with simple system settings.

Some people only learn what they want to or need to learn, the bare minimum.

They don’t need to know the edge cases to understand the basics of how DNS works. It is a foundational element of how the internet works and any software dev should have at least some fundamental knowledge of it (unless they don’t do anything that ever touched networking which I imagine is rather rare).

While there are certainly complex and weird stuff in the DNS world. The basic of how the DNS works is really not that complicated.

Yeah, but it's not like those comments are making a mistake about how the tech works because they're looking to learn something today. Posting an axe-grinding comment that shows a clear misunderstanding of the technology on a technical forum is an unforced and pretty indefensible error.

> registrar business

They're the registry, not the registrar. CISA is the registrar for .gov domains, Cloudflare just handles the backend. (DNS and whois infrastructure)

Government employees likely never see anything about Cloudflare at all when they manage the DNS settings for domains, just like I never see anything about Charleston Road Registry (Google subsidiary) when I manage a .dev domain on Name.com.

> push their Anti DDoS stuff on a captive audience

How is this a captive audience? Are you implying Cloudflare won't allow .gov domains to use non-cloudflare nameservers?

> push their Anti DDoS stuff on a captive audience

This is a very provocative way to spin “selling the CDN services customers are buying”. What reason do we have to think anyone is an unwilling party to that transaction?

How dare they sell their reliable and popular products at rates untouched by akamai and fastly.

That sounds vaguely like Qwest.

https://en.wikipedia.org/wiki/Qwest#Refusal_of_NSA_surveilla...

He’s getting downvoted for confusing two unrelated services. What you’re both talking about is what happens when someone uses Cloudflare’s CDN, enables their managed CAPTCHA feature, and directs their web traffic through it. This is about DNS, which is a separate service at a lower level.

Agencies would have to contract with Cloudflare separately to use the CDN, and each contract is a separate competition where a different part of the government using Cloudflare for a different service would not be considered when reviewing bids.