Off-Chain ENS Integration

Off-chain ENS integration offers a gas-free alternative using DNS TXT records. While it may have limited support on some platforms, it's completely free to set up and modify.

Prerequisites

• Access to your domain's DNS settings
• Ability to add TXT records
• Domain must not use NSEC/NSEC3 for negative proofs

Setup Process

1. Add ENS Configuration Record

Add a TXT record with the following format:

"ENS1 0x3CA097Edd180Ea2C2436BD30c021Ca20869087a0 0x9b6435e0e73d40f8a64fe5094e4ea462a54a078b https://hns.id/api/gateway/ccip (opens in a new tab)"

Where:

• "0x3CA097Edd180Ea2C2436BD30c021Ca20869087a0" is the resolver address
• "0x9b6435e0e73d40f8a64fe5094e4ea462a54a078b" is the signer address
• "https://hns.id/api/gateway/ccip (opens in a new tab)" is the endpoint URL

2. Configure DNS Records

Add this TXT record in two locations:

1. Against the "*" (wildcard) entry
2. Against the "@" (root) entry (optional)

3. Add TLD Mapping

Add another TXT record against "@":

"HNS1 your-tld-name"

Replace "your-tld-name" with your TLD (e.g., "cool-tld")

How It Works

The system maps your entire domain to a HNS.ID TLD:

• If you link "example.com" to "cool-tld/"
• Then "user.example.com" resolves to the same data as "user.cool-tld"
• This includes all ENS-compatible data (addresses, text records, etc.)

Verification

To verify your setup:

1. Wait for DNS propagation (usually 5-30 minutes)
2. Use dig to check your TXT records:

"dig TXT *.yourdomain.com" "dig TXT @yourdomain.com"

Limitations

• Not supported by domains using NSEC/NSEC3 for negative proofs
• May have limited support in some dApps
• Requires DNS infrastructure
• DNS propagation delays may affect updates

Benefits

• Completely free to set up and modify
• No blockchain transactions required
• Instant updates (after DNS propagation)
• Works with any DNS domain
• No gas fees

Troubleshooting

Common issues:

1. Records not resolving:

   • Verify TXT record format
   • Check DNS propagation
   • Confirm wildcard record support

2. Limited dApp support:

   • Consider switching to on-chain integration
   • Verify dApp's ENS resolver compatibility

3. DNS configuration:

   • Ensure both "*" and "@" records are set
   • Verify TXT record formatting
   • Check for conflicting DNS settings

Support

If you encounter any issues during setup, please:

1. Verify your DNS provider supports TXT records
2. Ensure your DNS configuration allows wildcard records
3. Double-check all record formats and values
4. Contact our support team if problems persist