If you only have 1 IP this is a good option вЂ“ however this will force you to use ports other than 443 which arenвЂ™t always open outbound from corporate networks and may cause usability issues on networks you cannot control.

вЂњUse a Single FQDN & IP AddressвЂќ вЂ“ this option will not be selected because we have plenty of public IPs to use.

Next we have a screen offering 3 options: Then we need to expand our topology, right click вЂњEdge PoolsвЂќ and choose вЂњNew Edge PoolвЂќД¬lick вЂњNextвЂќ on the вЂњDefine Edge PoolвЂќ pageД®nter the FQDN you will be using for your edge and select вЂњSingle Computer PoolвЂќ To start we need to add an edge to our topology, on the front end server (lyncfe) open вЂњLync Server Topology BuilderвЂќ. IвЂ™ve also matched the last octet of the address to make it easier to manage at a glance. Instead of placing the public IPs directly on the edge servers public NIC, I will NAT the public IPs to the private IPs with my lab ASA. In this example I will be using 1 internal IP, 3 DMZ IPs and 3 Public IPs.

Now that our DNS zone is in order we can plan for our edge server.

You also must have a SAN entry on the front end certificate to match this entry*** ***Note вЂ“ you can utilize another name here such as the Front End servers name, however the domain must match the sip domain. The new record will be for вЂњ_sipinternaltls._вЂќ and will point to on port 5061. We also need to create an SRV record for client automatic sign-in. To accomplish this IвЂ™ve created the following records in DNS: Record Type To start with I have to create a copy of my public zone on my internal DNS server so internal clients can reach the Lync server directly. To make this work you have to have an internal copy of the public zone and an external copy this is commonly referred to as вЂњsplit brain DNSвЂќ. I prefer to do these labs with different name spaces for AD and the public domain because that is the most common scenario IвЂ™ve run into in the real world. The active directory domain name for this lab is LyncGuy.local, with the public sip domain. The lab has the following servers and IPs: Server Name All articles moving forward will be built on the RTM bits of Lync, but to build the Front End server for this environment I followed the original article here, the only difference is the name of the server and the domain. For this article and the next I am going to add an Edge server and an XMPP gateway to an existing Lync environment.

Cannot get lync web app to open