Business email and DNS configuration
When business email stops arriving or legitimate messages land in spam, start by checking how your domain, mail provider and sending applications fit together. IT Service reviews the agreed systems, documents the findings and scopes the changes needed for your setup.
Discuss your email and DNS setup
When this service is useful
- Your business uses Microsoft 365, Google Workspace or another email provider, but DNS ownership is unclear.
- A website, invoicing tool or other application sends email using your domain.
- You are preparing a provider change and need a documented DNS and mail-flow plan.
- Authentication failures or suspicious use of your domain need investigation.
What we review
We map domain registration, authoritative DNS, the receiving mail provider and legitimate sending services. The agreed review covers relevant MX, TXT and CNAME records, SPF configuration, DKIM signing and DMARC alignment and policy. Provider-specific values are taken from your actual configuration, rather than copied from a generic example.
We distinguish verified observations from information supplied by your team. Missing access or evidence is recorded as an open item.
What you receive
- An inventory of the agreed domain, DNS and email dependencies and their owners.
- A findings list with evidence, impact, priorities and unresolved questions.
- A change plan showing the intended records, dependencies, validation and rollback steps.
- A handover record for any separately authorized changes, including the checks completed and remaining actions.
The assessment comes first. Implementation and subsequent monitoring are agreed separately; they are not automatically included in every review.
How the work proceeds
We agree the scope and authorized access, inventory legitimate senders, review the configuration and explain the findings. DNS or provider changes follow only after approval of the change plan. Validation is agreed in advance; actual test messages are sent only to approved recipients. A mail-provider migration requires its own cutover and rollback plan.
Limits of the service
Authentication helps receivers assess messages from your domain; it does not guarantee inbox placement. Content, sender reputation and recipient-side decisions can also affect delivery. We do not promise a zero-downtime migration or guaranteed delivery rates.
Mailbox migration, data recovery, ongoing incident response and paid provider licenses are scoped separately. Passwords, tokens and private email contents do not belong in the enquiry form or public report.
FAQ
Do you support Microsoft 365 and Google Workspace?
Yes, these are among the platforms covered by the existing service. The required records and access depend on the provider and your actual sending systems.
Can you guarantee that our messages will leave the spam folder?
No. We can investigate configuration and authentication issues and document the checks, but recipients ultimately decide how messages are handled.
Will you change our DNS during the initial review?
Only after the specific change plan is approved. A review does not automatically authorize an MX change or stricter DMARC policy.
Is moving our mailboxes included?
Not automatically. A mailbox migration needs a separate scope covering data, users, timing and rollback.
What should we send with the first enquiry?
Your public domain, email provider, a description of the problem and the systems known to send mail. Do not send passwords, keys or unredacted private messages.
Do you offer ongoing monitoring?
Monitoring and maintenance can be agreed separately. The handover identifies which checks were completed and who owns the next actions.