digitalcourage.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Diese Instanz wird betrieben von Digitalcourage e.V. für die Allgemeinheit. Damit wir das nachhaltig tun können, erheben wir einen jährlichen Vorausbeitrag von 1€/Monat per SEPA-Lastschrifteinzug.

Server stats:

816
active users

#dns

28 posts28 participants0 posts today
Charlie O’Hara<p>Apparently I have too much time on my hands, so I started generating DNS zone files so I can use BIND on my local network.<br><a href="https://indieweb.social/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNS</span></a> <a href="https://indieweb.social/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelfHosting</span></a> <br><a href="https://github.com/awfulwoman/infra/tree/main/ansible/roles/configure-dns-server" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/awfulwoman/infra/tr</span><span class="invisible">ee/main/ansible/roles/configure-dns-server</span></a></p>
Andrii Kuznietsov<p>🐧 Як змінити <a href="https://social.kyiv.dcomm.net.ua/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNS</span></a>-сервер на <a href="https://social.kyiv.dcomm.net.ua/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ubuntu</span></a> 👇<br><a href="https://linuxthebest.net/uk/kak-yzmenyt-svoj-dns-server-v-ubuntu/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">linuxthebest.net/uk/kak-yzmeny</span><span class="invisible">t-svoj-dns-server-v-ubuntu/</span></a></p>
Miek Gieben<p>OK, plan 2.1; modernizing miekg/dns wihtout _completely_ rewriting - sort of lessons learned.</p><p>Pondering if domain names should stay strings or move to []byte.</p><p><a href="https://mastodon.cloud/tags/go" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>go</span></a> <a href="https://mastodon.cloud/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dns</span></a></p>
※ Succubus Mia 🏳️‍⚧<p>Use all the free DNS.<br><a href="https://kinkycats.org/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://kinkycats.org/tags/server" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>server</span></a> <a href="https://kinkycats.org/tags/network" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>network</span></a> <a href="https://kinkycats.org/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dns</span></a></p>
Patrick Mevzek<p><span class="h-card" translate="no"><a href="https://social.wildeboer.net/@jwildeboer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jwildeboer</span></a></span> Publish it in the <a href="https://framapiaf.org/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNS</span></a> :-) See the SMIMEA DNS record type (RFC 8162) but no ideas which MUA really consume it.</p>
Miek Gieben<p>Funny that dig prints RR's TTL, class and type in the _exact_ opposite way of how they are in the wire data <a href="https://mastodon.cloud/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dns</span></a></p>
Mœllus<p>Artikel von 2014 <a href="https://sz-magazin.sueddeutsche.de/technik/schluessel-zur-macht-80495" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">sz-magazin.sueddeutsche.de/tec</span><span class="invisible">hnik/schluessel-zur-macht-80495</span></a> /via <a href="https://wandzeitung.xyz/tags/sz" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sz</span></a> <a href="https://wandzeitung.xyz/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dns</span></a> <a href="https://wandzeitung.xyz/tags/icann" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>icann</span></a> <a href="https://wandzeitung.xyz/tags/internetz" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>internetz</span></a></p>
The New Oil<p><a href="https://mastodon.thenewoil.org/tags/PiHole" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PiHole</span></a> discloses <a href="https://mastodon.thenewoil.org/tags/DataBreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DataBreach</span></a> triggered by <a href="https://mastodon.thenewoil.org/tags/WordPress" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WordPress</span></a> plugin flaw</p><p><a href="https://www.bleepingcomputer.com/news/security/pi-hole-discloses-data-breach-via-givewp-wordpress-plugin-flaw/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">bleepingcomputer.com/news/secu</span><span class="invisible">rity/pi-hole-discloses-data-breach-via-givewp-wordpress-plugin-flaw/</span></a></p><p><a href="https://mastodon.thenewoil.org/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>privacy</span></a> <a href="https://mastodon.thenewoil.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://mastodon.thenewoil.org/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNS</span></a> <a href="https://mastodon.thenewoil.org/tags/GiveWP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GiveWP</span></a></p>
kapierstau <a class="hashtag" href="https://kowelenz.social/tag/google" rel="nofollow noopener" target="_blank">#Google</a> macht <a class="hashtag" href="https://kowelenz.social/tag/invidious" rel="nofollow noopener" target="_blank">#Invidious</a> durch immer neue Änderungen das Leben schwer. Das ewige hin und her dürfte auch die Betreiber ziemlich nerven, nicht nur User wie mich.<br><br>Habe weder die <a class="hashtag" href="https://kowelenz.social/tag/hoffnung" rel="nofollow noopener" target="_blank">#Hoffnung</a> noch die <a class="hashtag" href="https://kowelenz.social/tag/erwartung" rel="nofollow noopener" target="_blank">#Erwartung</a>, dass das <a class="hashtag" href="https://kowelenz.social/tag/produkt" rel="nofollow noopener" target="_blank">#Produkt</a> <a class="hashtag" href="https://kowelenz.social/tag/youtube" rel="nofollow noopener" target="_blank">#Youtube</a> sich dahingehend in eine (in meinen Augen) "vernünftigere" Richtung entwickelt.<br><br>Was ich trotzdem nicht verstehe: Sollten (auch) Sperren der Grund dafür sein, dass alternative Frontends zeitweise nicht mehr funktionieren, wäre es nicht einfacher keine <a class="hashtag" href="https://kowelenz.social/tag/ipv4" rel="nofollow noopener" target="_blank">#IPv4</a>-Adressen mehr zu verwenden? Bei der größeren Menge verfügbarer <a class="hashtag" href="https://kowelenz.social/tag/ipv6" rel="nofollow noopener" target="_blank">#IPv6</a>-Adressen dürfte <a class="hashtag" href="https://kowelenz.social/tag/alphabet" rel="nofollow noopener" target="_blank">#Alphabet</a> es doch schwer haben ganze Bereiche zu sperren ohne versehentlich echte User ihrer <a class="hashtag" href="https://kowelenz.social/tag/plattform" rel="nofollow noopener" target="_blank">#Plattform</a> auszuschließen oder vorauszusehen, welche in Zukunft hinter der <a class="hashtag" href="https://kowelenz.social/tag/domain" rel="nofollow noopener" target="_blank">#Domain</a> einer <a class="hashtag" href="https://kowelenz.social/tag/instanz" rel="nofollow noopener" target="_blank">#Instanz</a> steckt? Außerdem ist schätzungsweise der Wechsel für die Betreiber deutlich zügiger und unkomplizierter möglich und User können ohne Einträge im <a class="hashtag" href="https://kowelenz.social/tag/cache" rel="nofollow noopener" target="_blank">#Cache</a> ihres <a class="hashtag" href="https://kowelenz.social/tag/dns" rel="nofollow noopener" target="_blank">#DNS</a> auch fast lückenlos weiter "vernünftiger" YouTube-exklusive Inhalte konsumieren.
Infoblox Threat Intel<p>Tens of thousands of compromised websites use DNS TXT records to conditionally redirect visitors to malicious content. For years, this exclusively redirected to VexTrio TDS - but in late-November 2024, it changed. But did it? We think not. </p><p>A couple of major takeaways from the research we released in June and what we've continued to learn since then: </p><p>* DNS is being used very successfully to drive innocent people to malware and scams, including alarming tech support scams </p><p>* These can be stopped by blocking the DNS query but it must be done at the website server side not the visitor </p><p>* VexTrio is tight not just with malware actors who hack sites and drive traffic to them, but they appear to be one and the same, or at least closely related, to infamous TDS and a multitude of other "adtech" platforms.</p><p>* reviewing old literature carefully connects VexTrio via shared software with ROI777 </p><p>we're going to throw up more "snackables" before heading to Vegas. If you want to see the faces behind VexTrio and hear their origin story, come see our talk or track us down at the booth. </p><p><a href="https://infosec.exchange/tags/threatintel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>threatintel</span></a> <a href="https://infosec.exchange/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>malware</span></a> <a href="https://infosec.exchange/tags/tds" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tds</span></a> <a href="https://infosec.exchange/tags/vextrio" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vextrio</span></a> <a href="https://infosec.exchange/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dns</span></a> <a href="https://infosec.exchange/tags/cybercrime" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybercrime</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/scam" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>scam</span></a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/infoblox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infoblox</span></a></p>

