Domain setup is often the first integration step that leaves your code editor. You add a domain in Sendar, receive DNS records and then make changes in a separate provider's control panel. Most confusion comes from the names and values of those records, not from the email request itself.
Know where DNS is managed
Your domain registrar and authoritative DNS provider may be different companies. Make changes where the active nameservers are managed. Editing an inactive DNS zone will not change the answers that Sendar or receiving systems see.
Before editing anything, save the current records relevant to email. This gives you a reference if a hostname is entered incorrectly. Preserve the records supporting existing business mail and other legitimate senders.
Copy the exact record and hostname
Use the records generated for your account rather than a value copied from a tutorial. Some DNS interfaces append your domain to the host field. Entering the full name in a field that already adds the suffix can create a doubled hostname.
Check record type, host and value separately. A value that looks correct under the wrong name cannot verify the intended domain. For DKIM checks, the selector is part of the lookup name; testing a different selector does not test the key you just published.
Allow for cached answers
DNS changes can take time to become visible through recursive resolvers. Repeatedly deleting and recreating a record during that window can make troubleshooting harder. Compare the authoritative configuration with the public result, then recheck verification in Sendar.
Our domain checker provides a public DNS snapshot for SPF, DKIM and DMARC. It is useful for spotting missing records, but it does not recursively evaluate SPF includes or DMARC parent inheritance. It also cannot tell you whether a particular message will reach an inbox.
Finish with a controlled message
After Sendar marks the domain verified, use an address on that domain as the sender in a controlled test. Inspect the returned record and the received message where available. Keep DNS verification and delivery validation as separate checks: each answers a different question about the integration.