Skip to content

v0.13.0 — moshcode dns

Choose a tag to compare

@ralyodio ralyodio released this 31 Jul 05:14
· 224 commits to main since this release
a280fc5

moshcode dns — resolve Moshpit names on the machine, not just in the browser.

The registry speaks HTTP, not DNS: pit.moshcode.sh answers /api/moshpit/resolve and nothing listens on port 53, so curl https://california.oranges/ failed on any server. A browser extension can't fix that — redirecting tabs isn't resolution.

moshcode dns tlds              # the TLDs claimed in the Pit
moshcode dns resolve <name>    # what a name resolves to, and why
moshcode dns start             # run the resolver
moshcode dns install [--write] # systemd-resolved / dnsmasq config

Claimed-but-unpointed names answer with the parking host, so they explain themselves instead of returning NXDOMAIN. A registry that is unreachable still returns NXDOMAIN — an outage must not silently point every Moshpit name on the machine at a parking page.

17 new tests including a real UDP round-trip; full suite 331 pass / 0 fail.