Installation guide

DNS Records Needed for the Acano Solution
Acano solution: Deployment Guide R1.2 76-1006-06-K
Page 60
Appendix A DNS Records Needed for the Acano
Solution
Note: Verify that no A or SRV records already exist before defining the records below.
If duplicates are created, they will “round robin” on lookups and will cause issues for existing
services as well as these new services. If there are conflicts, a new DNS Zone can be defined to
create isolation between the services. For example, if you already have an XMPP server in the
example.com zone using the same SRV records, define a new DNS zone for
acano.example.com and create the new SRV records for it. The client login will now need to use
[e-mail] for proper resolving but will not conflict with existing XMPP
deployment.
This same method holds true for the _sip._tls records: if one exists for the SIP Call Control
device already, adding the same for Lync using the same domain will cause a round robin
lookup. They must be isolated, therefore create a new DNS zone such as vcs.example.com,
define the SIP Call Control device within it and have it point to the original A record already
defined in the root DNS zone. You should then add this new domain into your SIP Call Control
device configuration as a valid SIP Domain and create a transform rule to convert @<SIP Call
Control device>.example.com to @example.com. This allows you to add this new zone without
modifying any of your current devices or registrations.
DNS A Records
 A record for server FQDN for SIP and Lync calls, e.g. acano.example.com, resolving to the
address used for SIP and Lync calls (probably interface A address) This is the A record for
Call Bridge resolving to the IP address of the interface you configure the Call Bridge to listen
on
 A record for server FQDN for Web Bridge access (can be the one above), e.g.
join.acano.example.com, resolving to the port address used for WebRTC
 A record for server FQDN for XMPP access (can be the above), e.g.
xmpp.acano.example.com, resolving to the port address used for XMPP
 A record for your SIP Call Control device, e.g. VCS, if used. (This may be in place already,
but add it if not)
 A record for Lync Front End Server if used (probably in place already, but be sure to verify
this)
DNS SRV Records
 SRV record for _xmpp-server._tcp.example.com set to port 5269 and resolving to host A
record above that was defined for the XMPP portion of the server
 SRV record for _xmpp-client._tcp.example.com set to port 5222 and resolving to host A
record above that was defined for the XMPP portion of the server