dnsglobe 0.5.0 - #297702
Merged
Merged
Conversation
daeho-ro
approved these changes
Aug 8, 2026
Contributor
|
🤖 An automated task has requested bottles to be published to this PR. Caution Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Created by
brew bumpCreated with
brew bump-formula-pr.Details
release notes
anything that matters: resolver IPs are shown in full, the numeric columns
(Ping, TTL, Exp) are right-aligned so their digits line up, units that the
header already implies are gone, and where there isn't room for the
spelled-out status the verdict moves to a glyph in the left margin
(
✓ ≠ ! ↻ ∅ ✗) — one place to scan for failures. The round-trip column isnow headed
Ping(it wasTime). Wider terminals are unchanged: they keepthe status word, the same answer column and the same map/globe thresholds.
--oncematches: it prints the same name/location/IP column widths as theTUI and right-aligns its TTL, so the two views line up.
(#33,
#40)
(
59s,1m,59m,1h,23h,1d,99d). A whole column of secondsticking out of unison was a distraction, and above a minute the exact
second never changed what you'd do. The TTL advisory notes still quote the
precise figure (
TTL ≈ 2h23m).(#33,
#40)
the table, and on the
not a domain namelabel under a malformed input —rather than red text, which went washed-out on terminal themes with a
mid-toned background (macOS Terminal's "Ocean"). Only the marker is
filled — error messages, map dots, the propagation gauge and slow ping
times keep the plain red, so the table doesn't turn into a wall of red
bars.
theme.erroraccepts the new"<fg> on <bg>"form (for exampleerror = "black on 208"); a plain color still works and means no badge.(#33,
#40)
first — a standard EDNS option servers answer with their own node name —
and only falls back to the old operator-specific
id.serverprobes whenthat names no place. More resolvers report where they actually answered
from: Lumen shows
→JFK, CIRA Canadian Shield→YYZ, DNS4EU→AMSandDNS.SB
→KIXwhere they used to show only the operator's home region.Resolvers you add yourself in the config file can now report a site too,
since NSID needs no per-operator support, and Google's site takes one
query instead of two. Nothing that already resolved to a site changed.
(#36,
#39)
Fixed
failing on every resolver with
protocol error: Label contains invalid character. Underscores are legal anywhere in a DNS label — theletter-digit-hyphen rule is about hostnames, not the DNS wire format — so
the delegated SPF/DMARC hosts that EasyDMARC, Valimail and friends generate
(
_spf.514_ax._d.example.com) now resolve like they do indig. Defaultand
--ecsruns accept exactly the same set of names; previously only--ecshandled these.(#34,
#37)
characters) is now reported once — as a startup error for a name given on
the command line, or in place of the propagation gauge for one typed in the
TUI — instead of filling the table with one identical error per resolver,
which read like a network outage.
(#37)
report the longest TTL any agreeing resolver returned, so one resolver
handing back an invented 8423s turned a 300s zone into "TTL ≈ 2h23m" and
advised lowering a TTL that was already low. The estimate now ignores
reports wildly out of line with the rest of the fleet (never more than a
tenth of it), and any resolver that reported one is named on the note line
with what it claims — that cache really will serve the old answer after a
change, and it is worth knowing which one it is.
(#35,
#38)
Install dnsglobe 0.5.0
Install prebuilt binaries via shell script
Install prebuilt binaries via Homebrew
Download dnsglobe 0.5.0
View the full release notes at https://github.com/514-labs/dnsglobe/releases/tag/v0.5.0.