Tootfinder

Microsoft's #Windows #DNS client survey: https://techcommunity.microsoft.com/t5/networking-blog/windows-dns-client-survey/ba-p/4122947
They seem particularly interested in responses to various DNS-over-* tech questions.

I talk a lot about blocking certain Internet services such as Dynamic DNS, but I realize that not everyone has a fancy DNS security service or NGFW that gives you an easy way to do this. If you don't have those, but do use Windows DNS, you can create a DNS Policy to create your own #DNS block list by running a simple PowerShell command on your DNS server:
Add-DnsServerQueryResolutionPolicy -Name "BlockListPolicy" -Action IGNORE -FQDN "EQ,*.duckdns.org" -PassThru
#cybersecurity

The French will be coming for the rootservers next. That won’t work.
Run your own recursive resolver. It’s easy. It's the way the net was meant to work.
#DNS https://infosec.exchange/@hotheadhacke

I just learned about #Postfix's #dnsblog daemon. The name seems a bit misleading. This is not an AI which blogs about DNS topics. 😉 It's the "Postfix DNS allow/denylist logger" and I assume the "blog" comes from "block logger" or so. 🤪

OH on slack:
> Warning: Godaddy silently cut access to their #DNS API unless you pay them more money. If you're using a #Godaddy domain with #letsencrypt or

Weekend Reads
* Biography of Tor #Tor #IPv6 #IoT #DNS #Deepfake #RIR

Microsoft announces Zero Trust DNS (ZTDNS). My quick, not-so-well-informed take is that it looks RPZ-like, but seemingly specific to Windows environments with all the bells, whistles, and functions that implies.
#DNS

🎯 Obtaining a locality domain
http://nguyen.cincinnati.oh.us/locality.html
#internet #dns

Not using free public DNS for #DNSBL queries has been a best practice forever, but they’ve tightened up a lot in the past few years. Using a free DQS account is a good idea even with a local caching recursing resolver, as it allows access to data sets that are not in any open-access list.
#Spam

Is anyone else experiencing #dns issues with #netcup right now?
One of my systems is hosted with them, with their (seemingly) default resolvers in /etc/resolv.conf:
46.38.225.230
46.38.252.230
I was working on the system when suddenly all of my DNS-requests for the subdomains…

Weekend Reads
* Rapid DNS zone updates #DNS #IETF #W3C #AI #BGP #SubseaCabling

Not using free public DNS for #DNSBL queries has been a best practice forever, but they’ve tightened up a lot in the past few years. Using a free DQS account is a good idea even with a local caching recursing resolver, as it allows access to data sets that are not in any open-access list.
#Spam

Sorry not sorry to all attendees who are fans of the #DNS haiku.

fellow geeks....
traceroute bad.horse
and wait for it...
#it #computer #geekHumor #DNS

Weekend Reads
* FCC open internet order analysis #FCC #DNS #ICANN #RustLang #DDoS

Weekend Reads
* DNS pulse attacks #DNS #TCP #FCC #BGP #ICANN #SSAC

Because I want to make sure that the probability of "It's probably #dns" is high enough I ended up setting up my own nameservers again.
Yes, I don't value my time, why do you ask?