Publish DNS-AID discovery records for rewrites.bio - #16
Draft
edmundmiller wants to merge 3 commits into
Draft
Conversation
Netlify DNS cannot create SVCB/HTTPS records required for DNS-AID agent discovery. Add Cloudflare-oriented publish/verify scripts, machine-readable record definitions (_index, _mcp, _a2a), a GitHub Actions workflow, and operator docs covering full-zone migration or _agents subdomain delegation. Co-authored-by: Edmund Miller <edmundmiller@users.noreply.github.com>
✅ Deploy Preview for rewrites-bio ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…s-16d5 Co-authored-by: Edmund Miller <edmundmiller@users.noreply.github.com>
Co-authored-by: Edmund Miller <edmundmiller@users.noreply.github.com>
ewels
requested changes
Jun 16, 2026
ewels
left a comment
ewels
left a comment
Member
There was a problem hiding this comment.
Isn't this a one-off action to add the records, as shown in the example? Why do we need all this stuff?
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
3 participants
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.
Summary
Adds automation and operator documentation to publish DNS for AI Discovery (DNS-AID) records for
rewrites.bio, fixing the failingchecks.discoverability.dnsAidcheck on isitagentready.com.The site already documents example records in
netlify/dns-aid-records.example, but they are not live in DNS. Netlify DNS does not support SVCB/HTTPS record types, so publishing requires either migrating DNS to Cloudflare or delegating_agents.rewrites.bioto a provider that supports RFC 9460 records.What changed
dns/records.json— canonical DNS-AID record definitions:_index._agents(HTTPS) — discovery entrypoint_mcp._agents(HTTPS) — WebMCP / MCP server card on homepage_a2a._agents(SVCB) — agent content endpoint with experimentalkey65000path paramscripts/publish-dns-aid.sh— publish (Cloudflare API), delegate (Netlify NS), enable DNSSEC, verify (DoH + isitagentready scan), and show zone-file outputdns/README.md— operator guide for Cloudflare migration vs_agentssubdomain delegation.github/workflows/publish-dns-aid.yml— manual workflow whenCLOUDFLARE_API_TOKENandCLOUDFLARE_ZONE_IDsecrets are configurednetlify/dns-aid-records.exampleandREADME.mdOperator action required (not in this PR)
DNS records cannot be committed to the Astro repo — they must be applied at the authoritative DNS provider:
rewrites.bioDNS to Cloudflare (or delegate_agents.rewrites.bioonly — seedns/README.md)../scripts/publish-dns-aid.sh verify→ expectdnsAid: "pass"anddnssecValidated: true.Test plan
./scripts/publish-dns-aid.sh showrenders expected zone-file records./scripts/publish-dns-aid.sh verifyconfirms current production state isfail(no records yet)publish+dnssec,verifyreportspass