Skip to main content

Connect your own domain

Your website always has a free address that ends in .site.payhoa.com .

M
Written by Michael Bollinger

Your website always has a free address that ends in .site.payhoa.com. If your association owns a domain, such as oakwoodhoa.com, you can connect it so visitors reach your site there too. You add a few records at the company where you bought the domain, then click Verify in PayHOA. HTTPS (the padlock) is set up for you.

Before you start:

  • Your association must own the domain. PayHOA doesn't sell, register or hold domains. You bought it from a registrar such as GoDaddy, Namecheap, Network Solutions, Cloudflare, Bluehost or IONOS. Not sure who it is? Look your domain up with any WHOIS lookup tool; the Registrar line tells you.

  • Your site must be published. Before the first publish, and while the site is offline, the Custom domain card says "You can connect a custom domain once your website is published". See Preview, publish and version history.

  • Have your registrar login ready. You make the changes yourself at your registrar. PayHOA support never logs in to your registrar. Never send your registrar password to anyone, including PayHOA support.

  • You need write permission for the Website builder.

What you'll set up

The new website builder uses CNAME records only:

  • a CNAME for www that points to your PayHOA address ({your-name}.site.payhoa.com);

  • a way for the root domain (the domain with nothing in front, shown as @) to reach the site. Many registrars don't allow a CNAME on the root, so the root usually forwards to https://www. your domain;

  • two certificate CNAMEs that prove you own the domain, so HTTPS can turn on.

You don't add A records, an IP address or TXT records. If an article or an old email tells you to add A records pointing to 199.34.228.x, that was for the old Weebly-based sites. See Legacy Weebly sites and moving to the new builder.

Your email doesn't change. Leave your MX records (and any other email records) as they are.

Step 1: Enter your domain

  1. Open Other Tools → Website builder → the Domain tab.

  2. On the Custom domain card ("Connect a domain purchased through a web hosting service"), turn on the switch.

  3. Click Set up custom domain.

  4. In Domain name, type your domain, for example oakwoodhoa.com. "Don't include "https://" or "www." - just enter your domain name."

  5. Click Validate Domain. When it changes to Continue to DNS setup, click it.

Clicking Continue to DNS setup saves the domain and requests its certificate. The domain now shows on the Custom domain card as Pending verification, even if you close the dialog.

If you see an error:

Message

What to do

"This domain is already in use by another website."

Another PayHOA website has this domain. Check you typed it correctly. If it's yours, contact support.

"This domain conflicts with an existing PayHOA subdomain."

The first part of your domain (for example oakwoodhoa in oakwoodhoa.com) is the same as another association's .site.payhoa.com address. Your domain isn't in use, but the builder won't accept it. Contact support with the domain you want to use.

"Please enter a valid domain name (e.g., example.com)."

Type the domain only, with no https://, www. or / at the end.

Step 2: Delete old A records

The dialog is now Add DNS records (Step 2 of 3). Keep it open, and in another browser tab log in to your registrar and open the domain's DNS settings (sometimes called DNS Management or Manage DNS).

The dialog says:

"Delete old A records first. Any existing A record on www or on the root domain @ blocks the records below. New domains often come with a parked A record, so look for one even if you never added it."

  1. Look for any A record whose name (host) is @, blank, your domain, or www.

  2. Delete each one. Don't touch MX, TXT or other email records.

Coming from a Weebly site with PayHOA? If your association ever had a Weebly site, the dialog also shows "Coming from Weebly? Start here. Remove the old Weebly A-records before adding the new DNS records. Log in to your domain provider and delete these if they exist:", with two rows for @ or * symbol and www pointing to 199.34.228.72. Delete every A record that points to an address starting 199.34.228., whatever the last number is. Each Weebly site was given its own address in that range, so yours may not end in .72 as the box shows (others ended in .43, .47, .50, .74 or .79). A leftover one is the most common reason a domain won't verify.

Step 3: Pick your DNS provider and add the records

  1. In Choose your DNS provider, pick the option for your registrar (see the table below).

  2. Add the records from Records that point your domain to PayHOA.

  3. Add both records from Records that prove you own the domain (HTTPS certificate).

  4. Save at your registrar.

Each value has a copy button. Copy and paste rather than typing.

What each choice shows

Choose your DNS provider

Records that point your domain to PayHOA

Most providers (Namecheap, Cloudflare and most others)

CNAME @ → {your-name}.site.payhoa.com and CNAME www → {your-name}.site.payhoa.com

GoDaddy (special setup required)

CNAME www → {your-name}.site.payhoa.com, then forward the root (steps below)

Domain forwarding (Network Solutions, legacy)

Domain Forwarding @ → https://www.{your domain} and CNAME www → {your-name}.site.payhoa.com

AWS native (Route53, Azure DNS)

ALIAS (name: Leave blank) → {your-name}.site.payhoa.com and CNAME www → {your-name}.site.payhoa.com

The root domain (@)

The www CNAME works at every registrar. The root is where most setups go wrong: most registrars don't let you put a CNAME on @. The dialog's Most providers choice notes: "Some DNS providers don't allow CNAME records for the root domain. In that case, pick GoDaddy or domain forwarding above, or contact your DNS provider for ALIAS record support."

If your registrar refuses the @ CNAME, or you're not sure, use the approach that works everywhere: set up the www CNAME, confirm https://www. your domain loads your site, then forward the root domain to https://www. your domain as a permanent (301) redirect with no masking.

Registrar

What to do for the root (@)

GoDaddy

Pick GoDaddy (special setup required). Forward the root to https://www. (steps below).

Network Solutions

Pick Domain forwarding (Network Solutions, legacy). Forward the root to https://www..

Namecheap

