Skip to content

Domain verification for signalfuse.xyz fails every time I click Continue, even though the TXT record is correctly set and resolving globally. #877

Description

@hypeprinter007-stack

Prerequisites

  • I checked the documentation and found no answer to my problem
  • I checked the existing issues and made sure there are no similar bug reports

Category

Bug (unexpected behavior)

Expected Behavior

No response

Observed Behavior

TXT record (verified via dig):
$ dig TXT signalfuse.xyz +short
"fetch-aname-token=xLquf1rKW-O3e_OSjctPBEfxpoR4lBI6isf7rZGomZg"

What I've tried:

  • Added TXT record with Host @ and the exact token value from the Agentverse UI
  • Confirmed propagation via dig, nslookup (resolves from multiple DNS servers)
  • Waited 1+ hours after propagation
  • Re-entered the domain from scratch
  • Added the same TXT on _fetch subdomain as well
  • Domain is on Cloudflare, DNS Setup: Full, record is DNS-only (not proxied)

Timeline: Domain was newly registered today. It initially returned NXDOMAIN for ~20 minutes before nameservers propagated. The TXT record has been resolving correctly for
over an hour now. Possible that the initial NXDOMAIN got cached on your verification server.

Also reporting: This same agent cannot get "ASI Available" despite 100% checklist completion (README, handle, avatar, about, 5+ interactions). My other 4 agents all have ASI
Available. This agent was deleted and redeployed fresh — still no ASI badge.

To Reproduce

No response

Version

unsure

Environment Details (Optional)

Failure Logs (Optional)

Additional Information (Optional)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

c-bugCategory: Something isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions