ArcanolothFeb 4
#UnitedDomains hat zum x-ten Mal in den letzten paar Jahren mein primaere #Domain verkackt; email, etc. alles tot; Einloggen ins UI geht auch nicht (vermutlich wegen dem ganzen Deutsche-Tochtergesellschaft Brimborium). Ich habe die Schnautze gestrichen voll… Also, wer kennt einen brauchbaren #desec freundlichen (also deren #dns server) #registrar fuer #de domains?
Herr HochhausJan 24

Diese Woche war eine gute Woche. Dreimal de-amerikanisiert mit

iCloud Mails —> #mailboxorg
Cloudflare DNS —> #deSEC
iCloud Drive —> #opencloud

Noch einige Aufräumarbeiten zu machen und einen Blogpost zu schreiben, speziell das docker compose für OpenCloud war schwieriger als es sein sollte.

#did #dut

Show threadJason EVRARDJan 8

• Moteur de Recherche : Google → @duckduckgo
Recherche anonymisée, sans pub.

• Filtrage DNS Réseau : DNS FAI → #NextDNS
Blocage des traqueurs, malwares et publicités à la source pour tous les appareils du réseau.

• Création nom de domaine : #deSEC
Accéder plus facilement à mes services.

3/13

Alexey SkobkinDec 30

Есть тут кто живущий на deSEC в качестве DNS-провайдера?

Как впечатления?

#DNS #deSEC #Europe #DNSSec #hosting #providers #help #survey

deSEC – Free Secure DNS

Show threadjzdmDec 20
@delta It seems, the primary error lays in the way the setup script is requesting the A record for the domain.
It first resolves the #MNAME part from the SOA and then tries to resolve the A record by sending a request to the MNAME server.
This is incorrect as the MNAME is not required to be publicly reachable. In the case of #desec this method fails. See https://talk.desec.io/t/communications-error-with-desec-services/1454
Communications error with deSEC services

HI there, I’m trying to install a chatmail server using deSEC as the DNS manager. However, the installer reports an error when running dig @get.desec.io. -r -q <my_domain> -t A +short. And if I run this same command from my command line I get the following error: ;; communications error to 2a01:4f8:10a:1044:deec:642:ac10:80#53: connection refused ;; communications error to 2a01:4f8:10a:1044:deec:642:ac10:80#53: connection refused ;; communications error to 2a01:4f8:10a:1044:deec:642:ac10:80#53...

deSEC Community
Show threadjzdmDec 19
#DNS #followerpower #desec #SOA #MNAME
jzdmDec 19

#DNS question:
Is the "primary master name server" (MNAME) from a SOA entry required to answer DNS queries for the domain in question?

Asking, because desec.io does return "get.desec.io" as the primiary master name server for domains hosted at desec.io. But there is no DNS server answering requests under that domain.
#followerpower #desec #SOA #MNAME

jzdmNov 15
When adding an #ACME #DNS Plugin for #deSEC on #proxmox the DEDYN_TOKEN variable must not contain any quotes. #desecio
Show threadBoris 🏳️‍🌈🤙🌿Nov 12

@hbauer @mnord yes, called DNS-01 challenge https://letsencrypt.org/docs/challenge-types/#dns-01-challenge we use #desec.io as DNS provider.

At our home lab the #traefik http proxy handle those #letsencrypt and ssl encryption stuff and secure all the https traffic from the other containers automagically. It looks like nextcloud.home.domain.tld of course, you also need an internal DNS server for that. But that's anyway good as you have DNS blocker...

Challenge Types

When you get a certificate from Let’s Encrypt, our servers validate that you control the domain names in that certificate using “challenges,” as defined by the ACME standard. Most of the time, this validation is handled automatically by your ACME client, but if you need to make some more complex configuration decisions, it’s useful to know more about them. If you’re unsure, go with your client’s defaults or with HTTP-01.

Herr Ungewiss ☕️🎶Nov 9

Kann es sein, dass ein mit deSEC eingerichteter DynDNS-Zugang öfter am Tag nicht verfügbar ist?
In letzter Zeit habe ich da häufiger Probleme mit der Erreichbarkeit. Das restliche Netzwerk und auch der Internetzugriff funktionieren ohne Probleme.
Hinter dem dynDNS hängt eine NextBox von NitroKey.

#DynDNS #DeSEC #askFedi