Da mir heute wetterbedingt etwas fad ist, habe ich daheim auf die Schnelle mal #Technitium #DNS in einem #Proxmox #LXC installiert. Habe hier in den letzten Tagen den einen oder anderen Beitrag dazu gelesen und ihr kennt mich ja, ich bin halt ein Spielkind. :wink:

Somit habe ich aktuell als Haupt DNS #AdguardHome mit lokalen #Unbound (#OPNSense) und zum Testen einen #PiHole und jetzt eben auch Technitium ebenfalls mit lokalen Unbound.

Bin gespannt, ob eines der beiden Adguard Home ablösen wird. Vorteil von Technitium ist schon mal, dass der lokale Unbound ohne rumbasteln verwendet werden kann, da dies in den Boardmitteln bereits enthalten ist.

DNS management with OpenTofu and some AI assistance. Needed to migrate dozens of DNS records to IaC. The key was providing specific context instead of vague requests. AI handled parsing raw data files and HTML, I focused on validation and problem-solving. It worked surprisingly well, I never want to go back to doing such stuff manually.

More in my Blog: dominik.wombacher.cc/posts/dns

dominik.wombacher.ccThe Wombelix Post - DNS management with OpenTofu and some AI assistanceUsing AI assistance to migrate DNS records from BIND zone files to OpenTofu configuration
#AI#DNS#OpenTofu