Creating a Public DNS Entry

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

After setting up Windows SharePoint Services on your server farm, you must create a public DNS entry to map your public FQDN to the IP address for the public interface of your reverse proxy server.

For example, you could map www.Contoso.com to 10.11.111.11. When a client attempts to connect to www.Contoso.com, it will ask the public DNS server what IP address corresponds to www.Contoso.com. The public DNS server would then point it to 10.11.111.11, which should be the public IP address for your reverse proxy server. The client will then attempt to establish a connection to 10.11.111.11.

If you are using Windows SharePoint Services in a
multiple host names deployment
(scalable hosting mode), you must be sure that a DNS mapping is created for each host name site you set up. To do so, create a unique public DNS entry for each host name site. For example:

Host1.Contoso.com
10.11.111.11

Host2.Contoso.com
10.11.111.11

Alternatively, you can create a wildcard public DNS entry so that all host names within your domain map to your proxy servers public interface IP address. For example:

*.Contoso.com 10.11.111.11

For more information about creating a DNS entry or a wildcard DNS entry, see your DNS server documentation.