Skip to content

fix(domains): explain "Points to another address" on the Domains page - #63

Merged
agentHits merged 1 commit into
AgentHits-Devfrom
fix/domains-dns-hint
Oct 13, 2026
Merged

agentHits merged 1 commit into
AgentHits-Devfrom
fix/domains-dns-hint

Conversation

@agentHits

Copy link
Copy Markdown
Owner

Why

On a server that sits behind a load balancer, every domain resolves to the balancer's address, so the DNS column of the Domains page shows a yellow "Points to another address" for all of them. The statement is correct: the panel's stored address is the server's own, and the domains resolve to a different one. But it reads like a misconfiguration, and nothing on the page says otherwise.

What changed

The "Points to another address" status now has a short note under it: this is expected when a load balancer, CDN or proxy stands in front of the server, and the page cannot check where that address forwards to. The status itself, its colour and the comparison rule are unchanged; no other status got a note.

Checks

  • tsc --noEmit for the app and biome check: clean.
  • Not checked in a browser.

🤖 Generated with Claude Code

When a load balancer, CDN or proxy stands in front of the server, every
domain resolves to that front address and the DNS column says "Points to
another address" for all of them. That is true, but it reads like a
fault. The status now carries a short note that this is expected with
such a front and that the page cannot check where the address forwards.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@agentHits
agentHits merged commit cbda9d4 into AgentHits-Dev Oct 13, 2026
7 checks passed
@agentHits
agentHits deleted the fix/domains-dns-hint branch October 13, 2026 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant