Operators hit DNS as the first wall when they stand up a mail server, and after the install the records live in a file whose path you have to remember. This adds one command for them.
inbuxa dns prints the dns.zone the install already wrote — no key, no server call. For most domains that never goes stale.
inbuxa dns --refresh --key - reads the records live from the running server (loopback, same as certs), so a rotated DKIM key or anything that changed since the install shows up; it also refreshes the saved copy.
The records are the MX/SPF/DKIM/DMARC/SRV/MTA-STS/autoconfig set the server already computes (x:Domain/get dnsZoneFile); nothing new is generated here. A --local or server-not-here install says so and stops. --domain covers pre-2026.10.13 installs that didn't record the domain.
New apply.FetchDNSZone wraps the loopback client + domain lookup; dnsCmd is the CLI. Usage and a flag-parsing test added. stdlib-only; gofmt, vet (amd64+arm64) and go test all pass.
Operators hit DNS as the first wall when they stand up a mail server, and after the install the records live in a file whose path you have to remember. This adds one command for them.
- `inbuxa dns` prints the `dns.zone` the install already wrote — no key, no server call. For most domains that never goes stale.
- `inbuxa dns --refresh --key -` reads the records live from the running server (loopback, same as `certs`), so a rotated DKIM key or anything that changed since the install shows up; it also refreshes the saved copy.
The records are the MX/SPF/DKIM/DMARC/SRV/MTA-STS/autoconfig set the server already computes (`x:Domain/get dnsZoneFile`); nothing new is generated here. A `--local` or server-not-here install says so and stops. `--domain` covers pre-2026.10.13 installs that didn't record the domain.
New `apply.FetchDNSZone` wraps the loopback client + domain lookup; `dnsCmd` is the CLI. Usage and a flag-parsing test added. stdlib-only; gofmt, vet (amd64+arm64) and `go test` all pass.
By default it prints the dns.zone the install already wrote, which needs
no key and, for most domains, never goes stale. --refresh --key - reads
the records live from the running server instead, so a rotated DKIM key
or a record that changed since the install shows up, and refreshes the
saved copy.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Operators hit DNS as the first wall when they stand up a mail server, and after the install the records live in a file whose path you have to remember. This adds one command for them.
inbuxa dnsprints thedns.zonethe install already wrote — no key, no server call. For most domains that never goes stale.inbuxa dns --refresh --key -reads the records live from the running server (loopback, same ascerts), so a rotated DKIM key or anything that changed since the install shows up; it also refreshes the saved copy.The records are the MX/SPF/DKIM/DMARC/SRV/MTA-STS/autoconfig set the server already computes (
x:Domain/get dnsZoneFile); nothing new is generated here. A--localor server-not-here install says so and stops.--domaincovers pre-2026.10.13 installs that didn't record the domain.New
apply.FetchDNSZonewraps the loopback client + domain lookup;dnsCmdis the CLI. Usage and a flag-parsing test added. stdlib-only; gofmt, vet (amd64+arm64) andgo testall pass.72a8681510to4210158481