Hi there,
The hosting company I use are using DirectAdmin as their control panel environment. I'm setting up Office365 which requires me to configure a few DNS records for things like autodiscover and stuff. This involves creating two SRV records, one of which with the following specs:
Service: _sip
Protocol: _tls
Port: 443
Weight: 1
Priority: 100
TTL: 3600
Name: @
Target: sipdir.online.lync.com
Now I've read the documentation (https://help.directadmin.com/item.php?id=488) on how to setup SRV records in direct admin, which says:
right hand side: <service>.<protocol>.<name>
left hand side: <priority>.<weight>.<port>.<target>
So I translated to:
right hand: _sip._tls.
left hand: 100 1 443 sipdir.online.lync.com
But when I save this record, Office365 reports that stuff is messed up. It says the record reads:
Port = 1 (=weight)
Weight = 100 (=priority)
Priority = 0 (?)
Target = 443 (=port)
So things seem to be in the wrong order. I tried swapping around stuff and came to:
1 443 100 sipdir.online.lync.com.
365 now returns:
Port = 443 (ok)
Weight = 1 (ok)
Priority = 0 (?)
Target = 100 (priority)
I tried all sorts of sequences to correct this, but have been unable to get it working properly. Some combinations are not allowed by DirectAdmin, the ones that are do not translate correctly to Office365. One might argue that this problem could be on the Office365 side, but I've done multiple installations using different DNS management tools which didn't have this problem.
Does anyone know what the problem might be? Does my host need to update their DirectAdmin for instance?
The hosting company I use are using DirectAdmin as their control panel environment. I'm setting up Office365 which requires me to configure a few DNS records for things like autodiscover and stuff. This involves creating two SRV records, one of which with the following specs:
Service: _sip
Protocol: _tls
Port: 443
Weight: 1
Priority: 100
TTL: 3600
Name: @
Target: sipdir.online.lync.com
Now I've read the documentation (https://help.directadmin.com/item.php?id=488) on how to setup SRV records in direct admin, which says:
right hand side: <service>.<protocol>.<name>
left hand side: <priority>.<weight>.<port>.<target>
So I translated to:
right hand: _sip._tls.
left hand: 100 1 443 sipdir.online.lync.com
But when I save this record, Office365 reports that stuff is messed up. It says the record reads:
Port = 1 (=weight)
Weight = 100 (=priority)
Priority = 0 (?)
Target = 443 (=port)
So things seem to be in the wrong order. I tried swapping around stuff and came to:
1 443 100 sipdir.online.lync.com.
365 now returns:
Port = 443 (ok)
Weight = 1 (ok)
Priority = 0 (?)
Target = 100 (priority)
I tried all sorts of sequences to correct this, but have been unable to get it working properly. Some combinations are not allowed by DirectAdmin, the ones that are do not translate correctly to Office365. One might argue that this problem could be on the Office365 side, but I've done multiple installations using different DNS management tools which didn't have this problem.
Does anyone know what the problem might be? Does my host need to update their DirectAdmin for instance?
