Skype for Business & External Hosted DNS/Domain

Skype for Business & External hosted DNS/Domain

To use federation with others using Skype4Business/Lync server, Office 365 or Skype consumers and be accessible using your own domain name, some DNS settings and- /or Name- servers changes have to made for domains that are not hosted by Voxogo.

This document is not applicable when using the generic name @enterlync.net address as sign- in address.

Services & SLA

Unified communication systems like SfB, are fully depended on DNS for operating smoothly. If for any reason availability and-/or configuration of DNS server is not available, communications to and from SfB will fail. These problems are not covered by the Voxogo SLA.

Support for DNS service records

Please check and make sure that your current DNS service-provider supports service records (SRV). Without these records not all SfB functionality is available and clients (Softphones of devices) need to be configured manually.

Sign-in name

Your domain name needs to be added to the Shared SSL certificate of the Hosted SfB deployment at Voxogo. To setup the certificate Voxogo’s certificate authority partners needs to verify that your control the domain-name. Please follow this procedure:

Method of Domain Control Validation (DCV): DNS CNAME-based with hash values

You will receive a request to validate your domain name in order to get it listed on the Hosted Skype for Business / cloudPBX services.

Two hash values (MD5 and SHA-1) are provided to you below for Hosted Skype for Business and must be entered as a DNS CNAME record for your domain.

The hashes are to be entered as follows:.sip.yourdomain.com. CNAME

CSR>.comodoca.com.Note: Please take notice the trailing period/fullstop at the tail end of each of the TLDs as this is required to make the entry fully-qualified.

Note2: yourdomain.com in the example above (and below in the HTTP(S) method instructions) means the Fully Qualified Domain Name (FQDN) contained in the certificate Let’t say your (sub) domain name is: sip.mydomain.com

The MD5 value for Hosted Skype for Business is: 95911A381D9409CDCB5213F52E33B4B6with the SHA-1 hash value of: E07219F3CFEC8D8CF1B9ED64657614347490F5C6

This is an example. You have to create the CNAME record as given to you by Voxogo.

To Validate settings

Goto http://www.kloth.net/services/dig.php

If the values of the previous examples are used, then enter in the domain field:

95911A381D09CDCB5213F52E33B4B6. sip.mydomain.com

Choose CNAME as Query type and click the Look it up button.

The results in the answer section should look like:

; <<>> DiG 9 <<>> @localhost 95911A381D9409CDCB5213F52E33B4B6.sip.mydomain.com.net CNAME ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 269 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;95911A381D9409CDCB5213F52E33B4B6.sip.mydomain.com. IN CNAME ;; ANSWER SECTION: 95911A381D9409CDCB5213F52E33B4B6.sip.mydomain.com. 3600 IN CNAME e07219f3cfec8d8cf1b9ed64657614347490f5c6.comodoca.com. ;; Query time: 53 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Mon Apr 6 16:32:27 2015 ;; MSG SIZE rcvd: 137 Any colors used in this example are purely for clarification.

Skype for business 2015 Autodiscover and Federation DNS records:

Please create the following Auto discover, SRV and Federation records: Type Domain IP

A sip.domain.com 109.205.192.222

A sip.domain.com 109.205.196.123

A lyncdiscover.domain.com 109.205.192.28

Service records (SRV):

Service Protoco Priority Weigh Port Number Host offering service l t

_sipfederationtl _tcp 100 1 5061 sip.domain.com s

_sip _tls 100 1 443 sip.domain.com

#replace domain.com with your own domain name

 Look for more details about DNS en SRV records: http://en.wikipedia.org/wiki/SRV_record Note: For meetings and dial-in conference URL’s the generic domain "enterlync.net" will be used.

Support Our support Engineers can assist in setup your External DNS configuration for the consultancy fee as stated in your quote.

Document version: 7/12/2016