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…
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…
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[] '…