Does anybody else ever think how messed up it is that unless you go out of your way (or live in a very rural area), you are bombarded with ads for the entire time you are awake.
Ads on your phone
Ads on your TV
Ads on every place they can buy outside
Ads on almost every website
It is honestly exhausting, and I wonder what a world with heavily limited ads would look like.
Incidentally, the lack of ads is one of the very nice things about self hosting things, and being on fedi.
#Selfhosted for as many of the important things as I can!
But I also have to shoutout about #DNS + adblocking, like #BIND9 and #pihole and the many others which have sprung up. (Yes, you can use BIND as a network adblocker, and also get the rest of its power too.)
Pihole may be more-approachable (no, it does not require a raspberry pi. Yes, you can install it on your laptop and use it wherever you are computing.) I have not tried the alternatives, but I am sure some are better.
ugh i don't even know how to search for this properly
there's a domain that lists two DNS servers, one is fine, the second is a non-resolving hostname. it's not just not answering: it doesn't even resolve to an IP address.
(no, it's not just me, google DNS can't resolve the broken one either.)
if my instance of bind9 on my domain's DNS server tries the broken nameserver first, it obviously fails to resolve in any form.
the problem is that it does not proceed to try the server that I know is working, and it should.
i've told the domain's owner that their DNS is fucked up and how, but really, I shouldn't've ever noticed.
anybody got any ideas why bind9 isn't trying the second server? because this is dumb.
"apt update" on a Sunday night and my e-mail starts filling up with cron errors:
"Use of K* file pairs for HMAC is deprecated"
That -k syntax is still in the manual page, so I have no idea what happened. Looking at BIND 9 release notes the only thing which seems possibly related is this:
"The ability to read HMAC-MD5 key files, which was accidentally lost in BIND 9.18.8, has been restored."
But that is about restoring access, and Debian is at 9.18.19, so it should be fixed? 😭