That gawd awful office365 portal gave me heartburn too.
I really hate the way they have taken something that should be really
simple and hosed up up beyond belief.
bp
<part15sbs{at}gmail{dot}com>
On 3/3/2015 7:37 PM, That One Guy wrote:
I figured it out, its the stupid office365 portal.
everytime i would run a check it had different errors and solutions,
like suggesting i remove the NS records because it thought they were
MX records (no clue on why)
at one point it saw one SRV record, but not the other, which was odd
because the both had the exact same syntax
It at one point had two CNAMEs that dont even exist and never have for
autodiscover responses
its almost like the issue is some caching on their side thats very
screwed up
I finally just ran the check over and over until it said everything
was good and left it alone. really irritates me cause I tried playing
hooky from work today and ended up spending six hours I could have
been playing minecraft with the kids trying to figure this out, at one
point even contemplating just rebuilding the DNS servers
On Tue, Mar 3, 2015 at 9:22 PM, Steve Utick <[email protected]
<mailto:[email protected]>> wrote:
Not sure on the GUI, as I've never used it. We do have this set up
for a couple of customers though, and the following is what's in
the zone file for them:
_sip._tls IN SRV 100 1 443
sipdir.online.lync.com <http://sipdir.online.lync.com>.
_sipfederationtls._tcp IN SRV 100 1 5061
sipfed.online.lync.com <http://sipfed.online.lync.com>.
On Tue, Mar 3, 2015 at 3:40 PM, That One Guy
<[email protected] <mailto:[email protected]>> wrote:
we are trying to get these srv record working for office 365
Adding through the web interface doesnt seem to get the format
correct
Editing the record file doesnt seem to do it either
is there something Im missing, like is there somewhere I need
to enable srv records, we have never put one in before.
The current iteration is as follows:
_sip._tls.domainname.com <http://tls.domainname.com>. 3600 IN
SRV 1 100 443 sipdir.online.lync.com
<http://sipdir.online.lync.com>.
_sipfederationtls._tcp.domainname.com
<http://tcp.domainname.com>. 3600 IN SRV 1 100 5061
sipfed.online.lync.com <http://sipfed.online.lync.com>.
This is what the host says needs to be present
Inline image 1
--
If you only see yourself as part of the team but you don't see
your team as part of yourself you have already failed as part
of the team.
--
If you only see yourself as part of the team but you don't see your
team as part of yourself you have already failed as part of the team.
