Trying to republish an existing server under a DNS-verified namespace (net.dabloons/dabloons). Both login dns and login http fail because the registry's resolver insists the domain does not exist:

failed to fetch keys: failed to lookup DNS TXT records: lookup daboons.net on 34.118.224.10:53: no such host
failed to fetch key: Get "https://daboons.net/.well-known/mcp-registry-auth": lookup daboons.net on 34.118.224.10:53: no such host

What I checked from outside:

• The apex TXT record (v=MCPv1; k=ed25519; p=...) and A records resolve fine via Cloudflare, Google, and Quad9 DoH.
• No DNSSEC DS record; plain Cloudflare zone, healthy SOA.
• Retried over ~40 minutes, so not a propagation delay (record TTL is 300s).
• mcp-publisher validate passes on the new server.json.

Go reports "no such host" on NXDOMAIN, so the cluster resolver at 34.118.224.10 appears to be serving a stale NXDOMAIN (or otherwise failing) specifically for this name. Happy to provide timestamps or test anything.