'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Microsoft 365 DNS Setup Only Allowing TXT Records
Question details
The user is configuring a custom domain in Microsoft 365 but finds that the interface restricts them to adding only TXT records, preventing the configuration of necessary CNAME, A, or MX records.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Setting up or managing custom domain DNS records within the Microsoft 365 admin center.
- Observed behavior
- The domain management interface exclusively exposes TXT records and does not provide any options or buttons to add CNAME, A, or MX records directly.
Ensure you have global admin access to your Microsoft 365 account and the login credentials for your external domain registrar (e.g., GoDaddy, Namecheap, Cloudflare).
Add DNS Records at Your Authoritative Domain Registrar
Since Microsoft 365 is not your authoritative DNS host, you must add the required service records directly through your domain provider's control panel.
When connecting a domain, Microsoft 365 first requires a TXT record to verify ownership. If your domain's nameservers point to an external registrar rather than Microsoft, the Microsoft 365 portal acts in a limited capacity and will not let you manage other critical records (like MX for email) directly.
To resolve this, you need to copy the specific DNS values provided by the Microsoft setup wizard and paste them into the DNS zone editor of your actual domain host.
Check your domain's authoritative nameservers using a public WHOIS lookup tool to determine which company is currently hosting your DNS.
Navigate to your DNS hosting provider's website and log in to your account control panel.
Locate the DNS management, advanced DNS, or zone editor section for your specific custom domain.
Create new entries for the CNAME, A, MX, and SRV records using the exact destination values, ports, and priorities supplied by the Microsoft 365 domain setup wizard.
Save your newly added DNS records. Allow up to 48 hours for the changes to propagate globally across all DNS servers.
Looking for a Simpler Office Solution? Try WPS Office
Managing complex Microsoft 365 setups, domains, and subscriptions can be overwhelming. If your primary goal is to efficiently create and edit documents, spreadsheets, and presentations without the administrative hassle, WPS Office offers a free, lightweight, and highly capable alternative.
Frequently Asked Questions
Why does Microsoft 365 only ask for a TXT record initially?
Microsoft 365 requires a TXT record first to securely verify that you actually own the custom domain you are attempting to add. This prevents unauthorized users from claiming domains they do not own.
Can I let Microsoft 365 manage my DNS records automatically?
Yes. If you change your domain's nameservers at your registrar to point directly to Microsoft 365, the portal will gain authoritative control and automatically configure your CNAME, A, and MX records.
What happens if my MX records are not configured correctly?
If your MX (Mail Exchanger) records are missing or incorrect at your DNS host, your Microsoft 365 Exchange mailboxes will be completely unable to receive emails from external senders.
How long does it take for Microsoft 365 to recognize my new DNS records?
While some DNS hosts update almost instantly, standard DNS propagation can take anywhere from a few minutes up to 48 hours to fully resolve globally.
