Sigmoid Social

slamp<a href="https://social.vivaldi.net/@sesivany" class="u-url mention" rel="nofollow noopener" target="_blank">@sesivany</a> Based in south of France : <a href="https://hachyderm.io/tags/cloudfare" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloudfare</a> 29ms, <a href="https://hachyderm.io/tags/quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#quad9</a> 41ms. I will test <a href="https://hachyderm.io/tags/dns4eu" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns4eu</a> !

Jiří EischmannOne advantage of using <a href="https://social.vivaldi.net/tags/AdGuardHome" class="mention hashtag" rel="nofollow noopener" target="_blank">#AdGuardHome</a> is that it provides statistics on the responsiveness of public DNS providers. For me, <a href="https://social.vivaldi.net/tags/DNS4EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS4EU</a> is by far the fastest (10 ms). Perhaps it's because of their geographical proximity, as they're also based in Czechia. The slowest has been <a href="https://social.vivaldi.net/tags/quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#quad9</a> at 500 ms. I have no idea why.I'm also glad to learn that DoH doesn't have a significant speed penalty. It's 12 ms versus 10 ms for DNS4EU. So you don't have to trade privacy for responsiveness.What has been your experience with <a href="https://social.vivaldi.net/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> providers based in Europe? Do you have any recommendations? I'm interested in unfiltered DNS because I do the filtering in AdGuard Home.

MichelNutzt ihr die <a href="https://norden.social/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> Server eurem <a href="https://norden.social/tags/Zugangsprovider" class="mention hashtag" rel="nofollow noopener" target="_blank">#Zugangsprovider</a>, <a href="https://norden.social/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a> oder Andere? Habe jetzt mal auf <a href="https://norden.social/tags/quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#quad9</a> umgestellt Habt ihr alternative Empfehlungen? <a href="https://norden.social/tags/Datenschutz" class="mention hashtag" rel="nofollow noopener" target="_blank">#Datenschutz</a> <a href="https://norden.social/tags/Spam" class="mention hashtag" rel="nofollow noopener" target="_blank">#Spam</a> <a href="https://norden.social/tags/Pishing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pishing</a><a href="https://quad9.net/de/" rel="nofollow noopener" translate="no" target="_blank">https://quad9.net/de/</a>

Nikhil 🐧<a href="https://social.linux.pizza/@selea" class="u-url mention" rel="nofollow noopener" target="_blank">@selea</a> <a href="https://mastodon.social/@quad9dns" class="u-url mention" rel="nofollow noopener" target="_blank">@quad9dns</a> I spent like two weeks with <a href="https://social.linux.pizza/tags/dns0" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns0</a> and it was unbearable. I'm now back on quad9 since about a week and the difference in speed is insane!Props to <a href="https://social.linux.pizza/tags/quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#quad9</a>!I hope that linux.pizza doesn't get flagged again 🙈😅

C++ Wage Slave<a href="https://infosec.space/tags/Quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#Quad9</a> seems to be in trouble: <a href="https://downdetector.co.uk/status/quad9/" rel="nofollow noopener" translate="no" target="_blank">https://downdetector.co.uk/status/quad9/</a>Right now, I'm seeing a weird mix of services that still work and others that don't. I'm expecting that to degrade as the afternoon wears on unless they can bring it up again soonish.<a href="https://infosec.space/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a>

Nikhil 🐧I might go back to <a href="https://social.linux.pizza/tags/quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#quad9</a> 😑 <a href="https://social.linux.pizza/tags/dns0" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns0</a> is just incredibly slow to the point where web browsing stops working. Getting timeouts sometimes when loading different random news websites. Refreshing once or twice solves the problem but this is really not a good state

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.

Dominik<a href="https://mastodon.social/@Tutanota" class="u-url mention" rel="nofollow noopener" target="_blank">@Tutanota</a> <a href="https://mastodon.neat.computer/@jonah" class="u-url mention" rel="nofollow noopener" target="_blank">@jonah</a> <a href="https://infosec.exchange/@chillybot" class="u-url mention" rel="nofollow noopener" target="_blank">@chillybot</a> People who know Switzerland have often said that it is a false assumption that privacy is more secure there. Too bad for the services like <a href="https://social.librem.one/tags/Quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#Quad9</a> that have made efforts to establish themselves there. <a href="https://mastodon.social/@quad9dns" class="u-url mention" rel="nofollow noopener" target="_blank">@quad9dns</a> Only the fundamental non-storage of personal data from the outset and the non-storage of logs can help.

Frehi<a href="https://infosec.exchange/@malmoeb" class="u-url mention" rel="nofollow noopener" target="_blank">@malmoeb</a> Thanks. The domain is blocked by <a href="https://fosstodon.org/tags/dns0" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns0</a>. <a href="https://fosstodon.org/tags/Cloudflare" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cloudflare</a> 1.1.1.2, <a href="https://fosstodon.org/tags/DNS4EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS4EU</a> and <a href="https://fosstodon.org/tags/quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#quad9</a> resolve it successfully.

