Configuring Office365 DNS settings via NFO control panel

[thecomputerdude]

I've got support working on this as well, but figured I would reach out to the hosting community here and see if anyone has successfully configured the DNS in the control panel for Office365? I'm attempting to move a site from another host and had the DNS managed by Network Solutions.

For the life of me I can't get the SRV records to work. Apparently NFO requires an A record, but A records aren't very useful with dealing with 200+ possible IPs for a service.

[soja]

viewtopic.php?f=45&t=12989&hilit=office+365

This might help you, what records do you need specifically set up? MX for mail, or something else?

[thecomputerdude]

I already got MX set up and working.

I'm trying to get the SIP TLS set up for their Lync/Office365 integration (I'm not sure exactly what this feature of Office is, never used it before)

It looked like this when NetworkSolutions managed it:

Code: Select all

_sip._tls.pierceandshows.com. 3600 100 1 443 sipdir.online.lync.com.
_sipfederationtls._tcp.pierceandshows.com. 3600 100 1 5061 sipfed.online.lync.com. 

My approach (and I think it's correct, but doesn't work due to a limitation on NFO's side) is to use this:

http://imageshack.com/a/img903/5240/kbxjx7.jpg

I think that NFO is specifying ONLY TCP or UDP for the _proto. I need to use TLS though.

[soja]

Try this for the SRV record:

_sip._tls in subdomain, sipdir.online.lync.com in target.

Sorry if you already tried this, im just trying to decypher what I am reading on microsofts support site.

[thecomputerdude]

yep, that's what I tried, NFO says:

The SRV subdomain for _sip._tls.pierceandshows.com is invalid; it should be in the form _service._proto.subdomain.

And it already is.

[soja]

Maybe _sip._tls. ?
(There is an extra dot at the end)

So Office expects(in your case) pierceandshadows.com to be set up with a SRV record for sipdir.online.lync.com right? Can office be configured to use like sip.pierceandshadows.com? If so try _sip._tls.sip.

[thecomputerdude]

adding the dot gets it double-dotted when NFO parses it (_sip._tls..pierceandshows.com) and it doesn't work.

The sticking point is using the _tls protocol. I've got a ticket for Edge100x to see if he can add _tls to the supported protocols.

It's pretty certain that NFO currently only allows _tcp or _udp protocols.