Once an instance of SharePoint Server 2013 has been installed, configured and activated, it needs to be added as a host to a Windows network. In a short video tutorial, MCreating a SharePoint 2013 testing environment – Part 6 – Configuring DNS for hosting SharePoint sites and Apps, Asif Rehmani demonstrates the steps to take to successfully connect the server to a Windows network supporting TCP/IP protocol.
Adding the server as a host on the network amounts to setting up Domain Name Services (DNS). Setting up DNS requires that IP address be mapped to a Domain Name, for example, “microsoft.com”, or, in a test environment, any text name assigned to the server. It is important to note that a server farm has been configured for the SharePoint Server 2013 in our test environment. Any number of sites may need to be reached by text names, therefore regardless of the method chosen to map a DNS to a device at a specific IP address must address the likelihood that unique variants on the same base text name for the server will be used as features are added in the test environment.
We demonstrate how to use the graphical DNS Manager feature of Windows Server 2008 R2 to correctly add the server as a host on the TCP/IP test network. Once DNS Manager has been selected, the “Forward Lookup Zone” from the Navigational Panel should be used to locate the server. A “New Host Record” needs to be created for the server. We use the “*” wildcard character in the name field of the form to represent any text name that may used along with the Fully Qualified Domain Name (FQDM) for any sites on the server, apps, or even related servers. The “IP Address” field should be populated with the IP address for the server on the test network. The IPCONFIG program should be run from the terminal to find the address if it is not readily available. The “Create Associated Pointer Record” (PTR) should not be enabled. Neither should the “Allow any authenticated user to update DNS records with the same owner name” be enabled.
Once the host has been successfully added, an administrator can test any variants on the FQDN with NSLOOKUP via Powershell to validate that DNS is working correctly.
© Rehmani Consulting, Inc. & Ira Michael Blonder, 2013 All Rights Reserved