Dataplane.orgThe Internet Last Week* Cairo telecom building fire <a href="https://noc.social/@cloudflareradar/114812834265048251" rel="nofollow noopener" target="_blank">https://noc.social/@cloudflareradar/114812834265048251</a> <a href="https://mastodon.social/@IODA/114817830857702130" rel="nofollow noopener" target="_blank">https://mastodon.social/@IODA/114817830857702130</a> <a href="https://mastodon.social/@netblocks/114813291615533273" rel="nofollow noopener" target="_blank">https://mastodon.social/@netblocks/114813291615533273</a> <a href="https://pulse.internetsociety.org/blog/egypt-internet-outage-another-example-of-the-need-to-spread-your-risk" rel="nofollow noopener" target="_blank">https://pulse.internetsociety.org/blog/egypt-internet-outage-another-example-of-the-need-to-spread-your-risk</a> <a href="https://www.nytimes.com/2025/07/11/world/middleeast/egypt-fire-cairo-telecom.html" rel="nofollow noopener" target="_blank">https://www.nytimes.com/2025/07/11/world/middleeast/egypt-fire-cairo-telecom.html</a> * OVH RBX dedicated servers outage <a href="https://bare-metal-servers.status-ovhcloud.com/incidents/j3xcv287w1wn" rel="nofollow noopener" target="_blank">https://bare-metal-servers.status-ovhcloud.com/incidents/j3xcv287w1wn</a> * St Petersburg Internet disruption <a href="https://therecord.media/russia-saint-petersburg-outage-drones" rel="nofollow noopener" target="_blank">https://therecord.media/russia-saint-petersburg-outage-drones</a> * Quad9 top500 domains <a href="https://github.com/Quad9DNS/quad9-domains-top500" rel="nofollow noopener" target="_blank">https://github.com/Quad9DNS/quad9-domains-top500</a><a href="https://noc.social/tags/Cairo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cairo</a> <a href="https://noc.social/tags/OVH" class="mention hashtag" rel="nofollow noopener" target="_blank">#OVH</a> <a href="https://noc.social/tags/RU" class="mention hashtag" rel="nofollow noopener" target="_blank">#RU</a> <a href="https://noc.social/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> <a href="https://noc.social/tags/Quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#Quad9</a> <a href="https://noc.social/tags/Outages" class="mention hashtag" rel="nofollow noopener" target="_blank">#Outages</a>

Gea-Suan Lin<a href="https://blog.gslin.org/archives/2025/07/12/12504/quad9-%e6%8a%8a%e6%9c%80%e5%b8%b8%e8%a2%ab-dns-query-%e7%9a%84%e7%b6%b2%e5%9f%9f%e5%85%ac%e9%96%8b-top-500/" rel="nofollow noopener" translate="no" target="_blank">https://blog.gslin.org/archives/2025/07/12/12504/quad9-%e6%8a%8a%e6%9c%80%e5%b8%b8%e8%a2%ab-dns-query-%e7%9a%84%e7%b6%b2%e5%9f%9f%e5%85%ac%e9%96%8b-top-500/</a>Quad9 把最常被 DNS query 的網域公開 (Top 500)<a href="https://abpe.org/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns</a> <a href="https://abpe.org/tags/domain" class="mention hashtag" rel="nofollow noopener" target="_blank">#domain</a> <a href="https://abpe.org/tags/quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#quad9</a> <a href="https://abpe.org/tags/query" class="mention hashtag" rel="nofollow noopener" target="_blank">#query</a> <a href="https://abpe.org/tags/top" class="mention hashtag" rel="nofollow noopener" target="_blank">#top</a>

stfnI switched my PiHole upstream DNS from Google to Quad9. Let's see how it goes and if I see any difference.One less Google service in my house :zawadiaka:<a href="https://fedi.stfn.pl/tags/pihole" class="mention hashtag" rel="nofollow noopener" target="_blank">#pihole</a> <a href="https://fedi.stfn.pl/tags/quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#quad9</a>

BjoernAusGE<a href="https://mastodon.social/@quad9dns" class="u-url mention" rel="nofollow noopener" target="_blank">@quad9dns</a> why do you have to break good things by jumping on the AI hype train. Just this morning i thought: i dont need <a href="https://social.sengotta.net/tags/dns4eu" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns4eu</a> because i already use <a href="https://social.sengotta.net/tags/quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#quad9</a> Yeah i might be think about that again.

