1.3 KiB
1.3 KiB
MCP Deep Discovery Findings - Phase 2B
Date: 2026-10-12T21:31:00+03:00
DNS Infrastructure Discovery
- resolv.conf:
nameserver 127.0.0.1+search mesh - Local DNS resolver: Running at
127.0.0.1:53inside containers - Search domain:
.mesh— suggesting DNS names resolve as<name>.mesh - Current DNS state: All patterns return NXDOMAIN — apps may need specific tag matching
DNS Resolution Test Results (from soc-backend)
| Pattern | Result |
|---|---|
soc-gateway |
NXDOMAIN |
soc-gateway.mesh |
NXDOMAIN |
soc-gateway.local |
NXDOMAIN |
soc-gateway.soc-private-net |
NXDOMAIN |
soc-gateway.project.mesh |
NXDOMAIN |
soc-gateway.cumin.internal |
NXDOMAIN |
App Object Schema Keys
id, created_at, updated_at, cpu, memory, project_id, name, image, args, ports, env, mounts, instances, hibernated, tags, status, alias
New Fields Discovered
aliasfield on both apps and constellationstagsfield: key-value pairs (e.g.,{"component":"gateway","platform":"soc"})- Constellation alias:
soc-private-net-ad145d86
Hypothesis
The Internal DNS feature likely requires apps to share the same tag for mutual DNS discovery. The .mesh search domain suggests names resolve as <app-name>.mesh but only within the same tag scope.