Custom Domains

What custom domains provide#

Pro and Enterprise can serve hosted links from a domain or subdomain they control. A single connected domain can host multiple links at separate paths:

example.com/catalog
example.com/menu
example.com/portfolio

One link can be selected as the root content at example.com/. Optional wildcard mode also makes a non-root link available as catalog.example.com.

Before changing DNS#

• Decide whether to use an apex such as example.com or a subdomain such as links.example.com.
• Confirm you can edit DNS at the authoritative DNS provider.
• Check whether the name already serves a website, storefront, or email-related web endpoint.
• Record the existing values before replacing them.

Pointing an existing apex away from another host can take that website offline. Use a dedicated subdomain if the current site must stay where it is.

Connect the domain#

1. In the dashboard, open Custom Domains for the correct personal or team workspace.
2. Select Add domain and enter the domain without https:// or a path.
3. Review the preflight warning if Linkyhost detects an existing website.
4. Choose whether to request wildcard subdomains.
5. Add the exact DNS records shown by the wizard.
6. Return to Linkyhost and select Verify or Re-verify.
7. Wait until both ownership verification and the live DNS check show the domain as working.

The current standard routing records are:

The wizard may also provide one or more TXT records for ownership or wildcard-certificate verification. Copy those values exactly. If the wizard shows a value that differs from this overview, use the wizard's current value.

For Cloudflare-managed DNS, set Linkyhost records to DNS only, not proxied, while verification and certificate issuance complete.

Attach links#

After the domain is working:

1. Open Manage on a link in the same workspace.
2. Select the custom domain.
3. Choose a unique path segment, such as annual-report.
4. Optionally select Set as root domain content for one link.
5. Save and open the displayed custom-domain URL.

You can also connect links from the domain section, including Connect all. Connecting another link does not replace existing links; each receives its own path.

Enable per-file subdomains#

Wildcard mode lets a path link answer at both:

example.com/annual-report
annual-report.example.com

Enable Per-file subdomains on the domain, add the * CNAME shown in the dashboard, and add any certificate-verification TXT record requested. Existing path URLs continue to work whether wildcard mode is on or off.

Domain presentation#

The domain settings can also store:

• a browser-tab title up to 128 characters; and
• a favicon in PNG, ICO, SVG, or WebP format, up to 200 KB.

A square image of at least 180 × 180 pixels is recommended for the favicon.

Verification checklist#

• The record is being edited at the active DNS provider, not merely the registrar account.
• An apex uses the required A value; a subdomain uses the CNAME value.
• Conflicting A or CNAME records have been removed.
• Cloudflare proxying is off for these records.
• All TXT verification values match exactly.
• The dashboard shows both verified ownership and correct live DNS.
• The attached link works at its path in a private window.

DNS caches and certificate issuance can take time. If the status remains broken, open Troubleshooting. Custom-domain serving stops if the workspace no longer has a Pro or Enterprise entitlement.