Skip to content

e2e: assert the actor zone publishes the router's AAAA - #1082

Open
Yuan Gao (ygao-g) wants to merge 4 commits into
agent-substrate:mainfrom
ygao-g:e2e-ipfamily-dns
Open

e2e: assert the actor zone publishes the router's AAAA#1082
Yuan Gao (ygao-g) wants to merge 4 commits into
agent-substrate:mainfrom
ygao-g:e2e-ipfamily-dns

Conversation

@ygao-g

@ygao-g Yuan Gao (ygao-g) commented Aug 20, 2026

Copy link
Copy Markdown
Collaborator

Stacked on #874, whose three commits it contains; the last commit is the reviewable change. Part of #246.

It skips until atenet-router has two ClusterIPs (#911), and the record it looks for arrives with #938 — so this is green but inert on main, and #1094's dual-stack lane is what will actually run it.

🤖 Generated with Claude Code

Before, the actor zone answered A queries and failed everything else --
AAAA for a valid actor, and any name in the zone that is not an actor.
A failure reads as a temporary error rather than an answer, so clients
retry it and then give up on the name; Alpine actors could not resolve
each other at all, even on an IPv4-only cluster. After, those queries
return a correct empty answer, and one that resolvers can cache.

A unit test pins the whole rendered zone as a literal, so editing the
name pattern or the suffix fails there rather than passing silently.
Nothing in the e2e harness could query the actor DNS zone. Suites reach
actors by port-forwarding atenet-router and passing the actor name as a
Host header, so the zone CoreDNS actually serves went unasserted, and a
suite that wanted to check it had no way to distinguish an empty answer
from a server failure. Adds a DNS client that port-forwards the atenet
DNS Service and reports the rcode class alongside the addresses, plus a
helper for the router's ClusterIP in each family.

The tests that use these follow. clusterIPsByFamily here is a stopgap
that agent-substrate#938 replaces with internal/ipfamily.
The zone answered A queries and failed everything else -- AAAA for a
valid actor, and any name in the zone that is not an actor -- and no
test caught it, because Go's resolver masks a SERVFAIL that musl treats
as fatal. These assert the rcode class rather than the record: a non-A
qtype and a name that misses the actor regex must come back NODATA or
NXDOMAIN, and an A query must carry the router's ClusterIP.

Both rcode assertions fail on a tree without the first commit here and
pass with it, measured on a single-stack IPv4 kind cluster. Part of
agent-substrate#246.
The rcode assertions in the previous commit prove the zone stops failing
an AAAA query, not that it ever answers one. Nothing checks that the
record the zone does publish is the router's IPv6 ClusterIP, so agent-substrate#938
could regress to an empty answer and every existing test would still be
green.

Kept separate from TestActorDNSZone because it is the only assertion
here whose expected result changes with the cluster: it skips wherever
atenet-router has a single ClusterIP, which is every cluster until agent-substrate#911
gives the Service a dual-stack policy. Part of agent-substrate#246.
@ygao-g Yuan Gao (ygao-g) changed the title e2e: assert the actor DNS zone answers benign rcodes e2e: assert the actor zone publishes the router's AAAA Aug 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

DO NOT MERGE This PR must not be merged yet.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant