You can host your website at TekLan while Microsoft 365 handles your email. Microsoft supplies the exact DNS values for your tenant; add those values to the authoritative DNS zone without replacing the records that keep your website online.
Before you begin: Open the Microsoft 365 admin centre and start the domain setup there. Use the records displayed for your domain. Microsoft may change or tailor values, so do not copy example values from an unrelated website.
1. Find where DNS is managed
Check the domain’s authoritative nameservers. The DNS zone might be at TekLan, your registrar, Cloudflare, or another provider. Add records only in that active zone; editing a dormant copy has no public effect.
If the domain uses TekLan’s hosting DNS, open the website in Enhance and go to its DNS management area. Take a screenshot or export of the current records before making changes.
2. Verify the domain with Microsoft
Microsoft normally asks you to add a TXT record so it can prove you control the domain. Copy the host/name and value exactly, save the record, then return to Microsoft 365 and choose the verification option.
Verification does not usually redirect email by itself. Leave the TXT record in place unless Microsoft explicitly says it is no longer required.
3. Add the Microsoft 365 mail records
The setup wizard will show the records needed for the services you selected. These commonly include an MX record for incoming mail, an SPF TXT record, and one or more CNAME records for service discovery. Add only the records shown for your tenant.
Remove or replace an old MX record only when the Microsoft mailboxes are ready to receive messages. Two unrelated mail systems cannot normally share delivery for the same domain merely by keeping both sets of MX records.
4. Avoid creating two SPF records
A domain should publish one SPF record. If a valid SPF TXT record already exists because your website or another service sends email, merge the authorised senders into a single policy instead of adding a second v=spf1 record.
If you are unsure which services send as your domain, stop and inventory them. Contact forms, invoicing software, newsletters, support desks, and booking systems may all need consideration.
5. Enable DKIM in Microsoft 365
Microsoft will provide tenant-specific DKIM CNAME records. Publish both selectors, wait for DNS to resolve, then enable DKIM for the domain in the Microsoft security or Defender administration area. Confirm the status rather than assuming publication automatically enabled signing.
6. Introduce DMARC carefully
DMARC tells receiving providers what to do when SPF or DKIM alignment fails. Begin with reporting while you verify every legitimate sender, review the reports, then move towards quarantine or reject when you are confident. A strict policy introduced before all senders are aligned can reject your own messages.
7. Test website and email separately
- Send to the new mailbox from an unrelated external address.
- Reply and confirm the external address receives it.
- Check message headers for SPF, DKIM, and DMARC results.
- Submit every website contact form and check its recipient.
- Load the website on both the root domain and
www.
Common problems
If Microsoft cannot see a record, confirm the authoritative nameservers, exact host label, record type, and whether the DNS panel automatically adds the domain name. If incoming mail still reaches the old provider, check the public MX answer and allow for its previous TTL.
For more DNS help, see Setting Up DNS Records. If TekLan controls the active zone and you want us to check it, open a ticket with the Microsoft values and redact any passwords.