Post ABup1WiCKXWCOP20Uy by demoakracia@pleroma.libretux.com
 (DIR) More posts by demoakracia@pleroma.libretux.com
 (DIR) Post #ABumFJwuHMCJ08nUaO by jrballesteros05@fosstodon.org
       2021-10-01T08:20:18Z
       
       0 likes, 0 repeats
       
       I'm having some troubles with OpenNIC DNS. They are not resolving the "slack.com" domain. Does anyone know if there is a related issue? I temporally changed the upstream DNS in my pihole to "cloudfare" for testing purposes and it works.
       
 (DIR) Post #ABumV9KvVJIuiia1iq by lig@fosstodon.org
       2021-10-01T08:23:07Z
       
       0 likes, 0 repeats
       
       @jrballesteros05 they did something recently. That's fore sure.> whois slack.comUpdated Date: 2021-09-30T16:10:03+0000
       
 (DIR) Post #ABumXAD7E2KS0gt3Oy by lig@fosstodon.org
       2021-10-01T08:23:32Z
       
       0 likes, 0 repeats
       
       @jrballesteros05 they did something recently. That's for sure.> whois slack.comUpdated Date: 2021-09-30T16:10:03+0000
       
 (DIR) Post #ABumdn5tZPlKLJfai0 by jrballesteros05@fosstodon.org
       2021-10-01T08:24:43Z
       
       0 likes, 0 repeats
       
       @lig Yeah, I tried other DNS different to OpenNic and LibreDNS and they work. I don't know what the hell they've done but it surely affects other alternatives.
       
 (DIR) Post #ABumnxN2DXo76uXAtE by jrballesteros05@fosstodon.org
       2021-10-01T08:26:33Z
       
       0 likes, 0 repeats
       
       @lig I also understand when you modify something in your domain it takes some time to spread over internet. I don't know if the open alternatives take longer than proprietary ones to update.
       
 (DIR) Post #ABup1WiCKXWCOP20Uy by demoakracia@pleroma.libretux.com
       2021-10-01T08:46:18.139420Z
       
       0 likes, 0 repeats
       
       @jrballesteros05 Prueba OpenDNS, FreeDNS, SafeDNS o UncensoredDNS
       
 (DIR) Post #ABup1X98iN4LjxdWUa by jrballesteros05@fosstodon.org
       2021-10-01T08:51:24Z
       
       0 likes, 0 repeats
       
       @demoakracia No conozco los demás pero recuerdo haber leído por ahí que OpenDNS ya no es tan confiable.
       
 (DIR) Post #ABus6ABbo6gfqCgsjI by iron_bug@friendica.ironbug.org
       2021-10-01T09:25:09Z
       
       0 likes, 0 repeats
       
       I believe this can be the problem with LetsEncrypt CA certificates. my server didn't work normally either until I deleted the outdated CA certificate (DST_Root_CA_X3). while the outdated CA is there it is used in verifying chains and fails server certificates checks although the certificates are allright.  not all admins deleted the outdated certificates and the network is going to hell partially since 30th of September, when the certificate was over.
       
 (DIR) Post #ABuwbkYJ34P1QEclfc by iron_bug@friendica.ironbug.org
       2021-10-01T09:26:42Z
       
       0 likes, 0 repeats
       
       now instead of DST_Root_CA_X3 the ISRG_Root_X1 is used.
       
 (DIR) Post #ABuwbl4D8RvJ1BYFOq by jrballesteros05@fosstodon.org
       2021-10-01T10:16:23Z
       
       0 likes, 0 repeats
       
       @iron_bug @lig It makes all the sense. I will check how to report them the issue.
       
 (DIR) Post #ABv6kcpo6xZrdMgI7M by demoakracia@pleroma.libretux.com
       2021-10-01T09:23:33.810901Z
       
       0 likes, 0 repeats
       
       @jrballesteros05 Puedes mirar el listado de dnscrypt, donde ponen las preferencias de mogollón de servidores.https://github.com/DNSCrypt/dnscrypt-proxy/wiki/Configuration-Sources#what-is-the-point-of-these-listsSi lo tienes instalado, hay un word con el listdo.
       
 (DIR) Post #ABv6kdHoQpyl2Dmelk by jrballesteros05@fosstodon.org
       2021-10-01T12:10:00Z
       
       0 likes, 0 repeats
       
       @demoakracia Parece ser un problema de Letsencrypt. Ya esperaré a que se solucione o bien buscar las alternativas.
       
 (DIR) Post #ABvCpaTEvYl7TVsHmy by funkyduck@fosstodon.org
       2021-10-01T13:18:01Z
       
       0 likes, 0 repeats
       
       @jrballesteros05 they did this: https://lists.dns-oarc.net/pipermail/dns-operations/2021-September/021340.html.  see here: https://status.slack.com/2021-09/06c1e17de93e7dc2, specifically 'In order to resolve this faster, your ISP (Internet Service Provider) will need to flush their DNS record for slack.com.'  Hopefully that's all it is.
       
 (DIR) Post #ABvKDgENrSqZyBMSoq by jrballesteros05@fosstodon.org
       2021-10-01T14:40:58Z
       
       0 likes, 0 repeats
       
       @funkyduck There is a letsencrypt issue. I was suspecting it had to do but it was pretty strange that any DNS, which isn't open, was affected. I could work without slack today. I don't know if calling ISP would help because I don't use their DNS. But I should look to report to opennic because I use their DNS.
       
 (DIR) Post #ABvLfFqfdzy6Cyywwi by iron_bug@friendica.ironbug.org
       2021-10-01T14:56:52Z
       
       0 likes, 0 repeats
       
       it's dependent only on certificates servers use. as LE is free many servers use it.