DNS not replicating to azure, 48 hours ago.

Azure is failing verification because the exact verification records that Microsoft Entra expects aren’t what it’s seeing in the authoritative DNS.

From the screenshots:

• The TXT record MS=ms58934209 is present and visible on public DNS.
• The MX record ms58934209.msv1.invalid. is also present.
• However, there is also an older TXT record MS=ms89377850 and an MX record pointing to sinclairmediagroup-com-au.mail.protection.outlook.com.

For Microsoft 365/Entra domain verification, only the current verification record matters, and it must match exactly what is shown in the Entra portal. Common causes when Azure “can’t see” it even after 48 hours are:

1. Verification record value not exact
   Ensure the TXT value is exactly MS=ms58934209 (including MS=) and that there are no extra spaces or quotes. This is explicitly called out as a common issue.
2. Record not saved in the authoritative zone
   Verification must be done in the DNS zone that is authoritative for the domain. Use an authoritative lookup (for example, with the “Authoritative DNS” option or a tool like Dig web interface) to confirm that the TXT and MX records are present on the authoritative name servers, not just on recursive resolvers.
3. Stale or conflicting verification records
   Having multiple MS= TXT records or multiple MX records used for verification can confuse troubleshooting. Remove any old or unused MS= TXT records and any obsolete msv1.invalid MX records that are not the current value shown in Entra, then keep only the pair that matches the portal.
4. Propagation/negative-cache delay
   Even when public tools show the record, Azure’s validation service may still be using a cached negative response or querying name servers that haven’t updated yet. After cleaning up the records, wait a bit longer and retry verification from the Entra portal.

Recommended steps:

1. In the registrar’s DNS zone for sinclairmediagroup.com.au, leave only:
   • TXT @ MS=ms58934209
   • MX @ ms58934209.msv1.invalid. (priority 32767)
2. Remove any older MS= TXT and obsolete verification MX records.
3. Use an authoritative DNS lookup (TXT and MX) to confirm those two records are visible from the authoritative name servers.
4. Return to Entra portal → Custom domain names → sinclairmediagroup.com.au and select Verify again.

If the authoritative lookup shows the correct records and verification still fails, use the Microsoft 365 admin center domain health check or open a support case, as recommended in the documentation.

References:

• Find and fix issues after adding your domain or DNS records
• "Sorry, we can't find the record you created" error message when you try to verify a domain in Office 365
• Azure DNS troubleshooting guide
• Azure: Help Identify My issue with Automatic Checks - DNS Records