toad.social

Tuxi ⁂Ich teste ja seit ungefähr zwei Wochen mit lokalen <a href="https://anonsys.net/search?tag=DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> Servern in meinem lokalen LAN herum: <a href="https://anonsys.net/search?tag=PiHole" class="mention hashtag" rel="nofollow noopener" target="_blank">#PiHole</a>, <a href="https://anonsys.net/search?tag=Technitium" class="mention hashtag" rel="nofollow noopener" target="_blank">#Technitium</a> und <a href="https://anonsys.net/search?tag=AdGuardHome" class="mention hashtag" rel="nofollow noopener" target="_blank">#AdGuardHome</a>. Alle drei Lösungen verwenden lokalen <a href="https://anonsys.net/search?tag=Unbound" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unbound</a>.Pi-Hole und AdGuard Home laufen auf einem <a href="https://anonsys.net/search?tag=Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a> jeweils in einem <a href="https://anonsys.net/search?tag=LXC" class="mention hashtag" rel="nofollow noopener" target="_blank">#LXC</a> Container. AdGuard Home läuft auf meiner <a href="https://anonsys.net/search?tag=OPNsense" class="mention hashtag" rel="nofollow noopener" target="_blank">#OPNsense</a>.Die Konfiguration ist so, dass im <a href="https://anonsys.net/search?tag=Adguard" class="mention hashtag" rel="nofollow noopener" target="_blank">#Adguard</a> Home als Upstream Server alle drei DNS Server angegeben sind, mit der Option "Paralleles Abfragen (Alle drei Upstream-Server werden angefragt, um dann den schnellsten zu verwenden)". AdGuard Home fragt also bei allen dreien nach und verwendet dann den schnellsten. Was mich echt verwundert, sind die doch sehr großen Unterschiede bei den Antwortzeiten, obwohl alle drei im gleichen lokalen Netzwerk sind und zumindest Pi-Hole und Technitium auch die gleichen Voraussetzungen haben, was die Hardware betrifft. Der Pi-Hole wurde nach der Anleitung vom Kuketz Blog (kuketz-blog.de/pi-hole-einrichtung-und-konfiguration-mit-unbound-adblocker-teil2/) und Technitium wie in diesem Blog beschrieben: fryboyter.de/pi-hole-und-unbound-durch-technitium-ersetzen/<pre><code>192.168.101.96 --> Pi-Hole 192.168.101.82 --> Technitium 192.168.101.1 --> (AdGuard Home auf OPNsense)</code></pre>Hätte echt nicht geglaubt, dass die drei Lösungen sich bei den Antwortzeiten doch so sehr unterscheiden. Unterschiede ja, aber so massiv?

Quad9DNSWe are happy to announce a significant capacity increase in our Warsaw systems, thanks to our partner <a href="https://mastodon.social/tags/i3D" class="mention hashtag" rel="nofollow noopener" target="_blank">#i3D</a>. We're now well-positioned to grow extensively as our user base in Poland (and neighboring countries like Ukraine) continues to expand. We're even more happy to make this announcement since two of our very small team are Polish! We'll continue to rebuild and expand our footprint to provide safe and trusted <a href="https://mastodon.social/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> services for the world. 🇵🇱

Quad9DNSZ przyjemnością informujemy, że dzięki naszemu partnerowi, <a href="https://mastodon.social/tags/i3D" class="mention hashtag" rel="nofollow noopener" target="_blank">#i3D</a>, znacznie zwiększyliśmy naszą wydajność w Warszawie. Jesteśmy dobrze przygotowani na obecny istotny wzrost liczby osób korzystających z naszych usług w Polsce i w krajach sąsiednich (jak Ukraina). Cieszymy się tym bardziej, że dwie osoby w naszym małym zespole są z Polski! Kontynuujemy prace nad ulepszaniem i rozszerzaniem naszej infrastruktury by świadczyć bezpieczne i godne zaufania usługi <a href="https://mastodon.social/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> na całym świecie. 🇵🇱

Nishant Sharma<a href="https://mastodon.social/@quad9dns" class="u-url mention" rel="nofollow noopener" target="_blank">@quad9dns</a> 9.9.9.9 not reachable from AS55836 (Jio) from North and Eastern India.RIPE Atlas measurement: <a href="https://atlas.ripe.net/measurements/123278046/overview" rel="nofollow noopener" translate="no" target="_blank">https://atlas.ripe.net/measurements/123278046/overview</a> <a href="https://mastodon.hopbox.net/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> <a href="https://mastodon.hopbox.net/tags/india" class="mention hashtag" rel="nofollow noopener" target="_blank">#india</a>

