Domain Synchronization

Domain synchronization is the core feature of Domain Collective, automatically fetching and updating your domain information from all connected registrars.

How Synchronization Works

The Sync Process

When a sync is triggered, Domain Collective performs these steps:

graph TD
    A[Sync Triggered] --> B{Validate Credentials}
    B -->|Valid| C[Fetch Domains]
    B -->|Invalid| D[Authentication Error]
    C --> E[Process Each Domain]
    E --> F[Fetch DNS Records]
    F --> G[Update Database]
    G --> H[Update Dashboard]
    H --> I[Sync Complete]
    D --> J[Show Error]

Sync Types

Sync Status States

Your integration can be in one of these states:

What Gets Synchronized

Domain Information

Core domain data synced from registrars:

• Domain Name - The FQDN (fully qualified domain name)
• Registration Date - When domain was registered
• Expiry Date - When domain expires
• Auto-Renewal - Automatic renewal status
• Privacy Protection - WHOIS privacy status
• Transfer Lock - Domain lock status
• Registrar DNS - Using registrar's nameservers

DNS Records

All standard DNS record types:

Nameserver Configuration

Current nameserver setup:

• Primary and secondary nameservers
• Registrar vs custom nameservers
• Provider detection (Cloudflare, Vercel, etc.)

Sync Performance

Timing Expectations

Sync duration depends on several factors:

Factors Affecting Speed

1. Number of domains - More domains take longer
2. DNS records per domain - Complex DNS takes time
3. Registrar API speed - Varies by provider
4. Network latency - Connection speed matters
5. Rate limits - API throttling may apply

Background Processing

Domain Collective uses Vercel Functions for background synchronization:

How It Works

1. Request initiated - User triggers sync
2. Response sent - Immediate acknowledgment
3. Background task - Sync runs asynchronously
4. Status updates - Real-time progress
5. Completion - Dashboard refreshes

Benefits

• No waiting - UI remains responsive
• Parallel processing - Multiple domains at once
• Error isolation - One failure doesn't stop others
• Automatic retry - Failed items retry

Data Consistency

Field Standardization

Different registrars use different field names. Domain Collective standardizes these:

Raw Data Preservation

Domain Collective stores both:

• Standardized data - For consistent UI/API
• Raw response - Original registrar data

This dual storage ensures:

• No data loss during mapping
• Ability to extract new fields later
• Debugging capability
• Future compatibility

Manual Sync

When to Use Manual Sync

Trigger a manual sync when:

1. After registrar changes - Updated DNS, nameservers, etc.
2. Domain additions - Added new domains at registrar
3. Credential updates - Changed API tokens
4. Data verification - Ensuring accuracy
5. Troubleshooting - Resolving sync issues

How to Trigger

1. Navigate to Integrations page
2. Find the integration card
3. Click "Sync Now" button
4. Wait for completion

Sync Errors

Common Error Types

Error Recovery

Domain Collective handles errors gracefully:

1. Partial success - Synced domains are saved
2. Error logging - Details preserved for debugging
3. User notification - Clear error messages
4. Retry capability - Manual retry available

Monitoring Sync Status

Integration Card Indicators

Activity Indicators

• Progress bar - Shows sync progress
• Domain counter - Updates as domains sync
• Last sync time - "2 minutes ago"
• Error messages - Specific failure reasons

Best Practices

Optimal Sync Frequency

• Weekly - For most users
• Daily - For active domain traders
• After changes - When modifying at registrar
• Before expiry - Check renewal status

Performance Tips

1. Stagger syncs - Don't sync all integrations at once
2. Off-peak hours - Sync during low-traffic times
3. Monitor errors - Address issues promptly
4. Keep credentials current - Update before expiry

Data Accuracy

• Verify counts - Ensure all domains appear
• Check dates - Confirm expiry dates correct
• Review DNS - Validate record accuracy
• Test changes - Sync after registrar updates

Advanced Topics

Incremental Sync (Future)

Planned enhancement for faster syncs:

• Only fetch changed domains
• Track modification timestamps
• Reduce API calls
• Faster updates

Webhook Integration (Future)

Real-time updates via webhooks:

• Instant change notification
• No polling required
• Reduced latency
• Better efficiency

Sync Scheduling (Future)

Automated sync scheduling:

• Daily/weekly/monthly options
• Time-based triggers
• Batch processing
• Email notifications

Troubleshooting

Sync Never Completes

Possible causes:

• Very large portfolio (500+ domains)
• Network interruption
• API timeout

Solutions:

1. Wait up to 10 minutes
2. Check integration card for errors
3. Try manual sync again
4. Contact support if persists

Missing Domains

Possible causes:

• Domains expired/transferred
• API permissions limited
• Pagination issue

Solutions:

1. Verify at registrar directly
2. Check API scope/permissions
3. Manual sync to retry
4. Report specific domains to support

Incorrect Data

Possible causes:

• Registrar API changes
• Field mapping issues
• Cache problems

Solutions:

1. Trigger manual sync
2. Clear browser cache
3. Compare with registrar
4. Report discrepancies

Frequently Asked Questions

Continue learning: DNS Management → | Nameservers →