Office 365 Email Setup

SkidMarkKing · 17 May 2021 at 08:08

Hi guys,

I am setting up my domain with the office 365 email system.

I've gone into 123-reg and added the TXT file (copy and pasted) from the login.microsoftonline.com admin - domain setup page. It's been 12 hours and it still hasn't been verified. I can't proceed to the next step until the TXT records have been updated. The next step is then to do the MX records.

The three videos i've watched all seem to work within 10 minutes.

Should I just keep waiting as it does say 48 hours it could take?

Thank you

Glanza · 17 May 2021 at 08:34

Once you added the TXT record for MX= did you go back into your admin panel to verify?

Post a screenshot of the TXT record from your 123-Reg DNS records.

Deleted member 77746 · 17 May 2021 at 09:07

verify the domain has the TXT record.

nslookup -type=TXT _acme-challenge.domain.com

SkidMarkKing · 17 May 2021 at 17:07

Glanza said:
Once you added the TXT record for MX= did you go back into your admin panel to verify?

Post a screenshot of the TXT record from your 123-Reg DNS records.

All i've done is add the one TXT record as requested (not sure I should be changing anything else yet?)

Deleted member 77746 · 17 May 2021 at 17:09

SkidMarkKing said:
All i've done is add the one TXT record as requested (not sure I should be changing anything else yet?)

Glanza wanted to see the txt record in your host and also have you verified that the txt file exists when you use nslookup?

SkidMarkKing · 17 May 2021 at 17:21

Bouton Aide said:
Glanza wanted to see the txt record in your host and also have you verified that the txt file exists when you use nslookup?

I'm stuck at the verification part, lol. I've added the TXT record then it fails to verify.

Deleted member 77746 · 17 May 2021 at 17:37

nslookup -type=TXT MS=ms81110261.YOURdomain.com

SkidMarkKing · 17 May 2021 at 20:52

Bouton Aide said:
nslookup -type=TXT MS=ms81110261.YOURdomain.com

Just added my domain after the "MS=ms81110261".

It doesn't say on the "How to" to do that? :/

I might try and verify with an MX record instead?

Deleted member 77746 · 17 May 2021 at 21:32

SkidMarkKing said:
Just added my domain after the "MS=ms81110261".

It doesn't say on the "How to" to do that? :/

I might try and verify with an MX record instead?

I didn’t say add it to the domain what I mentioned was to verify it through command prompt (CMD)

SkidMarkKing · 17 May 2021 at 21:40

Bouton Aide said:
I didn’t say add it to the domain what I mentioned was to verify it through command prompt (CMD)

I've emailed 123-reg because all the guides say copy and paste the MS=ms81110216 to a "TXT record" in the advanced DNS settings on 123-reg and it will verify (extremely simple). Starting to think is there a problem with the domain somewhere. I purchased it 2 days ago now.

Deleted member 77746 · 17 May 2021 at 21:52

Ping the domain? Check the domains txt record using nslookup.

them are the basic network commands to check/verify.

SkidMarkKing · 17 May 2021 at 21:59

Bouton Aide said:
Ping the domain? Check the domains txt record using nslookup.

them are the basic network commands to check/verify.

Just used nslookup.io and for the domain it's say nothing for any of the records.

Pinging using CMD also saying no host.

Deleted member 77746 · 17 May 2021 at 22:15

SkidMarkKing said:
Just used nslookup.io and for the domain it's say nothing for any of the records.

Pinging using CMD also saying no host.

If you can't ping the main domain then there's a problem before you even start with office 365.

SkidMarkKing · 17 May 2021 at 22:16

Bouton Aide said:
If you can't ping the main domain then there's a problem before you even start with office 365.

Looks that way. I've created a ticket with 123-reg to see what they come up with.

Thanks, appreciate the help

Deleted member 77746 · 17 May 2021 at 22:18

SkidMarkKing said:
Looks that way. I've created a ticket with 123-reg to see what they come up with.

Thanks, appreciate the help

They will fix it so it's pingable, there might not be a name server (NS) set on the domain. You should have a control panel with 123 reg to verify that setup. Did you just buy the domain or with hosting as well?

Have a read of this before 123 reg contact you to fix the issue.

Change nameservers to set up Microsoft 365 with any domain registrar - Microsoft 365 admin | Microsoft Docs

SkidMarkKing · 17 May 2021 at 22:24

Bouton Aide said:
They will fix it so it's pingable, there might not be a name server (NS) set on the domain. You should have a control panel with 123 reg to verify that setup. Did you just buy the domain or with hosting as well?

Have a read of this before 123 reg contact you to fix the issue.

Change nameservers to set up Microsoft 365 with any domain registrar - Microsoft 365 admin | Microsoft Docs

I just purchased the domain through 123-reg then office 365 business from the microsoft website for the email hosting.

Deleted member 77746 · 20 May 2021 at 23:25

Did you get this setup ?

SkidMarkKing · 21 May 2021 at 07:17

Bouton Aide said:
Did you get this setup ?

123-reg said it was an SOA error. Took them 2 days but I had it setup in minutes once they sorted it. Wasn't me being a numpty after all

Deleted member 77746 · 21 May 2021 at 08:56

SkidMarkKing said:
123-reg said it was an SOA error. Took them 2 days but I had it setup in minutes once they sorted it. Wasn't me being a numpty after all

At least it's setup now.

I love 0365.

Glanza · 21 May 2021 at 16:24

SkidMarkKing said:
123-reg said it was an SOA error. Took them 2 days but I had it setup in minutes once they sorted it. Wasn't me being a numpty after all

Glad your sorted now, I would move the domain to 20i personally if you don't have any other services with them.