Namecheap doesn't take a CNAME on @. Add an ALIAS record on @ pointing to {your-name}.site.payhoa.com, or use Namecheap's redirect to forward the root to https://www..

Cloudflare

A CNAME on @ is allowed (Cloudflare "flattens" it). Use Most providers. Set every PayHOA record to DNS only (grey cloud), not Proxied.

Bluehost, hosting.com, IONOS and others

If the root won't take a CNAME, forward the root to https://www. in the registrar's domain or redirect settings, or ask the registrar whether it supports ALIAS records.

Note: if a proxy sits in front of your domain (Cloudflare's orange cloud, for example), PayHOA can't see that the domain points to your site. DNS status then shows Points elsewhere even if the site loads, and the certificate records may not be found. Turn the proxy off for these records.

GoDaddy

The dialog's GoDaddy setup instructions go in this order:

  1. Change the www record. In DNS Management, GoDaddy already has a CNAME named www pointing to @. Click the pencil to edit it. Don't add a second one. Change its value to your {your-name}.site.payhoa.com address and save. If www is an A record instead, delete it first, then add the CNAME. Delete the parked A record on @ if GoDaddy lists one. Click Add New Record for each certificate record, and save after each one.

  2. Confirm www loads your site. Open https://www. your domain in a new tab. DNS changes usually take 5 to 30 minutes. Don't continue until your PayHOA site shows up.

  3. Set up root domain forwarding. In GoDaddy's Forwarding section, click Add Forwarding for Domain (not Subdomain). Forward to https://www. your domain, Forward type Permanent (301). "Choose Permanent (301), not Temporary, and no masking."

  4. Check and wait for validation. Confirm the www CNAME still points to your PayHOA address, then click Verify DNS configuration.

Warning: when you set up forwarding, GoDaddy (and some other registrars) may offer to point www at the root domain too. Don't accept. It undoes the www record and the domain stops loading.

Domain forwarding (Network Solutions and similar)

"This provider cannot point the root domain at a hostname, so the root domain forwards to www. Only www serves your site." Add the www CNAME and the two certificate records, confirm https://www. your domain loads your site (this can take up to 30 minutes), and only then forward the root to https://www. your domain as a permanent (301) redirect.

The certificate records

The second table, Records that prove you own the domain (HTTPS certificate), has two CNAME records with names that start with an underscore, like _a1b2c3… and _a1b2c3….www. "Add these too. Without them the certificate cannot be issued and your domain will not verify."

  • Copy the Name (Host) and Value of each exactly.

  • The dialog shows only the part of the name before your domain. If your registrar adds your domain to names on its own (most do), paste the name as shown. If it doesn't, add your domain at the end.

  • Leave these records in place after the domain verifies. The certificate needs them to renew.

The dialog is written for a root domain such as oakwoodhoa.com. If you're connecting a subdomain, such as hoa.example.com, the record names it shows (@, www and the certificate names) leave out your subdomain and won't work as shown. See Troubleshoot your custom domain before you add any records.

Step 4: Verify

  1. Back in PayHOA, click Verify DNS configuration.

  2. Read the result:

    • "Verified! Your custom domain DNS records look good." Click Continue to finish.

    • "Validation in progress." or "DNS isn't live yet." Your records haven't been picked up yet. Click Complete verification later to close the dialog, and come back to verify later (below).

    • "Needs attention." followed by a message. See Troubleshoot your custom domain.

Verified! means the certificate was issued. It doesn't prove your domain already sends visitors to PayHOA. After you close the dialog, check DNS status on the Custom domain card: if it reads Points elsewhere, your www or root records still need fixing. See Troubleshoot your custom domain.

When it's verified, the last step says "Your domain is all set!". With GoDaddy or domain forwarding, your site is served at https://www. your domain, and the root redirects there once forwarding is on. With the other choices, both your domain and www work. Your .site.payhoa.com address keeps working too.

Come back and click Verify

Nothing checks your domain on its own. If you closed the dialog before it verified, the domain stays Pending verification until someone clicks Verify, even after your records are correct.

  1. Open the Domain tab.

  2. On the Custom domain card, click Verify.

The certificate usually takes about 30 minutes after your records are in place, and the dialog says it can take up to 48 hours. Check back a few times. If the domain is still pending after about 3 days, the certificate request has expired. Verify then says "SSL certificate cannot be issued": fix your records, then save the domain again (Troubleshoot your custom domain).

PayHOA doesn't send an email when the domain verifies. Check the card.

Read the Custom domain card

Field

What it shows

URL

Your domain, for example https://oakwoodhoa.com.

DNS status

Pending verification (not verified yet; click Verify), Verified (working), or Points elsewhere (your domain still reaches another host; see Troubleshoot your custom domain).

Last verified

When it last verified, or Never.

The buttons are Verify (only while the domain isn't verified), Remove and Edit.

After it verifies

Publish your site once more (Preview, publish and version history). That updates your pages so search engines list them under your own domain instead of the .site.payhoa.com address.

Change or remove the domain

Edit opens the setup again so you can see the records or change the domain. On a verified domain, you first see Edit custom domain?: "Saving the domain again resets its verified status and requests a new certificate until your DNS is checked again." Click Continue only if you need to. After saving, the domain shows Pending verification again: add any new certificate records and click Verify.

Remove asks Remove custom domain?: "Visitors using {your domain} will no longer reach your site. It stays available at {your-name}.site.payhoa.com." Click Remove domain. Then delete the PayHOA records at your registrar, or point the domain elsewhere.

Once a domain is saved, the switch on the Custom domain card no longer shows. The only way to disconnect the domain is Remove.

If you take your site offline, your domain stays saved here with its certificate. See Take your site offline or start over.

What's next

Did this answer your question?