Quick Answer
How do you set up a dedicated sending domain?
Go to Settings → Email Services, open Dedicated Domain and IP, enter the sending subdomain you want to use, and add the DNS records BizStackPro provides. After DNS propagation and verification, set the domain as active or default for sending.
Improving Deliverability by Controlling Your Sending Identity
Some email configurations can show shared sending infrastructure in message headers, sometimes appearing as “sent via.”
A dedicated sending domain gives you more control over how your outbound email is authenticated and helps separate your email sending reputation from your primary domain.
Using a dedicated sending subdomain also gives mailbox providers a clearer, more consistent sending identity to evaluate.
Recommended approach
Use a unique subdomain, such as communication.yourdomain.com, rather than the root domain so your sending activity can be managed separately.
Dedicated Sending Domain at a Glance
Before You Begin
Make sure you can update the DNS records for the domain you plan to use for sending.
- Choose a dedicated sending subdomain.
- Have access to your domain's DNS settings.
- Be prepared to add the records provided by BizStackPro.
- Allow time for DNS propagation after making changes.
- Check existing SPF records before adding new SPF information.
Steps to Configure a Dedicated Sending Domain
Step 1: Open Email Services
In BizStackPro, go to Settings → Email Services.
Step 2: Open Dedicated Domain and IP
Select Dedicated Domain and IP, or the dedicated-domain option available inside Email Services.
Step 3: Enter the Sending Subdomain
Enter the subdomain you want to use for sending, such as communication.yourbrand.com.
Step 4: Choose the DNS Setup Method
Use Auto-configure DNS when supported, or complete a manual DNS setup using the records provided by BizStackPro.
Step 5: Add the DNS Records
Add the required DNS records and allow time for them to propagate.
Step 6: Verify and Activate
After the domain is verified, set it as active or default for sending.
If verification fails
The most common causes are DNS propagation time, a typo in one of the records, or duplicate or conflicting SPF entries.
Important DNS Records: SPF, DKIM, and DMARC
SPF
SPF authorizes the sending servers that are allowed to send email for your domain.
DKIM
DKIM adds a cryptographic signature that mailbox providers can verify.
DMARC
DMARC defines how messages should be handled when SPF or DKIM checks fail and can provide reporting.
Watch for duplicate SPF records
SPF should generally be configured as one record per hostname. If an SPF record already exists, the required sending information is typically merged into that record instead of creating a second SPF TXT record.
Deliverability Notes for Bulk Sending
Higher-volume senders increasingly need properly authenticated email using SPF, DKIM, and a DMARC policy.
Use a unique sending subdomain and keep your sending patterns consistent rather than making sudden changes in volume.
Example DMARC TXT record format
Type: TXT Name: _dmarc.your-subdomain Value: v=DMARC1; p=none; rua=mailto:[email protected]
Use the exact host or name BizStackPro recommends for your sending subdomain.
Best Practices
Frequently Asked Questions
Why should I use a dedicated sending domain?
Do I need DNS records for the dedicated domain?
What if DNS propagation takes too long?
Can I use my root domain instead of a subdomain?
Continue Learning
Continue with related Email & SMTP guides for authentication, domain reputation, sender requirements, and dedicated sending infrastructure.