Max Resing<a href="https://social.server17.net/@earl" class="u-url mention" rel="nofollow noopener" target="_blank">@earl</a> - I lurked on some of the working group meetings and posted about it occasionally. Some immediate thoughts are also in my timeline. Interestingly, <a href="https://infosec.exchange/tags/DNS4EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS4EU</a> does not block <a href="https://infosec.exchange/tags/Russian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Russian</a> news outlets, that are sanctioned by the <a href="https://infosec.exchange/tags/EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#EU</a>. Also, the performance on the threat protected service is noticably slower than the unfiltered service. The unfiltered service in en par with <a href="https://infosec.exchange/tags/Cloudflare" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cloudflare</a> or <a href="https://infosec.exchange/tags/Quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#Quad9</a> Hope that helps, have fun with the project!

Max ResingAs of today, <a href="https://infosec.exchange/tags/DNS4EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS4EU</a> is live. A project that started somewhat of 3 years ago. Now, it's public and live, promising secure and resilient service to <a href="https://infosec.exchange/tags/EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#EU</a> citizens, strengthening the <a href="https://infosec.exchange/tags/European" class="mention hashtag" rel="nofollow noopener" target="_blank">#European</a> <a href="https://infosec.exchange/tags/cyberresiliency" class="mention hashtag" rel="nofollow noopener" target="_blank">#cyberresiliency</a> .More <a href="https://www.joindns4.eu/learn/dns4eu-public-service-launched" rel="nofollow noopener" target="_blank">here</a>.I queried my own domain name out of interest. The EU protective resolver resolves in 340 ms, whereas <a href="https://infosec.exchange/tags/Cloudflare" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cloudflare</a> and <a href="https://infosec.exchange/tags/Quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#Quad9</a> both resolve within 50 ms.The unfiltered resolution however resolves within 50 ms as well, revealing that the filtering introduces a slight performance penalty.<a href="https://infosec.exchange/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> <a href="https://infosec.exchange/tags/Nameserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nameserver</a>

FrederikDNS4EU, DNS0, Quad9: review of European public DNS resolversThis week the DNS4EU initiative launched its public European DNS resolvers. I already wrote an article about public DNS resolvers but it’s time for an update. Not only do we have DNS4eu now, but with DNS0 there is another public DNS resolver focused on Europe available. And of course there is still Quad9, which has servers worldwide, but is a foundation with headquarters in […]<a href="https://blog.frehi.be/2025/06/08/dns4eu-dns0-quad9-review-of-public-european-dns-resolvers/" rel="nofollow noopener" translate="no" target="_blank">https://blog.frehi.be/2025/06/08/dns4eu-dns0-quad9-review-of-public-european-dns-resolvers/</a><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://blog.frehi.be/tag/dns/" target="_blank">#DNS</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://blog.frehi.be/tag/dns0/" target="_blank">#DNS0</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://blog.frehi.be/tag/dns4eu/" target="_blank">#DNS4EU</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://blog.frehi.be/tag/privacy/" target="_blank">#privacy</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://blog.frehi.be/tag/quad9/" target="_blank">#Quad9</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://blog.frehi.be/tag/security/" target="_blank">#security</a>

Kevin Karhan :verified:<a href="https://mastodon.social/@quad9dns" class="u-url mention" rel="nofollow noopener" target="_blank">@quad9dns</a> <a href="https://social.g2od.ch/@rapha3l" class="u-url mention" rel="nofollow noopener" target="_blank">@rapha3l</a> <a href="https://waldvogel.family/@marcel" class="u-url mention" rel="nofollow noopener" target="_blank">@marcel</a> <a href="https://ioc.exchange/@abuse_ch" class="u-url mention" rel="nofollow noopener" target="_blank">@abuse_ch</a> Also this only applies to the <code>filtered</code> & <code>secured</code> <a href="https://infosec.space/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> servers.<ul><li>default filtered DNS by <a href="https://infosec.space/tags/Quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#Quad9</a><pre><code>9.9.9.9 149.112.112.112 2620:fe::fe 2620:fe::9 </code></pre></li><li>secured quad9 servers<pre><code>9.9.9.11 149.112.112.11 2620:fe::11 2620:fe::fe:11 </code></pre></li><li>unfiltered quad9 DNS<pre><code>9.9.9.10 149.112.112.10 2620:fe::10 2620:fe::fe:10 </code></pre></li></ul>See <a href="https://www.quad9.net/service/service-addresses-and-features" rel="nofollow noopener" translate="no" target="_blank">https://www.quad9.net/service/service-addresses-and-features</a> for details.The unfiltered ones do not filter any results, thus they should only be used for those that i.e. filter their results themselves.

