DNS TXT records 0 record(s) found.

[gas-limit]

I'm encountering a persistent issue where the OpenAttestation DNS TXT toolkit is not recognizing the DNS TXT records that I have configured. Despite trying with three separate domains, the problem remains. I am including the steps I took below:

• Issue: DNS TXT records not detected by OpenAttestation Toolkit.
• Affected domains: dtgtest.gaslimit.engineer, docushield.live, dtgusa.org
• Steps to reproduce:

1. Logged into the domain provider's management panel.
2. Navigated to the section to manage DNS settings.
3. Added a new TXT record with the values required by OpenAttestation.
4. Saved the changes and waited for the records to propagate (verified via a DNS lookup tool).
5. Attempted to use the OpenAttestation toolkit to validate the records.

• Expected result: The toolkit should recognize the TXT records.
• Actual result: The toolkit does not recognize the TXT records for any of the domains.

I have made sure that the TXT records are correctly formatted and have allowed sufficient time for DNS propagation. Attached are the screenshots of the DNS configurations for each domain as evidence of the setup.

Your guidance on this matter would be greatly appreciated as I'm unsure what might be going wrong.

Thank you for your time and help.

Docushield.live hosted on godaddy

dtgusa.org hosted on godaddy

deftest.gaslimit.engineer

[HJunyuan]

Hi @gas-limit, here are 2 observations made:

1. docushield.live TXT record contains an extra space (incorrect: open atts). Instead, it should start with openatts.
2. The net=xxx value should be ethereum.

As such, the TXT record should look something like this:

"openatts net=ethereum netId=51 addr=0xDD56dEeF360FBB1C18E703B26B790487b05c939A"

You can find more info on the DNS TXT record format here: https://www.openattestation.com/docs/developer-section/quickstart/configure-dns#inserting-the-dns-record-for-ethereum-smart-contracts

[gas-limit]

Hello @HJunyuan,

Thank you for your prompt assistance.

I've updated the DNS TXT record for docushield.live as follows, but it still isn't recognized by the OpenAttestation DNS lookup tool:

"openatts net=ethereum netId=51 addr=0xDD56dEeF360FBB1C18E703B26B790487b05c939A"

The Google DNS lookup yields the attached result, which appears correctly formatted.

Google DNS Query Result

Could the contract itself influence how OpenAttestation processes the TXT record? I'm utilizing the TradeTrust Token contract from the token-registry repository as my document store. Here's the specific contract: TradeTrust Token Contract.

Any further guidance on this would be greatly appreciated.

[HJunyuan]

@gas-limit We have just deployed a fix. Please try again and let us know. Thank you!

[gas-limit]

@HJunyuan

Thank you for the fix, it's working perfectly now!