Forum Discussion
Bad registrar on 365 side
Hello,
We created a Microsoft 365 tenant several years ago but never used the online email services.
We added and verifed our domain, which was registered with Orange at the time, and then created some users manually to use PowerBI.
Today, we begin to migrate to Exchange Online. We have installed AD Connect and synchronized some users.
Since creating the tenant, we have changed registrars (to Gandi), but I've noticed that the registrar hasn't been updated in the tenant 365.
An `nslookup` correctly identifies Gandi as our current registrar.
Microsoft has remained with Orange... and this is causing errors in the hybrid Exchange configuration assistant due to bad autodiscover.
How can we "refresh" the registrar on the Microsoft 365 side ?
Thanks for your advises
Nicolas
2 Replies
There is nothing to refresh: the registrar name shown in Microsoft 365 does not control DNS or the Hybrid Configuration Wizard. Manage the records in Gandi, then use Microsoft 365 admin center, Settings, Domains, select the domain, and run Check DNS to validate them.
For an Exchange hybrid deployment, public autodiscover.yourdomain.com must resolve to the published on-premises Exchange endpoint, not Orange or autodiscover.outlook.com; the latter is used after all mailboxes are moved online. Remove any obsolete Autodiscover A, CNAME, or SRV records from Gandi and internal DNS, allow DNS propagation, verify with Resolve-DnsName, then rerun the Hybrid Configuration Wizard
Seems this is due to outdated or incorrect DNS records but not the registrar itself.
https://learn.microsoft.com/en-us/microsoft-365/admin/get-help-with-domains/create-dns-records-at-any-dns-hosting-provider?view=o365-worldwide&tabs=domain-connect
https://practical365.com/make-sure-your-implementation-of-autodiscover-avoids-common-pitfalls/
