Connecting your domain and setting up DNS records
Email deliverability is not magic; it is a technical requirement. If your emails are landing in spam, it is almost certainly because your domain is not properly authenticated. Connecting your domain to BAMF OS requires configuring specific DNS records to prove to receiving servers that you are a legitimate sender.
The first record you must configure is SPF (Sender Policy Framework). SPF acts as a guest list for your domain. It tells receiving servers which IP addresses and services are authorized to send email on your behalf. If you send an email from a server not listed in your SPF record, it will likely be rejected or marked as spam.
Next is DKIM (DomainKeys Identified Mail). DKIM adds a cryptographic signature to your emails. When an email is received, the server checks this signature against the public key published in your DNS records. This ensures that the email was not altered in transit and confirms it originated from your domain.
Finally, you must implement DMARC (Domain-based Message Authentication, Reporting, and Conformance). DMARC ties SPF and DKIM together. It tells the receiving server what to do if an email fails authentication. You can instruct the server to do nothing, quarantine the email, or reject it entirely. A strict DMARC policy protects your domain from spoofing and phishing attacks.
To set these up, log into your domain registrar (e.g., GoDaddy, Cloudflare, Namecheap) and navigate to the DNS management section. Add the specific TXT and CNAME records provided in your BAMF OS email settings. Once added, it can take up to 24 hours for the changes to propagate globally.
Do not skip this step. Sending unauthenticated email damages your domain reputation, and a ruined domain reputation is incredibly difficult to repair. Take the time to configure your DNS records correctly before launching any outbound campaigns.