DNŠ<a href="https://eupolicy.social/@bert_hubert" class="u-url mention" rel="nofollow noopener" target="_blank">@bert_hubert</a> Interestingly I subconsciously read that hastag as <a href="https://mastodns.net/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> 🙂 Thanks for the writeup. It is a very interesting read.

Miek GiebenMade a proper dnsutil package, but also needed interally, so I copy/generate it....<a href="https://codeberg.org/miekg/dns/src/branch/main/dnsutil_generate.go" rel="nofollow noopener" target="_blank">https://codeberg.org/miekg/dns/src/branch/main/dnsutil_generate.go</a><a href="https://mastodon.cloud/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns</a> <a href="https://mastodon.cloud/tags/go" class="mention hashtag" rel="nofollow noopener" target="_blank">#go</a>

Peter N. M. HansteenIn case you were unaware of that particular scam, "Domain Name Scams Are Alive And Well, Thank You" <a href="https://nxdomain.no/~peter/domain_name_scams_are_alive_and_well_thank_you.html" rel="nofollow noopener" translate="no" target="_blank">https://nxdomain.no/~peter/domain_name_scams_are_alive_and_well_thank_you.html</a> (tracked <a href="https://bsdly.blogspot.com/2016/03/domain-name-scams-are-alive-and-well.html" rel="nofollow noopener" translate="no" target="_blank">https://bsdly.blogspot.com/2016/03/domain-name-scams-are-alive-and-well.html</a>) <a href="https://mastodon.social/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns</a> <a href="https://mastodon.social/tags/domainnamescam" class="mention hashtag" rel="nofollow noopener" target="_blank">#domainnamescam</a> <a href="https://mastodon.social/tags/cndomains" class="mention hashtag" rel="nofollow noopener" target="_blank">#cndomains</a> <a href="https://mastodon.social/tags/chinaname" class="mention hashtag" rel="nofollow noopener" target="_blank">#chinaname</a> <a href="https://mastodon.social/tags/chinanetname" class="mention hashtag" rel="nofollow noopener" target="_blank">#chinanetname</a> <a href="https://mastodon.social/tags/scam" class="mention hashtag" rel="nofollow noopener" target="_blank">#scam</a> <a href="https://mastodon.social/tags/china" class="mention hashtag" rel="nofollow noopener" target="_blank">#china</a> <a href="https://mastodon.social/tags/cybercrime" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybercrime</a>(I repost when one of those scam messages actually reaches a mailbox I read)

Infoblox Threat IntelLast week we released the first of a three part VexTrio origin story. The second part is now available. This research includes more than 200 open source references to help others validate the results and start their own investigations. As of Tuesday, August 5th, all of those links were valid and all went directly to open material …. so anything that is gone, or social media that is now closed… welp, that's the actors, not us. Feel free to report missing things in this thread. :) The second part of this story focuses on the VexTrio activities that extend beyond their well-known traffic distribution systems (TDS). Enjoy. <a href="https://infosec.exchange/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns</a> <a href="https://infosec.exchange/tags/threatintel" class="mention hashtag" rel="nofollow noopener" target="_blank">#threatintel</a> <a href="https://infosec.exchange/tags/scam" class="mention hashtag" rel="nofollow noopener" target="_blank">#scam</a> <a href="https://infosec.exchange/tags/tds" class="mention hashtag" rel="nofollow noopener" target="_blank">#tds</a> <a href="https://infosec.exchange/tags/infoblox" class="mention hashtag" rel="nofollow noopener" target="_blank">#infoblox</a> <a href="https://infosec.exchange/tags/spam" class="mention hashtag" rel="nofollow noopener" target="_blank">#spam</a> <a href="https://infosec.exchange/tags/cybercrime" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybercrime</a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a> <a href="https://infosec.exchange/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#malware</a> <a href="https://blogs.infoblox.com/threat-intelligence/vextrio-unmasked-a-legacy-of-spam-and-homegrown-scams/" rel="nofollow noopener" translate="no" target="_blank">https://blogs.infoblox.com/threat-intelligence/vextrio-unmasked-a-legacy-of-spam-and-homegrown-scams/</a>

Miek GiebenThis looks rock solid,, nothing stands in my waypanic: runtime error: invalid memory address or nil pointer dereferenceoh<a href="https://mastodon.cloud/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns</a> <a href="https://mastodon.cloud/tags/go" class="mention hashtag" rel="nofollow noopener" target="_blank">#go</a>

