fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-12-24 01:42:10 +00:00
Code Issues Projects Releases Wiki Activity

Switched to deSEC

Browse source
This commit is contained in:
Rohan Kumar 2022-09-09 21:31:12 -07:00
parent df96135934
commit 015d8bcf25
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/notes/big-tech-nameservers.md
View file

@ -7,3 +7,5 @@ Many people are worried about Amazon Web Services and especially Cloudflare cent
Hot take: it's fine to use a "Big Tech" provider **as a name server,** provided you can handle the 24-hour delay involved in a migration. Of all things, using a name server doesn't have nearly the same the drawbacks as other types of centralization. It's super easy to migrate, and DNSSEC keep name servers honest. There are more important things to worry about.
I'll switch to Cloudflare *just for DNS,* because it's one of the only providers that supports DNSSEC and the new HTTPS records. The latter will be useful once a web server finally gains Encrypted Client Hello support; I'm watching Nginx, OpenLiteSpeed, H2O, redbean, and Caddy.
<ins datetime="2022-09-09T21:31:12-07:00">Update: I switched my name servers from Cloudflare to <a href="https://desec.io/">deSEC</a>.</ins>