sipexternal.(sip-domain), A record for the external Access Edge services (Externally only) sip.(sip-domain), Internal A record of the Frontend / Director pool (Internally), or Access Edge Service (Externally)Ħ. sipinternal.(sip-domain), internal A record of the Frontend / Director poolĥ. _sip._tls.(sip-domain) using TLS (Externally only)Ĥ. _sipinternal.tcp.(sip-domain) using TCPģ. _sipinternaltls.tcp_(sip-domain) using TLSĢ. lyncdiscover.(sip-domain) If Mobile client failed to resolve this record it will fail to login and stop trying!ĭesktop client will try to failback to DNS SRV Records: DNS SRV discovery process (desktop client only!)ġ. lyncdiscoverinternal.(sip-domain), this is an internal record so the client needs to be in internal network to be able to resolve this record, if the client couldn’t resolve the record it knows it is outside the corporate network and goes to step twoĢ. Autodiscover processīoth desktop and mobile clients will attempt to resolve DNS records in the following order:ġ. Since Lync 2013 clients favor Autodiscover services over DNS SRV records to locate the Front End server. Skype for Business Desktop Client Sign-In Process The last three records are common for the whole Skype for Business infrastructure. Skype for Business External Webservices FQDN for Pool02Īs you can see in case of multiple pools with multiple servers we need DNS A Record for each server in each pool. Skype for Business External Webservices FQDN for Pool01 IP address of Edge02 Web Conf Edge in Pool02 IP address of Edge01 Web Conf Edge in Pool02 IP address of Edge02 Web Conf Edge in Pool01 IP address of Edge01 Web Conf Edge in Pool01 IP address of Edge02 Access Edge in Pool02 IP address of Edge01 Access Edge in Pool02 IP address of Edge02 Access Edge in Pool01 IP address of Edge01 Access Edge in Pool01 Each pool has it’s own Reverse Proxy: Description In the example below there are two Edge pools with two Edge servers in each. Copypasted articles for the simplest scenario are everywhere… Finally I managed to figure out the stuff. It’s not easy to find Skype for Business DNS Requirements for multiple Edge pools. Skype for Business DNS Records requirements Skype for Business Internal DNS Records Description If you are not using “split-brain” DNS you can create a zone for each required DNS records pointing it to the internal IP-address. Thus Skype for Business clients will get information only from their zone, so if external client is trying to connect to Skype for Business server, it will resolve the entries to the external IP-addresses, if it’s from internal network then it will resolve the DNS entries to internal IP-addresses using the internal DNS server. The DNS is often deployed as “split-brain” DNS deployment: the same zone name is deployed internally and externally but with different (internal or external) IP-addresses for the same entries. Skype for Business uses two types of DNS records: A record and SRV record.
Skype for Business DNS Records are one of critical components of the whole infrastructure.
0 kommentar(er)
