Support
FAQ
What DNS records should our IT person add?
For a Vercel-hosted launch, use A @ 76.76.21.21 and CNAME www cname.vercel-dns.com unless the domain screen gives different records for your setup.
In-depth answer+
Domain setup connects a public hostname to the published site. The risky part is DNS: website records can be changed without disrupting email, but MX, SPF, DKIM, DMARC, donation, and other provider records should not be removed.
Technical checks
- Identify the DNS provider, not just the registrar. The registrar sells the domain; DNS may be hosted elsewhere.
- Before editing records, screenshot existing DNS settings and preserve email records such as MX, SPF, DKIM, and DMARC.
- Check whether the requested hostname is root domain, www, subdomain, or preview domain. Each can require different records.
- Allow for DNS propagation. Some providers update quickly, while cached records can take longer to resolve globally.
Escalation details to include
- Send the domain, DNS provider, screenshot of current records, desired live URL, and any verification error.
- If email is affected, stop changing records and include the mail provider name, changed records, and timing.
- For SSL or verification failures, include both root and www behavior if they differ.
Reference notes
- A record: points a root domain to an IP address when required by the hosting provider.
- CNAME: points a hostname such as www to another hostname.
- TXT: used for verification, SPF, DKIM, and other provider ownership records.
- MX: routes email. Do not delete MX records when launching a website.
Should we remove old DNS records?
No. Keep MX, TXT, email, donation, school, and verification records unless your IT provider confirms they are obsolete.
In-depth answer+
Domain setup connects a public hostname to the published site. The risky part is DNS: website records can be changed without disrupting email, but MX, SPF, DKIM, DMARC, donation, and other provider records should not be removed.
Technical checks
- Identify the DNS provider, not just the registrar. The registrar sells the domain; DNS may be hosted elsewhere.
- Before editing records, screenshot existing DNS settings and preserve email records such as MX, SPF, DKIM, and DMARC.
- Check whether the requested hostname is root domain, www, subdomain, or preview domain. Each can require different records.
- Allow for DNS propagation. Some providers update quickly, while cached records can take longer to resolve globally.
Escalation details to include
- Send the domain, DNS provider, screenshot of current records, desired live URL, and any verification error.
- If email is affected, stop changing records and include the mail provider name, changed records, and timing.
- For SSL or verification failures, include both root and www behavior if they differ.
Reference notes
- A record: points a root domain to an IP address when required by the hosting provider.
- CNAME: points a hostname such as www to another hostname.
- TXT: used for verification, SPF, DKIM, and other provider ownership records.
- MX: routes email. Do not delete MX records when launching a website.
Can someone else connect the domain?
Yes. Use the domain page to send clean instructions to your office manager, IT provider, registrar contact, or whoever controls DNS.
In-depth answer+
Domain setup connects a public hostname to the published site. The risky part is DNS: website records can be changed without disrupting email, but MX, SPF, DKIM, DMARC, donation, and other provider records should not be removed.
Technical checks
- Identify the DNS provider, not just the registrar. The registrar sells the domain; DNS may be hosted elsewhere.
- Before editing records, screenshot existing DNS settings and preserve email records such as MX, SPF, DKIM, and DMARC.
- Check whether the requested hostname is root domain, www, subdomain, or preview domain. Each can require different records.
- Allow for DNS propagation. Some providers update quickly, while cached records can take longer to resolve globally.
Escalation details to include
- Send the domain, DNS provider, screenshot of current records, desired live URL, and any verification error.
- If email is affected, stop changing records and include the mail provider name, changed records, and timing.
- For SSL or verification failures, include both root and www behavior if they differ.
Reference notes
- A record: points a root domain to an IP address when required by the hosting provider.
- CNAME: points a hostname such as www to another hostname.
- TXT: used for verification, SPF, DKIM, and other provider ownership records.
- MX: routes email. Do not delete MX records when launching a website.
What if we do not know who manages our domain?
That is common. Check old website invoices, email-provider records, the parish office manager, or the IT provider. The domain page can still prepare instructions for whoever has access.
In-depth answer+
Domain setup connects a public hostname to the published site. The risky part is DNS: website records can be changed without disrupting email, but MX, SPF, DKIM, DMARC, donation, and other provider records should not be removed.
Technical checks
- Identify the DNS provider, not just the registrar. The registrar sells the domain; DNS may be hosted elsewhere.
- Before editing records, screenshot existing DNS settings and preserve email records such as MX, SPF, DKIM, and DMARC.
- Check whether the requested hostname is root domain, www, subdomain, or preview domain. Each can require different records.
- Allow for DNS propagation. Some providers update quickly, while cached records can take longer to resolve globally.
Escalation details to include
- Send the domain, DNS provider, screenshot of current records, desired live URL, and any verification error.
- If email is affected, stop changing records and include the mail provider name, changed records, and timing.
- For SSL or verification failures, include both root and www behavior if they differ.
Reference notes
- A record: points a root domain to an IP address when required by the hosting provider.
- CNAME: points a hostname such as www to another hostname.
- TXT: used for verification, SPF, DKIM, and other provider ownership records.
- MX: routes email. Do not delete MX records when launching a website.
Why does SSL or verification still say pending?
DNS can take time to propagate, and old records can conflict. Confirm the exact records, avoid changing mail records, then use Check Connection again from the domain screen.
In-depth answer+
Domain setup connects a public hostname to the published site. The risky part is DNS: website records can be changed without disrupting email, but MX, SPF, DKIM, DMARC, donation, and other provider records should not be removed.
Technical checks
- Identify the DNS provider, not just the registrar. The registrar sells the domain; DNS may be hosted elsewhere.
- Before editing records, screenshot existing DNS settings and preserve email records such as MX, SPF, DKIM, and DMARC.
- Check whether the requested hostname is root domain, www, subdomain, or preview domain. Each can require different records.
- Allow for DNS propagation. Some providers update quickly, while cached records can take longer to resolve globally.
Escalation details to include
- Send the domain, DNS provider, screenshot of current records, desired live URL, and any verification error.
- If email is affected, stop changing records and include the mail provider name, changed records, and timing.
- For SSL or verification failures, include both root and www behavior if they differ.
Reference notes
- A record: points a root domain to an IP address when required by the hosting provider.
- CNAME: points a hostname such as www to another hostname.
- TXT: used for verification, SPF, DKIM, and other provider ownership records.
- MX: routes email. Do not delete MX records when launching a website.
Contact us
Include the domain, current site or dashboard URL, what changed, what you expected, and a screenshot when the issue is visual.
Need urgent help?
We will get back to you as soon as possible.