Lync 2013 Edge Server - DNS Resolution, cannot resolve IP addresses

-
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 into the DNS Client Cache.


Let's tap into several possible setups:

Also: NetBIOS and LMHOSTS should be disabled.

1. Only a internal DNS Server is used.
You need to configure a DNS Server on the internal network card
Firewall: PORT 53 TCP/UDP configured for internal DNS Server and Edge Server internal IP


2a. A HOSTS file and a external DNS server is used.
The HOSTS is used for internal Lync Server only, so specify all Lync Server in your internal Topology, configure the DNS Server only on the external NIC
Firewall: PORT 53 TCP/UDP configured for external DNS Server and Edge Server external IP (primary IP, the Access Edge)


2b. A HOSTS file and a internal DMZ DNS server is used.
The HOSTS is used for internal Lync Server only, so specify all Lync Server in your internal Topology, configure the DNS Server on the internal NIC, which has a route into the DMZ net.
Firewall: PORT 53 TCP/UDP configured for external DNS Server and Edge Server external IP (primary IP, the Access Edge)


3. Split DNS resolution, two DNS server are used
Configure the DNS Server for external resolution on the external NIC and the internal DNS server on the internal NIC.
Firewall: PORT 53 TCP/UDP configured for external and internal DNS Server and Edge Server external (primary IP, the Access Edge) and internal IP

Also the routing is very important.
However, make sure the routes have als o assigned the correct interface.
Recommendation:
alway use the ROUTE ADD -P command to manually set the routes.This ensure the correct METRIC as well as the corrcet INTERFACE.

Assume this IP addresses:
NIC: Interface 11
ACCESS Edge: 192.168.10.10
WEBCONF Edge: 192.168.10.20
AV Edge: 192.168.10.30

NIC: Interface 12
INTERNAL  Edge: 192.168.20.10

LAN Segement: 10.0.0.0

Default Route:
ROUTE ADD -P 0.0.0.0 MASK 0.0.0.0 192.168.10.254 METRIC 10 IF 11
ROUTE ADD -P 10.0.0.0 MASK 255.0.0.0 192.168.20.254 METRIC 50 IF 12

If now your DMZ DNS Server is used, make sure which path (interface and route) can be used to reach the DNS server. You might have to admit the route.

Comments

Post a Comment

Popular posts from this blog

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modify the AD hide at
Read more

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, unique FQDN fo
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more