diff --git a/skills/ard-registry-builder/references/publishing.md b/skills/ard-registry-builder/references/publishing.md
index 1af2737..bf09695 100644
--- a/skills/ard-registry-builder/references/publishing.md
+++ b/skills/ard-registry-builder/references/publishing.md
@@ -20,12 +20,16 @@ Publishers can surface the manifest through any of:
- **Well-Known URI** — the default above; nothing else needed if you can host there.
- **Agentmap directive** in `robots.txt`: `Agentmap: https://example.com/ai-catalog.json`.
- **HTML ``** in a page ``: ``.
-- **DNS records** when you cannot use the well-known path:
+- **DNS records** when you cannot use the well-known path — use SVCB records
+ (TXT is a supported fallback):
-| Name / Host | Type | Value |
+| Name / Host | Type | Notes |
| :-- | :-- | :-- |
-| `_catalog._agents.` | `TXT` | `"url=https://bucket.s3.amazonaws.com/ai-catalog.json"` |
-| `_search._agents.` | `SRV` | port `443`, target `search.` (for a dynamic registry endpoint) |
+| `{agent-name}.` | `SVCB` | Points to the manifest path, e.g. `well-known=/not-well-known/ai-catalog.json`. |
+| `_index._agents.` | `SVCB` | Points to a dynamic registry search endpoint. |
+| `_catalog._agents.` | `TXT` (fallback) | `"url=https://..."` — use when SVCB is unsupported. |
+
+ See [DNS-AID](https://datatracker.ietf.org/doc/html/draft-mozleywilliams-dnsop-dnsaid) for the full SVCB record specification.
## Step 3 — Verify what you published
Re-run validation against the **live URL**, not just the local file, to catch hosting issues