Fix a custom domain

Start with the domain status in Redo Page. Then compare your DNS record with the record shown there.

"Domain not verified" or "DNS not found"

The record may still be updating. You may also have changed it at the wrong company. Check that the host and target match Redo Page.

What to check:

1. Give it time. Many records update in a few minutes. Some can take up to 48 hours.
2. Check the public record. Use dnschecker.org to see what the internet can read:
   • For www.yourdomain.com, choose CNAME. The target should be sites.redopage.com
   • A root-domain ALIAS, ANAME, or flattened CNAME may appear as A or AAAA answers instead. Use the verification status in Redo Page for that setup.
   • If you used the apex A-record fallback, confirm that both 75.2.96.173 and 99.83.186.151 are present.
3. Compare each field. Check the record type, host, and target. Look for these common mistakes:
   • Entering the full domain when the provider expects only www or @
   • Leaving an old CNAME, A, forwarding, or parking record on the same hostname
   • Editing DNS at the registrar when a different provider controls the nameservers

"SSL certificate error" or "Connection not secure"

Redo Page adds an SSL certificate after it finds the DNS record. This may take a few minutes.

What to check:

1. Check DNS first. Redo Page can add the certificate after it finds the domain.
2. Use a private window. Open the site after its Redo Page status turns active. A normal browser window may still use an old result.
3. Check Cloudflare proxy status. Redo Page currently expects the record to be DNS only, shown as a gray cloud. A proxied record can hide the CNAME Redo Page needs to verify.
4. Check CAA records. A CAA record can block the SSL certificate. Send a screenshot of your DNS records to support before you change CAA.
5. Refresh the status in Redo Page. If it still says SSL pending, contact support. Do not keep changing a correct DNS record.

"This site can't be reached" or "DNS_PROBE_FINISHED_NXDOMAIN"

This error means the domain does not point to a site yet.

What to check:

1. Confirm that the record was saved. Some providers require a second Save or Apply action.
2. Find the company that runs DNS. It may not be the company that sold you the domain. The nameservers show where to make the change.
3. Use the hostname you added to Redo Page. If you added www.yourdomain.com, create the www CNAME. If you added the root domain, use ALIAS, ANAME, or CNAME flattening at @, or add both supported A records.

"Site shows old content" or "Wrong website appears"

Your domain may still be pointing to an old hosting provider.

What to check:

1. Replace the old web record. An old Wix, Squarespace, WordPress, parking, or forward record can send people to the old site.
2. Leave email records alone. Keep MX, SPF, DKIM, DMARC, TXT, and CAA records. Only replace a record that conflicts with the same web address.
3. Wait and clear the cache. DNS can take time. Your browser may still show the old site.

"www works but root domain doesn't" (or vice versa)

The root domain and www are two web addresses. Each one needs a DNS record or a redirect to the main address.

Choose one main address. Redirect the other one to it. This also gives search engines one address for the site.

"Domain already in use" error

This means the domain is connected to another Redo Page site (possibly an old project or a different account).

How to fix:

1. Check your other sites - Log into Redo Page and check if this domain is connected to another site in your account. Remove it there first.
2. Contact support - If you can't find where the domain is connected, reach out to us and we can help locate and release it.

Help for common DNS companies

GoDaddy

• GoDaddy does not allow a CNAME at @. For a root domain, add A records for both 75.2.96.173 and 99.83.186.151. Alternatively, connect www to sites.redopage.com, make www primary, then use GoDaddy's domain forwarding to send the bare domain to https://www.yourdomain.com.
• Choose forward only. Do not use masked forwarding.
• Remove a parking or old www record if it conflicts with the new CNAME.

Namecheap

• The Advanced DNS records in Namecheap apply only when the domain uses Namecheap BasicDNS, FreeDNS, or PremiumDNS. If the domain uses custom nameservers, edit DNS with that provider.
• Use CNAME for www. Namecheap also supports ALIAS at @ for a root domain.

Cloudflare

• Set proxy status to DNS only, shown as a gray cloud. A proxied record hides the public CNAME that Redo Page uses during verification.
• Cloudflare supports a CNAME at @ through CNAME flattening. For a www record, do not enable per-record flattening while Redo Page is verifying it.

Squarespace Domains (formerly Google Domains)

• Manage former Google Domains registrations at domains.squarespace.com.
• Open the domain, choose DNS, then DNS Settings. Add a CNAME for www.
• Delete only Squarespace website defaults that conflict with the hostname you are connecting. Keep email, verification, and security records.

How long DNS can take

Many DNS changes show up in a few minutes. Some can take up to 48 hours. The old record's TTL can make the wait longer.

• First few minutes: Check that the provider saved the record you entered.
• After an hour: Check the public DNS answer and refresh status in Redo Page.
• After 24 hours: Recheck the active nameservers and look for conflicting records.
• After 48 hours: Contact support with screenshots of the record and nameservers.

← Back to Custom Domains guide