Renée BurtonVexTrio's origins come from two distinct groups: an Italian group we can date back to 2004 and a Russian-speaking Eastern European group. The Italians were quite successful early on, with a dating app that was among the fastest growing on Facebook in 2012. But our guess is that their profits slid in the years that followed. In 2020, there is an merger-acquisition which leaves the Eastern Europeans in charge. They gain the trademarks, knowledge in spam distribution, and who knows what else. While developers remain in eastern Europe, VexTrio created business headquarters in Lugano, Switzerland. Including the existing AdsPro, which developed the Los Pollos, Taco Loco, and Adtrafico traffic distribution systems (TDS) through their software company HolaCode. (ok it's more complicated than that, but this is the cliffsnotes version). We have identified nearly 100 businesses associated with 8 key figures in many industries, including construction, energy, and advertising.So in the end, what is VexTrio? It's hard to say. We originally used it to refer to the TDS. Nice clean lines... but now, for us it is all the people and their labyrinth of companies. We spoke at BlackHat last week so if you have a briefings pass you can listen to that. Otherwise, find our research online and start your own investigation.<a href="https://infosec.exchange/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns</a> <a href="https://infosec.exchange/tags/threatintel" class="mention hashtag" rel="nofollow noopener" target="_blank">#threatintel</a> <a href="https://infosec.exchange/tags/scam" class="mention hashtag" rel="nofollow noopener" target="_blank">#scam</a> <a href="https://infosec.exchange/tags/cybercrime" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybercrime</a> <a href="https://infosec.exchange/tags/vextrio" class="mention hashtag" rel="nofollow noopener" target="_blank">#vextrio</a> <a href="https://infosec.exchange/tags/infoblox" class="mention hashtag" rel="nofollow noopener" target="_blank">#infoblox</a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a> <a href="https://infosec.exchange/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#malware</a> <a href="https://infosec.exchange/tags/tds" class="mention hashtag" rel="nofollow noopener" target="_blank">#tds</a>

iX MagaziniX-Workshop: Mastering Azure – Administration der Azure Cloud ServicesLernen Sie, die grundlegenden Komponenten der Microsoft Azure Cloud zu administrieren, zu konfigurieren und zu implementieren - in Theorie und Praxis.<a href="https://www.heise.de/news/iX-Workshop-Mastering-Azure-Administration-der-Azure-Cloud-Services-10508253.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon" rel="nofollow noopener" translate="no" target="_blank">https://www.heise.de/news/iX-Workshop-Mastering-Azure-Administration-der-Azure-Cloud-Services-10508253.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon</a><a href="https://social.heise.de/tags/CloudComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudComputing</a> <a href="https://social.heise.de/tags/Containerisierung" class="mention hashtag" rel="nofollow noopener" target="_blank">#Containerisierung</a> <a href="https://social.heise.de/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> <a href="https://social.heise.de/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT</a> <a href="https://social.heise.de/tags/iXWorkshops" class="mention hashtag" rel="nofollow noopener" target="_blank">#iXWorkshops</a> <a href="https://social.heise.de/tags/Virtualisierung" class="mention hashtag" rel="nofollow noopener" target="_blank">#Virtualisierung</a> <a href="https://social.heise.de/tags/Wirtschaft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wirtschaft</a> <a href="https://social.heise.de/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#news</a>

PCHHello Dresden!  We’re excited to share that we are now active and ready for <a class="hashtag" href="https://pleroma.pch.net/tag/peering" rel="nofollow noopener" target="_blank">#peering</a> at Dresden Internet Exchange! A big thank you to <a class="hashtag" href="https://pleroma.pch.net/tag/ddix" rel="nofollow noopener" target="_blank">#DDIX</a> for helping us strengthen and expand a faster, more secure, and more resilient DNS infrastructure. <a class="hashtag" href="https://pleroma.pch.net/tag/dns" rel="nofollow noopener" target="_blank">#DNS</a> <a class="hashtag" href="https://pleroma.pch.net/tag/anycast" rel="nofollow noopener" target="_blank">#Anycast</a> <a class="hashtag" href="https://pleroma.pch.net/tag/dnsanycast" rel="nofollow noopener" target="_blank">#DNSAnycast</a> <a class="hashtag" href="https://pleroma.pch.net/tag/peering" rel="nofollow noopener" target="_blank">#Peering</a> <a class="hashtag" href="https://pleroma.pch.net/tag/ixp" rel="nofollow noopener" target="_blank">#IXP</a> <a class="hashtag" href="https://pleroma.pch.net/tag/dnsresiliency" rel="nofollow noopener" target="_blank">#DNSresiliency</a>

