> ## Documentation Index > Fetch the complete documentation index at: https://partner-help.letsdothis.com/llms.txt > Use this file to discover all available pages before exploring further. # Custom Domains > Verify your own domain so campaign and transactional emails are sent from your address instead of a Let's Do This one. You need write access to your organizer account to reach **Settings → Branding → Custom Domains**, and access to your domain's DNS provider to complete verification. If you do not manage your own DNS, you can copy the records and send them to whoever does — see [Handing the records to your DNS administrator](#handing-the-records-to-your-dns-administrator). By default, your campaign and transactional emails are sent from a Let's Do This address. Verifying a custom domain lets you send from your own address instead, such as `events@yourdomain.com`. Participants recognize your address, so they are more likely to open the email and less likely to treat it as spam. Verify a domain well before you plan to send. DNS changes can take up to 48 hours to take effect, so this is not something to start on the morning of a send. You only need to do it once per domain: after that, the domain stays available for every campaign and transactional email you build. Verification covers both the **from address** and the **reply-to address**. Both are set the same way: you type the part before the @ and choose a verified domain from a dropdown, so neither can point at a domain you have not verified. Until you have at least one verified domain, both options stay disabled and your emails send from — and receive replies at — a Let's Do This address. Setup adds two records to your domain: a DKIM record and a Return-Path record. Neither is an MX record, so verifying a domain here does not change where email sent *to* your domain is delivered. Your existing inboxes keep working exactly as they do today. ## Adding and verifying a domain In your dashboard, go to **Settings → Branding → Custom Domains**. The page lists every domain you have added. If you have not added one yet, it shows **No domains added yet.** Click **Add domain** and enter the domain you want to send from, such as `example.com`. You can paste a full email address or a website address instead — `events@example.com` or `https://www.example.com` both reduce to `example.com`. If what you enter is not a valid domain, you see **Please enter a valid domain.** and the button stays disabled. Click **Add domain** again to save it. The domain field locks, the status shows **Pending verification**, and the **DNS records** section appears with the records you need to add. Add the DKIM and Return-Path records exactly as shown. Each one gives you a **Host** and a **Value** you can copy directly. Leave this page open — you can come back to it at any time from the domain's **Continue setup** button. Once the records are in place, click **Refresh status**. When both records come back verified, the window closes and confirms that the domain can now be used for sending. If the records have not propagated yet, the statuses stay as **Pending**. Wait and refresh again — there is no limit on how many times you can check. ## The two records you add | Record | Type | Example host | What it does | | --------------- | ------- | --------------------------- | ---------------------------------------------------------------------------------------------------------- | | **DKIM** | `TXT` | `pm._domainkey.example.com` | Signs your outgoing email so mailbox providers can confirm it genuinely came from you, not from a spoofer. | | **Return-Path** | `CNAME` | `pm-bounces.example.com` | Handles bounce reporting, which protects your sender reputation and helps your email reach the inbox. | Copy the **Host** and **Value** exactly as shown. Some DNS providers append your domain to the host automatically — if yours does, enter the host without the `.example.com` suffix, so `pm._domainkey` rather than `pm._domainkey.example.com`. Adding the suffix twice is the most common reason a record never verifies. ## Handing the records to your DNS administrator Rather than retyping the values or screenshotting the page, click **Copy all instructions** at the bottom of the DNS records section. This copies a plain-text version of everything — both records with their host, value, and current status, plus notes on the host suffix and how long DNS changes take — ready to paste into an email or a support ticket. The copied instructions are written for whoever administers your DNS, so they make sense to someone who has never seen your dashboard. You can re-copy them at any time; the statuses update to reflect how far verification has progressed. If your browser blocks clipboard access, you see **Could not copy the instructions**. Copy the **Host** and **Value** fields individually instead — each one has its own copy control. ## Tracking verification status Each domain appears as a card on the Custom Domains page showing its overall status and the status of each record: * **Verified** — both records have verified. The domain is ready to send from. * **Pending** — one or both records are still outstanding. The card shows which, as `DKIM: Verified · Return-Path: Pending`. Pending domains have a **Continue setup** button that reopens the records. Verified domains do not — there is nothing left to do on them. Opening a pending domain automatically re-checks its records once, so the status you see when the window opens is current. You do not need to click **Refresh status** immediately after opening it. ## A domain is only usable once both records verify A domain counts as verified only when **both** the DKIM and Return-Path records have verified. If one has verified and the other has not, the domain still shows as **Pending** and cannot be selected as a from address. This trips people up when a DNS provider publishes one record faster than the other. It is not a fault — carry on waiting and refreshing until both show **Verified**. ## Using a verified domain to send Once a domain is verified, it becomes available on the **Overview** step of both campaigns and transactional emails, for two separate settings: * **From address** — the address participants see the email came from. Type the part before the @ (such as `events`) and choose your verified domain from the dropdown. * **Reply-to address** — where participant replies are delivered. Set the same way, and also limited to your verified domains. You can point the two at different addresses on the same verified domain — sending from `events@yourdomain.com` while replies go to `support@yourdomain.com`, for example. See [Branding & Custom Domains](/docs/email-communications/branding) and [Transactional emails](/docs/email-communications/transactional-emails) for where these sit in the campaign flow. ## If verification stays pending DNS changes can take up to 48 hours to take effect, so give it time before assuming something is wrong. If a record is still **Pending** after that, check the following at your DNS provider: * The **Host** and **Value** match what the dashboard shows, character for character. * The host suffix is handled correctly for your provider — see [The two records you add](#the-two-records-you-add). * The record was added to the right domain, not to a different one you also manage. * The record type matches: DKIM is a `TXT` record, Return-Path is a `CNAME`. If the records look correct and the domain still has not verified after 48 hours, contact LDT support with the domain name and a screenshot of the records as they appear at your DNS provider. ## Changing or removing a domain The domain field locks as soon as you save it, so you cannot edit a domain after adding it. If you entered the wrong one, or you want to move to a different domain, add the correct one as a new domain — you can have as many as you need, and each is verified independently. There is no option to remove a domain from this page. If you need one taken off your account, contact LDT support.