Link to home
Start Free TrialLog in
Avatar of Theo
Theo

asked on

Verifying domain ownership for Office365

I own the domain richel.org . It is registered at hover.com, and I have Olm.net host a website for me with that domain name.

Now to verify my ownership of the domain name, Microsoft wants me to add a txt record at my DNS hosting provider.
Well at my registrar I am able to do that myself. Hover.com allows me to add such a record. I added it, and waited more than 72 hours, nut nslookup couldnt find it and neither did MS.
In its wizard for registrars/providers Office 365 offers Hover.com, but not Olm.net. I have now removed the new record from Hover and asked Olm.net to add it, which they have just done for me.
Suppose after  a few hours the OLM.net newly added DNS-record responds (with NSLookup, how can I then verify this in Office 365?
Avatar of footech
footech
Flag of United States of America image

So if you run a command like
nslookup -q=soa yourdomain.com 8.8.8.8
the primary name server should give you a clue where you need to create any records if you don't know where your DNS is managed.  Sometimes the name is obvious which organization it's associated with, other times not so much.

You said that MS didn't find your earlier record, so you know which button to push to check.  That's it.  You could also do it with PowerShell, but you're already familiar with checking through the web interface, so...
Avatar of Theo
Theo

ASKER

Thank you, I do know a bit how to use nslookup, but that is outside Office365 I am supposed to verify it inside Office 365 and I see no way to connect to OLM there. Office365 doesnt automatically see that new record is in my DNS, otherwise the verification button would be useless.
The check that Office 365 does for DNS isn't aimed at a particular provider.  It just checks that the record is available like any other client on the internet.  Like any client on the internet, there is a process of querying other DNS servers for the right info.  If the record is resolvable to internet clients, then Office 365 should be able to see it.
Avatar of Theo

ASKER

That may be true, but I do have to select a provider first before I can verify from within Office365
ASKER CERTIFIED SOLUTION
Avatar of footech
footech
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Theo

ASKER

OK, then all I have to do is wait till the record propagates
That's correct.  Though technically, it's inconsequential if the record hasn't propagated to all DNS servers, it just needs to be resolvable by whatever MS machine is doing the check in order to pass the verification.  When I've done it, often the record was detected in 15 minutes.
Avatar of Theo

ASKER

Doesnt it matter that I am in the Netherlands and the host in Connecticut?
Avatar of Theo

ASKER

It works now, thanks.