DNS and Network Adapter Binding Order
by Tom Pacyk, Andrew Abbate, Alex Lewis
Microsoft® Lync Server 2010 Unleashed
- Title Page
- Copyright Page
- Dedication
- Contents at a Glance
- Table of Contents
- About the Authors
- Acknowledgments
- We Want to Hear from You!
- Reader Services
- Introduction
- Part I. Overview
- Chapter 1. What Is Microsoft Lync Server?
- Chapter 2. What Is New in Microsoft Lync Server?
- Introducing New Management Tools
- Topology Changes
- New Enterprise Voice Features
- New Call Management Features
- Integrated Mediation Server
- New Presence Features
- New Conferencing Features
- DNS Load Balancing
- Survivable Branch Appliances
- Operating System Support
- New Lync Client Features
- Client Appearance
- The “Me” Area
- Enhanced Contacts
- Privacy Relationships
- Integration with Office and Windows 7
- Whiteboarding and Application Sharing
- Improved Meeting Join Experience
- Conferencing Attendant and Scheduling
- PSTN Dial-In Conferencing Improvements
- Video Improvements
- Manager/Admin Improvements
- Improved Phone Experience
- Summary
- Chapter 3. Feature Overview of Microsoft Lync Server
- Chapter 4. Benefits of Microsoft Lync Server 2010
- Part II. Microsoft Lync Server 2010 Server Roles
- Chapter 5. Microsoft Lync Server 2010 Front End
- Chapter 6. Microsoft Lync Server 2010 Edge
- Chapter 7. Microsoft Lync Server 2010 Monitoring
- Overview
- Installation
- Configuration
- Administration
- Troubleshooting
- Best Practices
- Summary
- Chapter 9. Director
- Part III. External Dependencies
- Chapter 10. Dependent Services
- Chapter 11. SQL
- Chapter 12. Firewall and Security Requirements
- Part IV. Administration and Management
- Chapter 13. Monitoring Microsoft Lync Server 2010
- Overview
- OpsMgr Lync Server 2010 Monitoring
- What Is New in OpsMgr R2?
- How OpsMgr Works
- OpsMgr Architecture
- How to Use OpsMgr
- OpsMgr Component Requirements
- Advanced OpsMgr Concepts
- Understanding OpsMgr Deployment Scenarios
- Multiple Configuration Groups
- Deploying Geographic-Based Configuration Groups
- Deploying Political or Security-Based Configuration Groups
- Sizing the OpsMgr Database
- Defining Capacity Limits
- Defining System Redundancy
- Monitoring Nondomain Member Considerations
- Securing OpsMgr
- Installing Operations Manager 2007 R2
- Installing Edge Component Monitoring Certificates
- Installing the Lync Server 2010 Management Pack
- Best Practices
- Summary
- Chapter 14. Backup and Restore of Microsoft Lync Server 2010
- Chapter 15. Administration of Microsoft Lync Server 2010
- Chapter 13. Monitoring Microsoft Lync Server 2010
- Part V. Migrating from Older Versions
- Part VI. Voice
- Chapter 17. PBX Integration
- Chapter 18. Enterprise Voice
- Chapter 19. Audio Conferencing
- Part VII. Integration with Other Applications
- Chapter 20. Exchange 2010 and SharePoint 2010 Integration
- Overview
- Exchange 2010 Unified Messaging
- Call Answering Rules
- Exchange 2010 Unified Messaging Architecture
- Unified Messaging Users
- UM Web Services
- Supported IP/VoIP Hardware
- Unified Messaging Protocols
- Unified Messaging Installation
- Postinstall Configuration
- Data Storage in Unified Messaging
- Exchange 2010 Outlook Web Application
- SharePoint 2010 Integration
- Best Practices
- Chapter 21. UCMA
- Chapter 20. Exchange 2010 and SharePoint 2010 Integration
- Part VIII. Clients
- Chapter 22. Microsoft Communicator Client for Macintosh
- Chapter 23. Windows, Browser, and Silverlight Clients
- Chapter 24. UC Endpoints
- Part IX. Planning for Deployment
- Chapter 25. Virtualization
- Chapter 26. Planning for Internal Non-Voice Deployment
- Chapter 27. Planning for Deploying External Services
- Chapter 28. Planning for Voice Deployment
- Index
DNS and Network Adapter Binding Order
,Being able to resolve DNS queries correctly is absolutely critical to making an Edge Server functional. At a minimum, an Edge Server must be able to resolve the names of internal pools and servers, so be sure to enter an internal DNS server IP address on the internal adapter’s network configuration.
It’s also important that an Edge Server resolve external DNS queries for federation or public IM scenarios. These queries can be answered by internal DNS servers, or an Edge Server can use a public DNS server to resolve queries if entered on the network adapter configuration. In a single Edge Server deployment where the A/V Edge is behind NAT, the service must be able to resolve its own publicly addressable name and IP address.
The binding order of the network adapters is not critical to an Edge Server operation, but can have an effect on how an Edge Server resolves DNS queries. Servers use the DNS servers entered on an adapter starting with the adapter listed first in the binding order.
The impact is if a split-DNS namespace is in place where internal and external queries can return the same name with different IP addresses, the Edge Server might resolve names incorrectly. For example, if the external adapter is listed first in the binding order, the Edge Server might be unable to resolve the name of an internal pool correctly because that name is not registered in the public DNS.
Tip
To avoid this issue, enter the IP addresses of the internal DNS servers on the internal adapter, and then place the internal adapter highest in the binding order. If internal DNS lookups are not allowed, a host file can be used.
If this configuration still does not make DNS lookups succeed and resolve correctly, it might be necessary to use a host file for resolving internal names. Usually only a few internal pool and server names need to be entered, so it is fairly quick to configure, but be aware, this option exists when troubleshooting name resolution issues.
-
No Comment