Agentverse verification too fast for Network Solutions

[lacryptorina]

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 in Agentverse

Expected Behavior

Verification when entry created correctly

Observed Behavior

I added the DNS @ txt entry for verification.
Network Solutions takes WAY too long to verify.
Your verification times out before it even loads.
Please fix.

To Reproduce

No response

Environment Details (Optional)

Failure Logs (Optional)

Additional Information (Optional)

[jrriehl]

Thanks for raising this. I think I see the issue. On this screen, "Continue" is meant to be clicked once the TXT entry has already been added to the DNS record, but we'll update this to make sure it is more clear.

[lacryptorina]

Let me make it clear that I understood that, did that exactly, know how to make a dns entry, and yet again it was to no avail.

so yeah

no

(growls)

[lacryptorina]

give different directions to people other than @ if it is a subdomain

[lacryptorina]

do i have to create a whole new token yet again or will the system pick it up after it's already failed?

[jrriehl]

Sorry for misunderstanding. I wasn't sure what you meant by Network Solutions taking too long to verify given that this verification should have already been done before registering the domain on Agentverse. In any case, I'll test to make sure every looks good on our end. And the token you get should not change provided that the domain name does not change.

[lacryptorina]

It takes Network solutions over 24 hours to push a change in DNS entries. The only fix for this because of the way you have it set up is leaving the entry open for 24 hours after I copy the token before clicking that, yes I added the DNS entry. I think the best thing would be to not have such a stringent timeout and give it a day, at least before the connection fails. As you have it now there's no way to recheck, it just fails, that's it, and if I want to reconnect I need a new token.

…

On Wed, Aug 5, 2026, 13:45 James Riehl ***@***.***> wrote: *jrriehl* left a comment (fetchai/agentverse#116) <#116 (comment)> Sorry for misunderstanding. I wasn't sure what you meant by Network Solutions taking too long to verify given that this verification should have already been done before registering the domain on Agentverse. In any case, I'll test to make sure every looks good on our end. And the token you get should not change provided that the domain name does not change. — Reply to this email directly, view it on GitHub <#116?email_source=notifications&email_token=AZ2T3MUT244SLGPPLIEBJP35IMF3BA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJZGA3TKNJTGMZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5190755333>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ2T3MUEGIQULCA2R5RFUND5IMF3BAVCNFSNUABFKJSXA33TNF2G64TZHM4DCOJYGMZDCMRWHNEXG43VMU5TKMBVHA2TKNZQGY2KC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AZ2T3MWULJGSGBYHR3AJONT5IMF3BA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJZGA3TKNJTGMZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AZ2T3MXUWTG6SGPZ45BRLUD5IMF3BA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJZGA3TKNJTGMZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[lacryptorina]

or should I say if I want to attempt to reconnect the way you have it set up is that each time I have to ask for a new token so each time I have to push another DNS registry which each time takes another 24 hours because it's Network Solutions. I hope I've made myself clear and if you have any questions please ask.

…

On Thu, Aug 6, 2026, 10:45 The Cryptory ***@***.***> wrote: It takes Network solutions over 24 hours to push a change in DNS entries. The only fix for this because of the way you have it set up is leaving the entry open for 24 hours after I copy the token before clicking that, yes I added the DNS entry. I think the best thing would be to not have such a stringent timeout and give it a day, at least before the connection fails. As you have it now there's no way to recheck, it just fails, that's it, and if I want to reconnect I need a new token. On Wed, Aug 5, 2026, 13:45 James Riehl ***@***.***> wrote: > *jrriehl* left a comment (fetchai/agentverse#116) > <#116 (comment)> > > Sorry for misunderstanding. I wasn't sure what you meant by Network > Solutions taking too long to verify given that this verification should > have already been done before registering the domain on Agentverse. In any > case, I'll test to make sure every looks good on our end. And the token you > get should not change provided that the domain name does not change. > > — > Reply to this email directly, view it on GitHub > <#116?email_source=notifications&email_token=AZ2T3MUT244SLGPPLIEBJP35IMF3BA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJZGA3TKNJTGMZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5190755333>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AZ2T3MUEGIQULCA2R5RFUND5IMF3BAVCNFSNUABFKJSXA33TNF2G64TZHM4DCOJYGMZDCMRWHNEXG43VMU5TKMBVHA2TKNZQGY2KC5QC> > . > Triage notifications, keep track of coding agent tasks and review pull > requests on the go with GitHub Mobile for iOS > <https://github.com/notifications/mobile/ios/AZ2T3MWULJGSGBYHR3AJONT5IMF3BA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJZGA3TKNJTGMZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> > and Android > <https://github.com/notifications/mobile/android/AZ2T3MXUWTG6SGPZ45BRLUD5IMF3BA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJZGA3TKNJTGMZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. > Download it today! > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[jrriehl]

Yes, the token you are provided for a particular domain should not change. It's derived from the domain name itself and deterministic so there should be no need to make any updates in Network Solutions.

We have fixed an issue on our side that was blocking the verification of some domains, so please try again and let us know how it goes.