Hi There,

If I want the Lync server environment to work Internal as well from External in all the aspects. (auto-discover, meetings, AV conferencing,web conferencing, voice integration, mobility etc), please answer to the below questions and also their purpose please. I'm not sure whether the answer varies for 2010 and 2013 version.

1. What are the Internal and External(public) DNS records to be created for the reverse proxy(assume i'm using TMG servers), and their purpose?

2. What are the Internal and External(public) DNS records to be created for Lync Edge server, and their purpose?

• Edited by Magudeeswaran M 16 hours 56 minutes ago

Hi,

Following DNS entries are required

For single Lync Edge server

External:

• Sip.domain.com
• Webcon.domain.com
• avcon.domain.com

Internal:

• edge.domain.com (FQDN of Edge server)

For Reverse Proxy

Internal

• FQDN of Server

External

• meet.domain.com
• Dialin.domain.com
• webapp.domain.com
• LyncWeb.domain.com
• LyncDiscover.domain.com

I'll try to answer as well.

1) For the reverse proxy, you'll need to publish the following:

External:

• lyncdiscover.sipdomain.com (You'll need this record for every sip domain you have).  This is for client autodiscover.
• external web services FQDN (You'll need one of these per pool, you get to choose the name).  This is for address book downloads, web conferencing, etc.
• Meet.sipdomain.com (You can choose the name here, and have one per sip domain or one for the whole org).  This is for web conferencing.
• Dialin.sipdomain.com (You'll just need one here, it doesn't have to be dialin).  This is for changing your conferencing/phone pin, resetting conference info, and general conferencing info.
• For Lync 2013 only, you may want the Office Web Application server pool name as well for PowerPoint sharing.  Lync 2010 doesn't use this.  

Internal:

• The external web services FQDN.  You'll need this available internally through the reverse proxy so you can redirect requests on port 443 to port 4443.  This will be used for mobile devices on WiFi.

2) For the Edge server:

Externally:

• sip.sipdomain.com (you'll need one per sip domain) this is an autodiscover/multi use FQDN and should point to your access edge IP.
• webedge.sipdomain.com (edge web conferencing, you can pick any name you like).
• avedge.sipdomain.com (av edge, you can pick any name you like).
• accessedge.sipdomain.com (you'll need a name for the access edge role, however you can just use sip.sipdomain.com and save a name in your certificate request).

Internally:

• edgepool.sipdomain.com (you can pick any name you want, it's just the name assigned to the internal edge interface.

If you choose to have a single ip for the external edge, you can get away with just an access edge name and/or sip.sipdomain.com