v0.5.0 — third-level names through a wildcard

Names under a name

• A third-level name like www.chovy.hacker now resolves. It is asked of the registry as written, and a name the registry does not hold falls back to the owner's published *.chovy.hacker wildcard.
• * is a label only whole and only leftmost: f*.chovy.hacker and foo.*.hacker are not names the registry can be asked about.
• A sub-name that misses everywhere is NXDOMAIN rather than parked. Parking exists to explain that a name is for sale, and a sub-name has nothing to park to.
• The answer keeps the name that was asked, as a wildcard answer should — the wire codec writes the question's name into every owner field.

Also

• Resolve several names in one go (#17).
• Inspect published AAAA records, including on wildcards.

Note for moshcode

moshcode vendors this package as src/dns.mjs and guards the copy with a drift test against the published tarball, so this release is what lets that copy learn subdomains.

v0.4.1 — publish the resolver fix

Publishes the resolver fix from #15.

The fix merged yesterday but the version stayed at 0.4.0, so npm i @moshcoder/moshpit-dns kept installing a bridge that answered ANSWER: 0 for names that resolve perfectly well.

That authoritative-empty answer is the worst failure shape available: the client treats it as final, dig reports the name exists, and nothing logs an error — so it reads as "Moshpit is broken" with no thread to pull.

Upgrade: npm i -g @moshcoder/moshpit-dns@0.4.1

A running bridge is not restarted by upgrading the package — moshpit-dns disable then enable to pick it up.

v0.4.0 — the records command

Published as @moshcoder/moshpit-dns@0.4.0.

Added

moshpit-dns records <name> [CNAME|MX|TXT] [--json] — inspect the records published for a Moshpit name (#12).

• optional record-type filtering
• stable JSON output for scripts and monitoring
• sanitizes malformed registry records, and tells a parked name apart from an unregistered one

moshpit-dns records california.oranges MX --json | jq '.records[]'

Note

records merged to main some time before this release but was never published, because the version stayed at 0.3.0 — so npm i kept installing a build with no records subcommand. Verified against the published tarball this time, not the source tree.

This is the first tagged release in this repo; earlier versions were published untagged.