Dendrobatus AzureusAs I am browsing through the settings in firefox I see the odd setting of using it's own DNS over https enabled. My settings should be copied over from the account I use and I know that I've **never** turned this setting on.I'm now on the SBC Pi5 running MX Linux Pi respin. My own dns config is perfectly fine and Im changing it back to my own local DNS.Why is the firefox team doing this? IS there any protective benifit from having this setting on? Are they snooping my data?The help file is here<a href="https://support.mozilla.org/en-US/kb/dns-over-https?as=u&utm_source=inproduct#w_what-is-a-local-provider" rel="nofollow noopener" translate="no" target="_blank">https://support.mozilla.org/en-US/kb/dns-over-https?as=u&utm_source=inproduct#w_what-is-a-local-provider</a><a href="https://mastodon.bsd.cafe/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a> <a href="https://mastodon.bsd.cafe/tags/AskFediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#AskFediverse</a> <a href="https://mastodon.bsd.cafe/tags/firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#firefox</a> <a href="https://mastodon.bsd.cafe/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> <a href="https://mastodon.bsd.cafe/tags/https" class="mention hashtag" rel="nofollow noopener" target="_blank">#https</a> <a href="https://mastodon.bsd.cafe/tags/port443" class="mention hashtag" rel="nofollow noopener" target="_blank">#port443</a> <a href="https://mastodon.bsd.cafe/tags/settings" class="mention hashtag" rel="nofollow noopener" target="_blank">#settings</a> <a href="https://mastodon.bsd.cafe/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>

Miek GiebenNew Msg layout and printing (dnsv2), <a href="https://mastodon.cloud/tags/go" class="mention hashtag" rel="nofollow noopener" target="_blank">#go</a> <a href="https://mastodon.cloud/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns</a> ; QUERY, status: NOERROR, id: 17759, flags: qr rd ra ad do ;; EDNS, version: 0, udp: 512 ;; QUESTION: 1, PSEUDO: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: miek.nl. IN A ;; PSEUDO SECTION: . CLASS0 NSID 6770646e732d616d73 ; ("gpdns-ams) ;; ANSWER SECTION: miek.nl. 14301 IN A 45.138.52.215

Notxor :esperanto:Acabo de configurar el router para tirar del DNS de esta instancia: <a href="https://rocksdns.ovh/site/" rel="nofollow noopener" translate="no" target="_blank">https://rocksdns.ovh/site/</a> y va de lujo<a href="https://tuiter.rocks/tags/tuiterrocks" class="mention hashtag" rel="nofollow noopener" target="_blank">#tuiterrocks</a> <a href="https://tuiter.rocks/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a>

Asheville CharlieMy fedifam nerds.. just a random reminder to check who/where your DNS is..<a href="https://mastodon.social/tags/internet" class="mention hashtag" rel="nofollow noopener" target="_blank">#internet</a> <a href="https://mastodon.social/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns</a>

Kathleen FitzpatrickI have been fighting with the process of setting up a server on my home network for what is now literally months. (I keep having to walk away from the project because of that whole “day job” thing, plus travel and so forth.) If anyone has advice to offer, it would not be unsolicited! <a href="https://kfitz.info/networking-continued/" rel="nofollow noopener" translate="no" target="_blank">https://kfitz.info/networking-continued/</a> <a href="https://hcommons.social/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://hcommons.social/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns</a> <a href="https://hcommons.social/tags/proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#proxmox</a> <a href="https://hcommons.social/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a>

