non voodoo caa records in bind9

Really gay and corrupt

Nothing to do with flying but tls certificates [my blog] anyhow i discovered that debian [my blog] now supports these records by providing the more up to date bind release so you do not have to

zoo.	IN	TYPE257	\# 8 000569737375653B

but text

;; ANSWER SECTION:
zoo. 38400 IN CAA 0 iodef “mailto:abuse@zoo.”
zoo.net. 38400 IN CAA 0 issue “letsencrypt.org”

now works.

Anyhow type 257 records still work and one day i will convert them to the more readable text format into the zone file in the voodoo zones that have them.

Since most people have never heard of a caa record its kind of a good place to stop this nonsense.

raspberry pi os assumption fail

I like the pi zero [my blog] – but it has no wifi by default* so when raspberian tries and runs this.

cat /etc/profile.d/wifi-check.sh.off ( export TEXTDOMAIN=wifi-check . gettext.sh if [ ! -x /usr/sbin/rfkill ] || [ ! -c /dev/rfkill ]; then exit 0 fi if ! /usr/sbin/rfkill list wifi | grep -q "Soft blocked: yes" ; then exit 0 fi echo /usr/bin/gettext -s "Wi-Fi is currently blocked by rfkill." /usr/bin/gettext -s "Use raspi-config to set the country before use." echo )

Has no flying chickens chance in hell of working.   Being helpful is nice but well try harder.

Checking /proc/device-tree/model for exceptions in the script may help but i have yet to patch or submit the bash file.

I guess the zero is easy to consider legacy.

*it can be added as a user thing not the zero w model

arm hardware uptime wow

impressive for a pi zero [my blog]. Having no wifi networking means this is very much possible unlike the iffy pi3 wireless lan which seems to require reboots way more often or it loses connection to the whole network stack.

05:05:01 up 102 days, 19:14,
Linux monkeyhouse01 4.19.97+ #1294 Thu Jan 30 13:10:54 GMT 2020 armv6l GNU/Linux
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 10 (buster)
Release: 10
Codename: buster

I guess one day i will reboot the zero – has not happened at time of posting this, or we have a ‘fusebox malfunction‘ [my blog].

debian 10.4

Is out [my blog] and seems good, apt the package manager now asks about duplicate locations when running as our server is old it certainly has a history of upgrades and it also asked to replace postfix in /etc/init.d

I have not had any nightmares so no major problems here.  Cups loves making local raw printers stil but that artifice is known of and easily fixed if irritating..

fixing opendmarc import

In this [my blog] I was getting this

failed to insert policy data

So i dug about and discovered that the requests table now has a field policy in it but instead of being not null should be set to zero [0] in one of those more up to date guides in the sql.

Being bored i changed the table.  First impression seemed to be acceptable on reading the import file text into mysql.

I still note the /run/opendmarc path is is getting warned about on daemon restart.

I got around to it eventually

linux bug reporting means email spam

scumbag spammer Robert Soloway

Occasionally i find bugs in the zoo’s distro which i can work around  and on a 10+ year server that’s fairly easy to achieve and report the issue.

I even sometimes provide a fix and send it

Using a real email address means spam for non package related issues like bitcoin and apparently means i signed up on numerous email lists that i dont remember since the gmail account i used is very occasionally logged into and not the zoos primary email address.

Oh well email spam has always been full of scum like Robert Soloway so next time some marketer whines about how hard it is to email ponzi schemes like bitcoin [my blog] remember me and my spam folder on gmail.

I am glad i did not use the ‘real’ email address here at the zoo although thats very well protected.

apt listbugs throws its toys out of the pram

I installed it on a test machine. It ran fine for a month or so and then bugs.debian.org died

Retrieving bug reports… 0% Fail
Error retrieving bug reports from the server with the following error message:
E: getaddrinfo: Temporary failure in name resolution (bugs.debian.org:80)
It appears that your network connection is down. Check network configuration and try again
Retry downloading bug information? [Y/n] Y
One package at a time? [Y/n] Y
One bug report at a time? [Y/n] Y
Fail
Error retrieving bug reports from the server with the following error message:
E: getaddrinfo: Temporary failure in name resolution (bugs.debian.org:80)
It appears that your network connection is down. Check network configuration and try again

Perhaps not the wisest install i did and not good on production servers.

‘amazing’ debian uptimes in the zoo

50 days + [my blog]  i do restart services weekly via cron but since kernels are not being upgraded and the uptime would have been more if the metres [my blog] where not had to be replaced.

Stretch the old version was usually up for thirty days before an kernel upgrade required a reboot .  While these times are not that impressive remember i am upgrading software not simply running linux at a certain point of time.

I do not object to server reboots.