Thomas.Poett@TEAMS (MVP Teams and Cross-Tenant M&A/D Migration Expert Lead)

DNS Configuration for Skype for Business Hybrid Deployments DNS settings are important and you need to understand how your organizations Skype for Business communication flow works. First important understanding: If you run a hybrid installation, your Office 365 Tenant with Skype for Business Online is seen from your On-Premise installation as a federated organization. Therefore the following DNS records must also be resolvable from your internal DNS infrastructure (Edge Server). Depending on how DNS is configured in your organization, you may need to add these records to the internal hosted DNS zone for the corresponding SIP domain(s) to provide internal DNS resolution to these records. (see illustration below table) DNS RECORD RECORD TYPE WHERE IT SHOULD RESOLVE TO PORT sip.YourDom.com A Public IP of Access Edge n/a _sip._tls.YourDom.com SRV External on-premises Access Edge Interface (sip. YourDom .c...

A new topic came along my way, even I personally work with windows server since NT 3.5, but in very tight configured network environments you might run into server DNS resolution issues. Principals regarding Lync Edge Server DNS resolution. It is recommended to resolve DNS queries on the Internet, which means via the external NIC. For internal DNS resolution, best practice is a dedicated hosts file, or make it possible to resolve intern DNS. Therefore a common practice is to simply let even external DNS names resolve by the internal DNS servers. NOTE: Make sure you have the put in the DNS Servers on the correct network interface! What and how Windows Server really works: A we know, each IP setting for every NIC allow us to specify a DNS Server entry. As I figured out and very important to know, DNS resolution will work ONLY on the network adapter, where DNS servers are configured. While we still keep in mind, if a hosts file is used, the hosts entries are loaded int...

Hi all, (This is an updated version 2.2: 09 .07.201 5 ) This blog entry is valid for Lync 2010, Lync 2013 and Skype for Business Server. Generally, I'll write a new blog article, since the conversion history over multiple device and other service have change with Skype for Business 2015 Server. Once this written, I post the link here. there is always confusion in how Lync is crawling Exchange Web Services (EWS). Generally it is necessary to understand how DNS must be implemented: Just remember, identify if you have DNS Split configuration, different internal and external DNS names and what are your SMTP and SIP Domains. Very often you find in Lync/ Exchange deployments an issue, where the Lync configuration show up with empty: EWS Internal URL EWS External URL and EWS Information = EWS not deployed Therefor Exchange Web Service are not connected deployed and several Lync Integration Features are not working, e.g. Presence Information based on your Outlook Calendar....