Hello,
The other day I saw one of BitFolk's IP addresses in a log file and
wondered which host that was, so I did a reverse lookup and got:
2001-ba8-1f1-f284-0-0-0-2.autov6rev.bitfolk.space
which was useless to me.
It's quick to look this up and fix it of course, but I wondered how many
other such addresses I had forgotten to take care of the reverse DNS
for.
In order to answer that question, automatically and in bulk, I wrote
this tool:
https://github.com/grifferz/ptrcheck-rs
The answer, for bitfolk.com, was 1 A record and 4 AAAA records.
I ran it against every customer domain on BitFolk's secondary service
and found that 20.1% of customers domains contain host records with no
PTR.
When I added:
--badre 'autov6rev'
to catch unset BitFolk IPv6 reverse DNS, that percentage went up to
26.5% of customer zones. This is not a shaming. 😀 All but one of my own
zones had at least one broken/missing PTR.
I will make a few more improvements and then turn it into a Nagios check
plugin available on request.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Hi,
It seems that since about 0500Z today the Debian mirror CDN at
deb.debian.org has been rejecting requests from our apt-cacher with a
message like:
E: Failed to fetch http://apt-cacher.lon.bitfolk.com/debian/deb.debian.org/debian/dists/bullse… 421 Misdirected Request [IP: 2001:ba8:1f1:f079::2 80]
I am looking into this. I don't know what is wrong yet. If you are
urently needing to uodate or install new packages just disable use of
BitFolk;s apt0cacher by removing "apt-cacher.lon.bitfolk.com/debian/"
from every line of your sources.list file(s).
I suspect some unfortunate interaction between Debian CDN (Fastly?) and
apt-cacher, as other mirrors are still working fine through our
apt-cacher.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Something that I have noticed on my bitfolk box but not other Debian machines.
I am running Debian 12.7
When I go "sudo -s" it shows a new login on a different pts.
I logged in via ssh at 16.14 and then went: sudo -s
If I run "w" I now appear to be logged in twice (1.52 is the current time):
addw pts/0 2001:4d48:ad51:2 16:14 40.00s 0.02s 0.01s sudo -s
addw pts/1 2001:4d48:ad51:2 01:52 3.00s 0.00s 0.01s sudo -s
So I am now on a different tty and the old one shows idle time.
I get similar results if I run "who".
ps shows interesting results:
# ps -f
UID PID PPID C STIME TTY TIME CMD
root 28669 28644 0 01:52 pts/1 00:00:00 sudo -s
root 28670 28669 0 01:52 pts/1 00:00:00 /bin/bash
root 28979 28670 0 01:59 pts/1 00:00:00 ps -f
# ps -fp28644
UID PID PPID C STIME TTY TIME CMD
root 28644 1819 0 01:51 pts/0 00:00:00 sudo -s
What is happening ?
--
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256 https://www.phcomp.co.uk/
Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html
#include <std_disclaimer.h>
