Office 365 / Hosting Direct DNS issues

Forums › IT Pro and developers › Office 365 / Hosting Direct DNS issues

SATTV

1670 posts

Uber Geek
+1 received by user: 657

ID Verified

#150589 27-Jul-2014 21:13

Hi All,
I am helping someone set up there Office 365 hosted exchange.

Their domain is with Hosting Direct.

I have managed to to set emails going to and fro.

Emails can take some time, I think there are DNS issues that Hosting direct is not refreshing as often as they should be.

Auto discover is working some times then just stops.

Over time it should resolve itself.

What I am have issues with is the the following record.

TXT @ v=spf1 include:spf.protection.outlook.com -all

when I check it with mxtoolbox it shows

TXT @ v=spf1include:spf.protection.outlook.com -all

I have tried putting a full stop at the end ( I had to do this for the MX record & autodiscover record ) but it keeps coming up short.

Anyone got any ideas?

I have spent way to long on this, it normally takes me 30 mins to set up a basic 365 but this has taken several hours

I also have changed the TTL down to 5 minutes.

Any help appreciated. Particularly is you have set up 365 with hosing direct before.

Cheers
John

I know enough to be dangerous

mattwnz

20515 posts

Uber Geek
+1 received by user: 4795

#1096781 27-Jul-2014 21:17

Why don't you contact the host as they will know their systems the best, and the owner of the account will get support as part of the service?

SATTV

1670 posts

Uber Geek
+1 received by user: 657

ID Verified

#1096791 27-Jul-2014 21:38

Being that today is sunday they are not answering their phone.

I have a busy day tomorrow, I wanted to resolve it today if I could.

Failing that, I will get the UDAI and move them over to 1st domains when time allows.

I know enough to be dangerous

insane

3324 posts

Uber Geek
+1 received by user: 1006

ID Verified

Trusted

2degrees

Subscriber

#1096813 27-Jul-2014 23:35

What was the TTL BEFORE you started making changes? Some people (perhaps not you) don't realise they have to wait for the old TTL to expire before other DNS servers will reflect the changes to the zone file.

SATTV

1670 posts

Uber Geek
+1 received by user: 657

ID Verified

#1096854 28-Jul-2014 07:53

TTL was 4 hours, I changed it to 5 mins.
It wasn't just the TTL that was causing the issue, it was the DNS entries themselves.
I finally sorted it at 10.20 last night, I had to put the record in quotes " " to get it correct.
Cheers
John

I know enough to be dangerous