Skip to main content
Navigation Path: Admin Dashboard → Settings → Domain API Settings
URL: /admin/DomainAPI

Overview

Configure automatic domain registration through Dynadot’s API, set up nameservers, CNAME records, and manage available domain extensions (TLDs).

Dynadot API

API token for domain registration

Nameservers

Default DNS servers

CNAME Records

Custom domain configuration

TLD Management

Available domain extensions

Dynadot API Configuration

Configure automatic domain registration through Dynadot’s domain registration API. Setting Up Your API Token:
  1. Log in to your Dynadot account at Dynadot.com
  2. Navigate to My Account → API Settings
  3. Generate a new API key or copy your existing key
  4. Paste the API token in the Domain API Settings page
  5. Save the configuration to enable automatic domain registration
Security: Keep your API token confidential and never share it publicly. If your token is compromised, regenerate it immediately in your Dynadot account and update it in your platform settings.
API Functionality: Once configured, the API enables automatic domain registration, renewal, DNS management, and transfer operations directly from your platform without manual intervention in Dynadot’s interface.

Nameserver Configuration

Configure default nameservers that will be automatically assigned to newly registered domains.
SettingDescriptionExample
NS1Primary nameserverns1.yourdomain.com
NS2Secondary nameserverns2.yourdomain.com
CNAME DomainDomain for CNAME recordsplatform.example.com
How Nameservers Work:
  1. Customer registers a domain through your platform
  2. Domain is registered via Dynadot API
  3. NS1 and NS2 are automatically configured for the domain
  4. DNS points to your hosting infrastructure
  5. Domain becomes active and ready to use
Redundancy: Use reliable nameserver providers and ensure NS1 and NS2 are on different servers for redundancy. This ensures DNS continues working even if one server fails.
DNS Propagation: After setting nameservers, DNS changes can take 24-48 hours to propagate globally. Inform customers about this delay when they register domains.

TLD Management

Configure which domain extensions (TLDs) are available for registration on your platform. Default TLDs (shown by default in domain search):
com
net
org
io
co
Extended TLDs (shown when users click “Show More”):
app
dev
tech
online
store
shop
blog
site
Format: One TLD per line (without the dot)

Common TLDs by Category

CategoryTLDs
Genericcom, net, org, info, biz
Technologyio, tech, dev, app, cloud, ai
Businessco, company, store, shop
Creativedesign, art, studio, media
TLD Selection: Choose TLDs that match your target market. Popular TLDs like .com, .net, and .org should always be in the default list. Add niche TLDs to extended list based on customer demand.

Configuration Examples

  • Basic
  • Advanced
  • API Token: Your Dynadot key
  • NS1: ns1.yourplatform.com
  • NS2: ns2.yourplatform.com
  • CNAME: yourplatform.com
  • Default: com, net, org, io, co
  • Extended: app, dev, tech, online, store

DNS Testing

Check nameserver response:
nslookup domain.com ns1.yourplatform.com
dig @ns1.yourplatform.com domain.com
host domain.com
DNS Propagation Time:
  • Nameserver (NS): 24-48 hours
  • A Record: 1-4 hours
  • CNAME: 1-4 hours
Testing Tools: Use online DNS propagation checkers like whatsmydns.net to verify DNS changes across different global locations.

Best Practices

  • Store API tokens securely and never commit to version control
  • Regenerate API tokens periodically (every 6-12 months)
  • Limit API access to only necessary operations
  • Monitor API usage for unusual activity
  • Set up alerts for failed API calls
  • Keep backup of API credentials in secure location
  • Document who has access to API credentials
  • Use reliable nameserver providers with high uptime
  • Ensure nameservers are geographically distributed
  • Set up monitoring for nameserver availability
  • Keep NS1 and NS2 on different servers/networks
  • Document your DNS configuration
  • Test DNS resolution regularly
  • Have a backup DNS provider ready
  • Regularly review and update available TLDs
  • Add new popular TLDs as they become available
  • Remove TLDs with low demand to reduce clutter
  • Price TLDs competitively based on market rates
  • Highlight premium or recommended TLDs
  • Provide clear descriptions for niche TLDs
  • Monitor TLD registration trends
  • Inform customers about DNS propagation delays
  • Provide clear instructions for domain setup
  • Send confirmation emails after domain registration
  • Notify customers before domain expiration
  • Offer support for DNS configuration issues
  • Create documentation for common DNS tasks
  • Set up automated reminders for renewals

Troubleshooting

Issue: Domains cannot be registered through the platformSolutions:
  1. Verify API token is correct and active in Dynadot
  2. Check Dynadot account has sufficient balance
  3. Confirm domain is available for registration
  4. Review API usage limits and quotas
  5. Check error logs for specific API error messages
  6. Test API connection manually
  7. Contact Dynadot support if issue persists
Issue: DNS not resolving for registered domainsSolutions:
  1. Verify nameserver addresses are correct
  2. Wait 24-48 hours for DNS propagation
  3. Test nameservers with dig/nslookup commands
  4. Check nameserver provider status
  5. Verify nameserver records are configured correctly
  6. Ensure nameservers are responding to queries
  7. Check for typos in nameserver addresses
Issue: CNAME records not working for custom domainsSolutions:
  1. Verify CNAME domain is correct in settings
  2. Wait for DNS propagation (up to 48 hours)
  3. Remove conflicting A records at the same hostname
  4. Test with DNS lookup tools (dig, nslookup)
  5. Check CNAME target is accessible
  6. Verify DNS zone configuration
  7. Clear DNS cache on local machine
Issue: Domain extensions not showing in searchSolutions:
  1. Re-enter TLDs (one per line, no dots)
  2. Clear application and browser cache
  3. Save configuration again
  4. Refresh domain search page
  5. Check for JavaScript errors in browser console
  6. Verify TLD list format is correct
  7. Test in incognito/private browsing mode