Oh wow. AT&T has long been one of the networks I've dreaded running afoul of when sending email newsletters. For years they've been opaque in how their process for getting a false positive IP address de-listed from their block list.
Most networks have a form you fill out, a list of things you have to fulfill to get automatically restored, and some automatically reinstate you with a delay if you even contact them.
For years AT&T has operated under the "can neither confirm nor deny" philosophy. It has taken me weeks to a month to get a blocked IP address reinstated.
I had some email delivery issues with Gmail and needed to make some DNS changes to make Gmail happy, which instantly landed me in AT&T hell. I was expecting a month of neglect. Instead, they replied back within a few days to let me know that my request will be carried out shortly.
Mais :nko_angry: comment ça peut fonctionne un coup et l'autre pas ...
Sur le OnePlus 6T (Android 11) :
Quand je passe par Rethink DNS (avec mon DNS) j'ai aucun accès a mes mails (Proton, Infomaniak, Free), Matrix mais pas de soucis pour me connecter a Iceshrimp ou Conversatin
Quand je passe le DNS direct dans la config Wi-Fi, j'ai les mail, Matrix, mais impossible de me connecter a mon instance Iceshrimp (Web ou app), Fdroid arrive pas joindre les serveurs.
Y a que Conversation qui fonction dans les deux cas en fait ...
"Because of the lack of clear signals of general adoption of DNSSEC over three decades, is it time to acknowledge that DNSSEC is just not going anywhere? Is it time to call it a day for DNSSEC and just move on?"
We plan to implement #JSON output in our #DNS investigation tool dnsi. There is informational RFC 8427 for representing DNS messages in JSON, but we’d like to see if there is a more ergonomic way of representing such a format. We'd love to hear about your use cases and wishes. https://github.com/NLnetLabs/dnsi/issues/12
Délégation des noms de domaine. Les registres ont des règles d'enregistrement, parfois différentes. Ainsi, .coop est réservé aux coopératives et alliés.
C'est pendant les pannes qu'on peut le mieux observer comment un système marche. Les perturbations qui affectent le serveur racine du #DNS identifié par la lettre C sont donc l'occasion d'apprendre comment fonctionne ce système des serveurs racine.
@shane_kerr@jpmens I just had the opposite train of thought: (aggressively) discard all cached entries when I know a zone has been updated (increased ZONEVERSION).
Maybe this could make the CDNs stop using dramatically low #DNS TTLs on all their records, just in case they might update their zone (or we could more comfortably use higher min-ttl values).
I also some potential to limit of outages caused by #DNSSEC bad practice.
Są tu spece od Dockera? Próbuję uruchomić kontener Dockera używają Podmana (https://github.com/TechnitiumSoftware/DnsServer/blob/master/CHANGELOG.md), ale utknąłem. Po wielu próbach, kombinowaniu, aktualizacji setek programów, utknąłem na niemożności uruchomienia kontenera, bo twierdzi, że port 53/tcp jest w użyciu. Zrobiłęm już chyba wszystko, co mi wpadło do głowy, czyli wyłączenie systemd, wyłączenie nasłuchiwania przez systemd na porcie 53 i nic to nie daje. Co ciekawe, netstat nie pokazuje portu 53 jakoby był w użyciu, więc nie wiem nawet, jaki program może tego używać. Co ciekawe, jak wziąłem nmapa z innego hosta, to pokazuje, ze port 53 jest zamkniety, wiec cos tam nasluchuje, ale nie wiem co.
Podobno podman używa jakiegoś własnego serwera DNS do zarządzania siecią między kontenerami, ale nie ogarniam tego, a i nie wiem, czy tu może być problem. Poza tym serwerem podmana, nie przychodzi mi juz nic do glowy.
»Cloudflare-Alternative:
19 Cloudflare-Alternativen im Überblick«
Hat jemensch von euch Erfahrung mit eines diesen Alternativen oder gar sogar mit einer nicht aufgeführten? Wenn ja, welches könnt ihr aus welchen Argumente und Gründen empfehlen?
(Ich zweifle immer noch welches am "sichersten" und "daten sparsam" ist)