Kevin Karhan :verified:Thx <a href="https://ohai.social/@lina" class="u-url mention" rel="nofollow noopener" target="_blank">@lina</a> for exposing the <a href="https://infosec.space/tags/Copyrightmafia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Copyrightmafia</a>'s <a href="https://infosec.space/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a>-based <a href="https://infosec.space/tags/internetcensorship" class="mention hashtag" rel="nofollow noopener" target="_blank">#internetcensorship</a>: <a href="https://cuiiliste.de" rel="nofollow noopener" translate="no" target="_blank">https://cuiiliste.de</a><ul><li>I really should test the <a href="https://infosec.space/tags/API" class="mention hashtag" rel="nofollow noopener" target="_blank">#API</a> more: <a href="https://api.cuiiliste.de" rel="nofollow noopener" translate="no" target="_blank">https://api.cuiiliste.de</a></li></ul>As for circumvention: Just use <a href="https://infosec.space/tags/OpenNIC" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenNIC</a>'s <a href="https://github.com/greyhat-academy/lists.d/blob/df41ea6a5320f0a895b801145efe0ea6d2e9ea33/dns.servers.list.tsv#L2" rel="nofollow noopener" target="_blank">DNS servers</a>...<ul><li>Personally <a href="https://lina.sh/blog/cuii-gives-up" rel="nofollow noopener" target="_blank">I'm not as enthusiastic</a> as to claim <a href="https://infosec.space/tags/CUIi" class="mention hashtag" rel="nofollow noopener" target="_blank">#CUIi</a> <a href="https://netzpolitik.org/2025/die-cuii-gibt-auf-fuer-netzsperren-braucht-es-jetzt-einen-gerichtsentscheid/" rel="nofollow noopener" target="_blank">is done</a> because not only ain't they forced to remove any blockages but also they marginally changed their process.</li></ul>The sheer <a href="https://infosec.space/tags/Zensursula" class="mention hashtag" rel="nofollow noopener" target="_blank">#Zensursula</a>-Style bullshit is the <a href="https://infosec.space/tags/IllicitActivity" class="mention hashtag" rel="nofollow noopener" target="_blank">#IllicitActivity</a>! <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#ISP</a>|s should have no right to interfere with any traffic (except to defend their own infrastructure from getting hacked) unless explicitly requested by customers to do so.<ul><li>And now <a href="https://infosec.space/tags/ISPs" class="mention hashtag" rel="nofollow noopener" target="_blank">#ISPs</a> like <a href="https://infosec.space/tags/O2" class="mention hashtag" rel="nofollow noopener" target="_blank">#O2</a> want to sell <a href="https://infosec.space/tags/TechIlliterate" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechIlliterate</a> <a href="https://infosec.space/tags/business" class="mention hashtag" rel="nofollow noopener" target="_blank">#business</a> clients the idea that fucking around with <a href="https://infosec.space/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> is somehow "<a href="https://infosec.space/tags/Cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cybersecurity</a>" for which they want to <a href="https://www.o2business.de/cloud-sicherheit/cybersicherheit/webguard/" rel="nofollow noopener" target="_blank">charge clients a premium and make it opt-out!</a> when <a href="https://mastodon.social/@quad9dns" class="u-url mention" rel="nofollow noopener" target="_blank">@quad9dns</a> offers the same <a href="https://quad9.net/service/threat-blocking/" rel="nofollow noopener" target="_blank">for free</a> [and I'm certain they just use <a href="https://infosec.space/tags/quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#quad9</a>'s filtered DNS and slap CUII's <a href="https://infosec.space/tags/blocklist" class="mention hashtag" rel="nofollow noopener" target="_blank">#blocklist</a> <a href="https://api.cuiiliste.de/blocked_domains" rel="nofollow noopener" target="_blank">on top.</a>]!</li></ul>I do wish <a href="https://mastodon.social/@ooni" class="u-url mention" rel="nofollow noopener" target="_blank">@ooni</a> would take a look at the <a href="https://api.cuiiliste.de/blocked_domains" rel="nofollow noopener" target="_blank">CUII blocklist</a> and add that to their <a href="https://infosec.space/tags/OONIprobe" class="mention hashtag" rel="nofollow noopener" target="_blank">#OONIprobe</a> to test for.

✍️ Eljo #MorpurgoMediaSo what happens when I enter a building that has Wi-Fi and routers set on DNS-x and my hardware has DNS-y?<a href="https://mastodon.nl/tags/question" class="mention hashtag" rel="nofollow noopener" target="_blank">#question</a> <a href="https://mastodon.nl/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a>

Mitex LeoRegistration of new .ONE domains is going up to $24.75 USD per year. 😕<a href="https://mitexleo.one/tags/Domain" class="mention hashtag" rel="nofollow noopener" target="_blank">#Domain</a> <a href="https://mitexleo.one/tags/dotone" class="mention hashtag" rel="nofollow noopener" target="_blank">#dotone</a> <a href="https://mitexleo.one/tags/internet" class="mention hashtag" rel="nofollow noopener" target="_blank">#internet</a> <a href="https://mitexleo.one/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns</a>

Recent searches

Search options

Administered by:

Server stats:

#dns