I'm sad about LetsEncrypt TLS-SNI-{01,02} challenges shutting down for good:
https://community.letsencrypt.org/t/2018-01-11-update-regarding-acme-tls-sni-and-shared-hosting-infrastructure/50188 …
The http-01 and dns-01 challenges kinda suck, IMHO. I don't want to even listen on port 80. 
Hope there's a tls-sni-03 fix one day.
-
I'm saying the goal here is having the validation method be minimally intrusive to the *actual* usage of the service. For internal sites that's trivial with DNS-01 because they don't have external DNS... so you make one just for ACME.
For external sites you need to integrate it with a real, production DNS which is annoying. Much like HTTP-01 needs to integrate with real, production web server vhosts. Meanwhile TLS-SNI-01 could stay out of the way with .acme.invalid vhosts.
-
-
I always found that the needed records lived nicely beside the production records. Maybe that has more to do with the DNS backend storage and if it accommodates the needed records. I can see how that could be a problem.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.