Domain verification error

[MickaelNeves]

I added the TXT to vercel but still getting error when trying to validate domain

[ligi]

seems you TXT record is not properly added

$ dig botto.com TXT

; <<>> DiG 9.18.12-1ubuntu1.1-Ubuntu <<>> botto.com TXT
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42397
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;botto.com.			IN	TXT

;; ANSWER SECTION:
botto.com.		273	IN	TXT	"google-site-verification=6U_xckvGgNAs8e3cRkDd5tmjZvx8BdQy_FSUISqt61k"
botto.com.		273	IN	TXT	"google-site-verification=BGXp8pxyH-U2m-8d4nOduLWVkByoGYuY4iOLm5Tygeg"

;; Query time: 28 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Wed Aug 02 12:03:37 CEST 2023
;; MSG SIZE  rcvd: 200

[boidushya]

seems like youve added the flag for "wallet-connect-dns-verficiation" subdomain. Instead, you need to add it for your main domain, and copy-paste the string exactly how it shows up while keeping the "Name" section empty
A correct configuration would show up like this on dig

boidushya.com.		600	IN	TXT	"wallet-connect-dns-verification=b7e0...9be1"

[MickaelNeves]

yap that was the issue, thanks!

[michallangmajer]

Hello, I'm facing a similar problem with coinbrain.com. How can I validate whether the TXT record was correctly added? 😞 From my POV everything looks fine. 🙏 Any ideas, please?

[boidushya]

Hello, I'm facing a similar problem with coinbrain.com. How can I validate whether the TXT record was correctly added? 😞 From my POV everything looks fine. 🙏 Any ideas, please?

Hey, can you try using mxtoolbox.com/txtlookup.aspx for this?

[cryptojoindev]

I vahe added TXT correctally but not work

[boidushya]

Looks like you might've set up your domain incorrectly on your WalletConnect Cloud dashboard, since I see you're using com.br instead of cryptojoin.com.br

[cryptojoindev]

Domain is correct

[cryptojoindev]

In domain verification always show ".com.br", I think that is a bug in backend of wallet connect

[Cali93]

Hey @cryptojoindev, thanks for the report.
The issue has ben fixed, you should be able to head over https://cloud.walletconnect.com and copy the newly generated verification code for cryptojoin.com.br instead of com.br. You will then need to update your TXT record to point to the new verification code.

Sorry for the inconvenience, let us know if it worked out or if you're still facing issues.

[michallangmajer]

In our case, the problem was that we set everything correctly only in GoDaddy administration but we're using CloudFlare for CDN and it was necessary to setup there as well.

[ravisriv]

Domain verification issue again on Walletconnect.com when verifying domain at https://cloud.walletconnect.com/app as of September 15, 2023.

I had my domain verified earlier. Recently, I made a minor change and tried to re-verify the domain but it no longer works. I tried all the different permutations and combinations. The key of the TXT record has changed. Instead of "wallet-connect-dns-verification," the key is now a hex string. I tried replacing the key with the old standard ("wallet-connect-dns-verification"). That did not work. I tried the key the way it is - straight copy-paste. That did not work too.

Here is the error I get when I copy-paste the verification code for the TXT record.

And checked on mxtoolbox.com/txtlookup.aspx. The DNS is publishing the TXT record correctly. The issue appears to be with the verification program of Walletconnect. It is not matching the key correctly.

[TurboFolkBlackMetal]

I am having the same issue! Tried verifying it in 10 different ways, recreating keys, etc... and nothing works. It seems that the verify process is now broken.

[ravisriv]

@albymack - Delete the project. After that re-create the project by clicking on the "New Project" button and completing the profile. I had tested this procedure on a domain yesterday and it had worked. But the process is continuing to fail for previously verified domains.

[Cali93]

There are only 2 ways of verifying your domain. Please follow our detailed guide https://docs.walletconnect.com/2.0/cloud/verify and give it some time (it can take up to 72 hours for your DNS record to propagate) also make sure that the TTL of previous/stale records isn't too long.

[TurboFolkBlackMetal]

@Cali93 - the DNS has been propagated I used dig to check the DNS records. I have followed the guide to the letter.

This is the response for dig klaster.io TXT

; <<>> DiG 9.10.6 <<>> klaster.io TXT
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12334
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;klaster.io.			IN	TXT

;; ANSWER SECTION:
klaster.io.		3600	IN	TXT	"3751743d-1dfc-41b2-b002-071d1be358bb=hidden-info-hidden-info"

;; Query time: 159 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Wed Sep 20 11:17:33 CEST 2023
;; MSG SIZE  rcvd: 153

Yet, when I click verify on the site it gets broken.

I'm quite sure you guys have a bug in the verification process.

[Cali93]

Thanks for the additional context and sorry for the inconvenience.
The domain verification was relying on a 200 status code to check if you used the static file method.
And in your case curl --location 'https://klaster.io/.well-known/walletconnect.txt' is returning 200.
This is a valid edge case and the issue has been fixed.

[TurboFolkBlackMetal]

Oh amazing! This is probably partially my fault also, but the speed of this fix is impressive. Thanks guys 👍

[Ductm00]

This is my curl result but not verified domain

[darrenvechain]

Any update on this?

[Cali93]

Hey there, this issue has been fixed since then. If you're facing problems verifying your domain please provide information so that we can help you.

[haiifeng]

me too, help.

[c0da523]

Is it only support second level domain?

[Cali93]

Yes, once you verified your second level domain it should work for all subdomains.

[ketan-esp]

Domain Verification failing.