How do I tell "not resolving" from "resolving to wrong value"?

dig CNAME msoid.yourdomain.com +short. Empty output = not resolving (NXDOMAIN or no record). A value that isn't clientconfig.microsoftonline-p.net = wrong value. The article you want depends on which: this one for empty output, the "doesn't match" one for wrong value.

Why does dig +trace help here specifically?

It walks the DNS hierarchy from the root down, showing each delegation. If the trace stops at the registrar's nameservers without a delegation to your DNS provider, the nameserver records at the registrar are wrong. If trace gets to your provider but they answer NXDOMAIN, the record was never added there.

An AAAA record on the same name — why would it break a CNAME lookup?

Strict CNAME semantics: a name with a CNAME can't have any other record type at the same name (RFC 1034 §3.6.2). When both are published, some resolvers reject the answer entirely and others return inconsistent results. Delete the AAAA on msoid; the CNAME alone covers both IP families through the alias chain.

I waited 48 hours and Microsoft still says not resolving.

At 48 hours propagation isn't the issue. Either the record isn't actually published (re-check the panel, save again), or the record exists but at the wrong host (msoid vs msoid.yourdomain.com depending on UI conventions). Verify with an external tool like dnschecker.org — if a different region shows the record fine, propagation in Microsoft's network is your remaining variable.

Fix: MSOID Record Not Resolving (msoid.clientconfig.microsoftonline-p.net)

4 min read

15.03.2025

If your MSOID CNAME record is not resolving, it means Microsoft cannot verify your domain for authentication, which may cause issues with Microsoft 365, Azure AD, and Single Sign-On (SSO). This problem often leads to user login errors, client application configuration issues, and problems using Microsoft cloud services.

Fixing MSOID Record Not Resolving error — MSOID record published but not resolving — typical Microsoft 365 setup failure.

For background and the closely-related "doesn't match expected values" variant, see MSOID DNS Record — What It Is and How to Configure It, Verify That the MSOID Record Works, Fix: "The Record We Detected Doesn't Match All the Expected Values", and Understanding clientconfig.microsoftonline-p.net (MSOID CNAME Record).

Verify if the MSOID Record Exists

Check if your MSOID CNAME record is properly configured in DNS.

Using Linux/macOS Terminal

Run the command:

dig CNAME msoid.yourdomain.com +short

Expected Output:

clientconfig.microsoftonline-p.net.

Using Windows Command Line

Run the command:

nslookup -type=CNAME msoid.yourdomain.com

Expected Output:

msoid.yourdomain.com canonical name = clientconfig.microsoftonline-p.net.

Using Online Tools

Check propagation on these sites:

If the record doesn't appear, your MSOID CNAME record is missing or configured incorrectly.

Problem	Solution
MSOID record missing	Add the correct CNAME record to DNS
DNS changes not detected	Wait 24-48 hours for propagation
Cloudflare DNS issues	Set proxy to "DNS Only" (Grey cloud ??)
Conflicting CNAME records	Remove duplicate or incorrect CNAME records
Incorrect MSOID CNAME value	Ensure target is `clientconfig.microsoftonline-p.net` (no prefix or suffix)
Record blocked by firewall	Check firewall settings and network rules
DNS server cache issues	Clear DNS cache on local router or ISP

Task	Steps
Check if MSOID resolves	Use `dig CNAME msoid.yourdomain.com +short`
Fix MSOID record	Set CNAME to `clientconfig.microsoftonline-p.net`
Flush DNS and check propagation	Use `ipconfig /flushdns` and WhatsMyDNS
Check in Microsoft 365	Go to Admin Center > Domains > Verify
Troubleshoot	Check conflicting records, proxy settings, propagation delays

Fix: MSOID Record Not Resolving (msoid.clientconfig.microsoftonline-p.net)

Verify if the MSOID Record Exists

Using Linux/macOS Terminal

Using Windows Command Line

Using Online Tools

Check and Fix the DNS Record

Add or Fix the CNAME Record

For cPanel Users

For Cloudflare Users

For GoDaddy, Namecheap, or Other Registrars

Flush DNS Cache and Wait for Propagation

Flush Local DNS Cache

Check Propagation Delays

Re-verify in Microsoft 365

Check in Microsoft 365 Admin Center

Troubleshooting if MSOID Still Won't Resolve

Summary

Fix: MSOID Record Not Resolving (msoid.clientconfig.microsoftonline-p.net)

Verify if the MSOID Record Exists

Using Linux/macOS Terminal

Using Windows Command Line

Using Online Tools

Check and Fix the DNS Record

Add or Fix the CNAME Record

For cPanel Users

For Cloudflare Users

For GoDaddy, Namecheap, or Other Registrars

Flush DNS Cache and Wait for Propagation

Flush Local DNS Cache

Check Propagation Delays

Re-verify in Microsoft 365

Check in Microsoft 365 Admin Center

Troubleshooting if MSOID Still Won't Resolve

Summary

Выберите валюту