Cisco Cisco Meeting Server 2000
Cisco Meeting Server Release 2.0 : Single Split Meeting Server Deployments
97
Type
Example
Resolves to
Description
A /
AAAA
AAAA
ukcoreadmin.example.com
ukedgeadmin.example.com
IP address of the
MMP Interface
MMP Interface
This record is used purely for admin purposes;
when system administrators prefer a FQDN to
remember for each MMP interface.
when system administrators prefer a FQDN to
remember for each MMP interface.
SRV
(*)
(*)
_sipinternaltls._
tcp.lync-domain.com
tcp.lync-domain.com
The A record of the
Lync FE server or
FE Pool
Lync FE server or
FE Pool
If you have an FE pool, you can have multiple FE
records pointing to individual FE servers within
the pool. You also need this record if you want
Meeting Server to resolve Lync meetings by Lync
meeting IDs.
records pointing to individual FE servers within
the pool. You also need this record if you want
Meeting Server to resolve Lync meetings by Lync
meeting IDs.
A /
AAAA
AAAA
fe.lync-domain.com
IP address of the
Lync FE server
Lync FE server
You will need one record for each individual FE
server
server
SRV
(*)
(*)
_sipfederationtls._
tcp.domain.com
tcp.domain.com
The FQDN of the
Call Bridge.
Call Bridge.
This record is required for Lync federation.
A
call-bridge.example.com
IP address of the
Call Bridge.
Call Bridge.
Required for Lync federation as the Call Bridge
will need to have a public IP address, and NAT is
not supported in this scenario.
will need to have a public IP address, and NAT is
not supported in this scenario.
(*) SRV records do not resolve directly to IP addresses. You need to create associated A or
AAAA name records in order to satisfy the SRV requirements.
AAAA name records in order to satisfy the SRV requirements.
Appendix A DNS records needed for the deployment