If you have already purchased your domain from another domain registrar, we recommend transferring it to Cloudflare. This will simplify the process of using your domain with Church Connect.
Prior to starting the transfer process of your church's existing domain, you will want to build your website in Church Connect first. You want your people to visit a new completed website, NOT a work in progress! Learn more ›
Cloudflare has a detailed guide describing step-by-step on how to transfer your domain as well as detailed instructions for the most popular registrars. This can be found HERE.
Here are the top 6 common troubleshooting issues people encounter when transferring a domain from one registrar to another:
Issue: This is an advanced form of security offered by some domain registrars.
Solution: Disable this feature on your old registrar. It may take up to 24 hours for the DNSSEC to be disabled.
Issue: The domain is still locked at the current registrar, which prevents the transfer from proceeding.
Solution: Ensure that the domain is unlocked by logging into your current registrar’s account and disabling the domain lock feature. Most registrars provide a toggle option to unlock the domain.
Issue: The EPP (Extensible Provisioning Protocol) code, also called the transfer authorization code, is either missing or incorrect.
Solution: Request the correct EPP code from your current registrar and double-check it when initiating the transfer. Make sure it’s entered correctly without any extra spaces.
Issue: Domains cannot be transferred within 60 days of initial registration or a previous transfer, as per ICANN regulations.
Solution: Verify when the domain was registered or last transferred. If it falls within the 60-day window, you’ll have to wait until the period ends before attempting the transfer again.
Issue: The WHOIS contact information for the domain (such as email address) is incorrect or outdated, preventing the current registrar from verifying the transfer request.
Solution: Update your domain’s WHOIS contact information with your current registrar to ensure the contact email is valid and accessible. This is crucial because verification emails are sent to the WHOIS email address.
Issue: The domain’s nameservers are not updated, causing issues with DNS resolution post-transfer. While this doesn’t prevent the transfer itself, it can cause downtime or disruptions to services like email or website access.
Solution: Before or during the transfer, update your nameservers at the new registrar to reflect any custom DNS settings, ensuring continuous operation of your domain services after the transfer.
Typically, transferring your domain should not cause any downtime if the nameservers and DNS settings remain unchanged. It’s important to ensure that your DNS settings are correctly configured before initiating the transfer. Updating nameservers after the transfer can cause temporary disruptions.
Domain transfers usually take between 5 to 7 days to complete, but it can sometimes be faster depending on the registrars involved. Once initiated, both the gaining and losing registrars must confirm the transfer. You will be notified when the process is complete.
No, your email accounts will not be lost during the transfer, but it’s crucial to ensure your DNS records, especially MX records (which handle email routing), are correctly set up at the new registrar. Failing to update these can cause disruptions in email services.
Yes, when you transfer a domain, most registrars will require you to pay for a one-year renewal, which is added to your current domain registration period. The domain transfer fee typically covers this extension.