# Using a Custom Domain

Send Internal Communication emails from your company’s domain. Set up and verify DNS records in **Communications > Settings > DNS Settings**.

**Note:** Your custom domain must be **verified** before communication emails can be sent from it. If unverified, emails will be sent from **[comms@nectarhr.com](mailto:comms@nectarhr.com)**.

---

# Add your custom domain

1. Navigate to **Communications > Settings > DNS Settings.**

If you don’t see your domain, or your domain does not have a green checkmark next to _Verified_, proceed to step 2.  
Otherwise, you’re all set 👏

2. Click **_Add Custom Domain_**.

3. Select your DNS provider (i.e., the hosting provider associated with your custom domain).

4. Enter your custom domain in the **From Domain** field.

5. Click **_Continue_**.

---

# Install DNS records

1. Create each of the four generated DNS records in your domain provider’s dashboard.  
   
   - The `_dmarc` record may already exist for your domain. You just need one, and the generated value provides a minimal example.
   - Consult your provider’s documentation for specific steps.

For example:  
     - [Cloudflare: Create DNS Records](https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/)  
     - [GoDaddy: Manage DNS Records](https://www.godaddy.com/help/manage-dns-records-680)

---

# Verify installed records

1. Once installed, check **I have installed the records below**, then click **Verify DNS Records**.

2. If verification is successful, you should see a screen like this:

3. Verification usually completes within minutes, but in some cases it can take up to **72 hours**. Don’t delete your DNS records or start over if verification doesn’t happen immediately.  
If your domain still shows as unverified or you experience issues, check the **Troubleshooting section** below.

---

# Troubleshooting Help

#### **My custom domain is still failing to verify one or more of my DNS records:**
- Verification failures often occur when DNS records are added to an internal or private DNS zone (e.g., **BlueCat**).
- Make sure the records are created in a **public DNS zone** that’s reachable from the internet.
- SendGrid (which handles the verification process) must be able to access your DNS records publicly to confirm ownership. If the records exist only in an internal or private DNS environment, verification will not succeed. - DNS changes may take up to 72 hours to propagate fully across the internet. Avoid removing or repeatedly disconnecting and retrying the verification process during this period, as this can lead to further delays.
- Double-check the DNS records for accuracy, including spelling and formatting. Use online tools to verify that your DNS records are publicly accessible.
- Contact your DNS provider if you encounter issues with making the records public.

## Common DNS setup issues

|     |     |     |
| --- | --- | --- |
| **Issue** | **Description** | **Resolution** |
| **Incorrect Record Type** | Entering the wrong DNS values or types. | Double-check your entries line-by-line against the keys provided in Nectar settings. |
| **Root Domain Auto-Appending** | Domain providers (like Squarespace or BlueCat) automatically append your root domain to the hostnames, breaking the record. | Add a trailing period to the end of the hostname entry (e.g., `em4525.yourdomain.com.`). |
| **Verification Lag** | Changes do not appear immediately in Nectar. | DNS propagation can take up to 24 hours. Wait and attempt verification again the following day. |
| **SendGrid Conflict** | Your organization already uses an active SendGrid account, causing a DKIM key clash. | Contact Nectar Support to have unique, non-conflicting keys manually assigned to your account. |
| **Strict SPF Record Blocking** | Your existing domain SPF record ends in a strict `-all` (hard fail) syntax, causing security systems to reject unauthorized Nectar mail. | Ask your IT team to explicitly update your domain's SPF record to include SendGrid. Example: `v=spf1 ... include:sendgrid.net -all`. |

**Note:** SPF setup is optional for most organizations because DKIM handles identity verification independently. The only exception is if your organization uses a strict `-all` SPF record, which requires adding `include:sendgrid.net`. Subdomain sending is not supported; Nectar must send directly from your root domain.