Wednesday, January 04, 2012 3:26 PM
We have a Windows domain at our HQ, lets say contoso.com. We use Lync, and people can connect because of the right entries in our DNS. The can resolve sip.contoso.com etc.
So far, so good. Now we have started a new small office at another location, we connect through VPN tunneling based on L2TP. Users and workstations at the small office can logon, we have a domain controller at the other site. DNS is also being replicated. Because of performance issues, we want Lync users at the small office to logon NOT throught te VPN tunnel, but outside through the internet. But the problem is that they also resolve the name sip.contoso.com and al the other records. Can we make something in DNS or otherwise, so that Lync Clients don't resolve the Lync DNS records from internal, some they automaticly connect as a external client.
Please, Advise. Thanks, Hans
Thursday, January 05, 2012 7:36 AMModerator
Thanks for posting here.
You may consider to set a new conditional forwarder entry on DNS server where located at remote new small office and forward this individual domain sip.contoso.com to internet publish DNS server or ISP DNS server.
Please DO NOT select to store this forwarder setting in active directory on that server:
Assign a Conditional Forwarder for a Domain Name
Are we using same internal and external domain name space ?
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.