I didn't compile the tool, even though it looks useful.
Question:
Does it _actually_ render the flame in your terminal?
How long did it take you to look up the unicode character (assuming that is what it is) for that?
Very nice touch indeed! Love it.
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:
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
_______________________________________________
