Repository navigation
feat(ui): look up public addresses on IP sites - #540
Merged
Merged
Conversation
Owner
Author
Connection menu (1280: before / after; 390 after)
DNS query cards
DNS log detail
|
Zakkaus
force-pushed
the
feat/ipinfo-link
branch
from
October 9, 2026 10:46
a2773ac to
454b80a
Compare
Owner
Author
|
Updated DNS screenshots: the address itself is the link, and the per-answer "新增規則" buttons line up on the right. DNS query cards (before / after)
DNS log detail (before / after)
|
Zakkaus
force-pushed
the
feat/ipinfo-link
branch
from
October 9, 2026 11:02
454b80a to
07ea06f
Compare
Owner
Author
|
Updated: clicking a public address opens a popover to choose the lookup site. The ⋮ menu item is gone. DNS query card (closed / open)
DNS log detail (open)
Connection detail (closed / open)
|
Zakkaus
changed the title
Zakkaus
force-pushed
the
feat/ipinfo-link
branch
from
October 9, 2026 11:20
07ea06f to
7644af4
Compare
Owner
Author
|
Updated: the lookup opens a menu, DNS answers lead with the address (type and TTL after it), and the destination trigger covers ip:port. Light / dark. DNS log detail
DNS query card
Connection detail
Lookup menu
|
Clicking a public address in the connection details or a DNS answer opens a menu of ipinfo.io, ipapi.is, ip-api.com and bgp.he.net. The chosen site opens in a new tab without a referrer; nothing is requested before that. DNS answers now lead with the record data, followed by the type and TTL, and show the owner name only when it differs from the name asked for.
Zakkaus
force-pushed
the
feat/ipinfo-link
branch
from
October 9, 2026 11:35
7644af4 to
c407e49
Compare
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
1 participant
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.
Problem
There is no way to see who owns a destination or DNS answer address. Looking it up inside doona would mean either new honk API surface or doona fetching data from a third party in the background.
How
ip:port) and in DNS query cards and log details (A/AAAA answers) becomes a trigger. Clicking it opens a menu that says the chosen site opens in a new tab and receives the address, and lists ipinfo.io, ipapi.is, ip-api.com and bgp.he.net.rel="noreferrer". Nothing is requested before the user picks a site, so there is no setting.isPublicIpexcludes private, loopback, link-local, CGNAT, ULA, multicast and reserved ranges, including IPv4-mapped IPv6. Documentation ranges stay clickable so the demo shows the feature.Net lines: src +120, unit +128, e2e +112, css +51.
Verified
pnpm typecheck,lint,format:check,check:i18n,check:size,test(3,743 passed).