1. Decide Whether to Route the Domain Through Cloudflare
Confirm that the domain will be managed through Cloudflare for DNS handling.
Use this approach when you want:
Automatic DNS record updates.
Better speed and security benefits.
One central place to manage multiple domains.
Keep the domain registered with your current registrar (for example, Crazy Domains, GoDaddy, or Venture IP) and only change the nameservers to Cloudflare.
2. Start the Domain Onboarding Process in Cloudflare
In Cloudflare, choose the option to onboard a domain.
Enter the domain name you want to connect (example:
lharrison.design).When prompted, choose the option to scan existing DNS records.
Use the quick scan/recommended option instead of manually entering records to reduce the chance of mistakes.
Select the free plan if you do not need a paid Cloudflare plan.
3. Review the Scanned DNS Records
Wait for Cloudflare to scan the current DNS records.
Review all detected records carefully, including:
Email-related records.
Website records.
Campaign or third-party service records.
Verify that the records match what is currently in use before continuing.
If any record should not be proxied, turn off the proxied status for that record.
4. Continue to Activation and Prepare Registrar Changes
After confirming the DNS records, continue to the activation step in Cloudflare.
Do not expect the domain to work fully until the nameservers are updated at the registrar.
Keep the Cloudflare nameserver details visible so they can be copied into the registrar settings.
5. Update Nameservers at the Domain Registrar
Log in to your domain registrar account (for example, Crazy Domains).
Open the domain settings by selecting the cogwheel or settings icon.
Go to Manage Domain.
Open the Nameservers section.
Replace the existing nameservers with the two nameservers provided by Cloudflare.
Save the changes.
6. Confirm the Change and Allow Time to Propagate
Confirm that the nameserver update has been saved successfully.
Mark the domain as having updated nameservers in Cloudflare if prompted.
Allow time for DNS propagation to complete.
Understand that the change may not take effect immediately across all systems.
7. Verify Automatic DNS Management in Cloudflare
Once propagation is complete, confirm that future domain changes are being routed through Cloudflare.
When adding or changing domains in the connected system, DNS records should now be added automatically in Cloudflare.
This removes the need to manually copy and paste individual DNS records each time a change is made.
Cautionary Notes
Do not delete or alter DNS records without verifying their purpose first. Incorrect changes can break email or website services.
Be careful with the proxied setting. Some records should remain DNS-only, especially certain email-related records.
Nameserver changes can take time to propagate. Expect a delay before the domain fully resolves through Cloudflare.
Keep registrar access secure. You will need access to the current registrar account to complete the nameserver update.
Tips for Efficiency
Use Cloudflare’s recommended quick scan to reduce manual entry errors.
Keep all domain names under one Cloudflare account for easier management.
Review DNS records immediately after scanning so issues are caught before activation.
Save the Cloudflare nameservers in a secure note or password manager for quick access during registrar updates.
Centralizing domains in Cloudflare can simplify future maintenance and reduce repetitive DNS work.