Marcel Waldvogel6️⃣ <a href="https://waldvogel.family/tags/Quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#Quad9</a> hat eine Grafik, die den Einbruch des Internetverkehrs in Spanien und Portugal gestern visualisiert.Ihre drei Serverstandorte waren scheinbar mit funktionierender Notstromversorgung ausgestattet. Im Gegensatz zu – mutmasslich – diversen Internetanbietern. Wie im Wallis werden da jetzt wahrscheinlich die Notfallszenarien an vielen Stellen nochmals überdacht. <a href="https://mastodon.social/@quad9dns/114416276417809952" rel="nofollow noopener" translate="no" target="_blank">https://mastodon.social/@quad9dns/114416276417809952</a>

Max ResingReceived an email by the <a href="https://infosec.exchange/tags/NANOG" class="mention hashtag" rel="nofollow noopener" target="_blank">#NANOG</a> mailing list in which they raise a pretty concerning thing: Apparently, <a href="https://infosec.exchange/tags/Spain" class="mention hashtag" rel="nofollow noopener" target="_blank">#Spain</a> started to intercept or nullroute certain IP addresses of <a href="https://infosec.exchange/tags/CDN" class="mention hashtag" rel="nofollow noopener" target="_blank">#CDN</a> providers. The intent is to fight <a href="https://infosec.exchange/tags/piracy" class="mention hashtag" rel="nofollow noopener" target="_blank">#piracy</a> during <a href="https://infosec.exchange/tags/football" class="mention hashtag" rel="nofollow noopener" target="_blank">#football</a> matches.Do the people who pass the list of IP addresses even understand the significance of blocking a bunch of <a href="https://infosec.exchange/tags/CDN" class="mention hashtag" rel="nofollow noopener" target="_blank">#CDN</a> networks of various providers? Seriously?! It <a href="https://infosec.exchange/tags/censors" class="mention hashtag" rel="nofollow noopener" target="_blank">#censors</a> access to tens of thousands of legitimate <a href="https://infosec.exchange/tags/websites" class="mention hashtag" rel="nofollow noopener" target="_blank">#websites</a> which is blatantly accepted as a <a href="https://infosec.exchange/tags/collateral" class="mention hashtag" rel="nofollow noopener" target="_blank">#collateral</a> to help out some shady sports association in their <a href="https://infosec.exchange/tags/copyright" class="mention hashtag" rel="nofollow noopener" target="_blank">#copyright</a>?How much shadier can a decision be? Since this is a thing, maybe they can think about taking down entire regions in Spain the next football match?The amount of collateral damage in the name of copyright is ridiculous. The <a href="https://infosec.exchange/tags/EuropeanUnion" class="mention hashtag" rel="nofollow noopener" target="_blank">#EuropeanUnion</a> really has to step-up their game in addressing those concerning developments. I read about multiple such blatant decisions so far. Eyeing at you, <a href="https://infosec.exchange/tags/Quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#Quad9</a> and <a href="https://infosec.exchange/tags/Sony" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sony</a>...<a href="https://infosec.exchange/tags/copyrightinfringement" class="mention hashtag" rel="nofollow noopener" target="_blank">#copyrightinfringement</a> <a href="https://infosec.exchange/tags/LaLiga" class="mention hashtag" rel="nofollow noopener" target="_blank">#LaLiga</a> <a href="https://infosec.exchange/tags/digitalsovereignty" class="mention hashtag" rel="nofollow noopener" target="_blank">#digitalsovereignty</a> <a href="https://infosec.exchange/tags/eu" class="mention hashtag" rel="nofollow noopener" target="_blank">#eu</a> <a href="https://infosec.exchange/tags/digitaleurope" class="mention hashtag" rel="nofollow noopener" target="_blank">#digitaleurope</a> <a href="https://infosec.exchange/tags/corporatepower" class="mention hashtag" rel="nofollow noopener" target="_blank">#corporatepower</a>

Yann Büchau :nixos:Losing my mind over <a href="https://fosstodon.org/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> bullshit. Seems that DNS servers (<a href="https://fosstodon.org/tags/Quad9" class="mention hashtag" rel="nofollow noopener" target="_blank">#Quad9</a>) return different answers depending on the connection method, with built-in randomness.dig +tcp <domain> @9.9.9.9 → always correct IP ✅Anything else, no +tcp or +edns=0, +bufsize=4096 returns either the outdated or the correct IP, less erratic without edns and smaller bufsize. 🤡 🤪So I guess I somehow need to d̶i̶s̶a̶b̶l̶e̶ ̶e̶d̶n̶s̶ o̶r̶ ̶c̶o̶n̶f̶i̶g̶u̶r̶e̶ ̶"̶m̶y̶ ̶D̶N̶S̶"̶ ̶t̶o̶ ̶o̶n̶l̶y̶ ̶q̶u̶e̶r̶y̶ ̶v̶i̶a̶ ̶T̶C̶P̶.̶ use a better DNS server.

Recent searches

Search options

Administered by:

Server stats:

#quad9