Lmst

I did another thing that was a first to me.

I created a #DNS zone; .pen, on my DNS server to translate Private Enterprise Numbers into their #OIDs.

The zone consists of three records; SOA, NS, and a DNAME record.

This is the first time that I've used a DNAME record and I've got to say it did exactly what I wanted it to do.

@ IN DNAME 1.4.1.6.3.1.oid.

So querying for <anything>.pen gets treated as if you queried for <anything>.1.4.1.6.3.1.oid.

So I can do something like the following to get information about a #PEN from my OID zone:

% dig txt 61926.pen
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) REDACTED(61926)}

Well I did a thing.

I created a #DNS zone; .oid, on my DNS server #OIDs.

I can now easily look up OID values with dig (et al.):

% dig +short txt 2.3.7.5.5.1.6.3.1.oid.

To look up OIS 1.3.6.1.5.5.7.3.2.

I also wrote a one* line shell script to make doing the lookups easier:

\dig +short txt $(echo ${1} | awk -F. '{for (C=NF; C>1; C--){printf "%s.", $C}; printf "%s.oid.", $1}') | sed 's/"//g' #awk

So I can now run:

% oidlookup 1.3.6.1.5.5.7.3.2

and get the following output:

{iso(1) identified-organization(3) dod(6) internet(1) security(5) mechanisms(5) pkix(7) kp(3) id-kp-clientAuth(2)}

WIP - Project Nova - Thrusterz 2
Recreation of the Planet 6 from the 8bit classic Thrust.

#OIDs