Addalternatedomain: Stsadm operation (Office SharePoint Server)

Applies To: Office SharePoint Server 2007

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.


Topic Last Modified: 2015-03-09

Operation name: Addalternatedomain


Adds an internal URL and maps it to one of the five URL zones of a Web application or external resource.

This operation is equivalent to the Add Internal URLs user interface setting that is located on the Alternate Access Mappings page of the SharePoint Central Administration Web site.

For more information, see Configure alternate access mapping.


stsadm -o addalternatedomain

**   -url <URL name>**

**   -incomingurl <http://internal.url>**

**   -urlzone {Default | Internet | Intranet | Extranet | Custom}**

**   -resourcename <non-Web application resource name>**


Parameter name





A valid URL, such as http://server_name or http://server_name:1234

No. However, if the url parameter is used then the resourcename parameter cannot be used.

URL of the Web application. This parameter should be an existing alternate access mappings (AAM) URL that is assigned to a Web application so that stsadm can determine which Web application you are targeting. The URL can be a public URL or an internal URL from any zone associated with the targeted Web application.


A valid URL, such as ""


The internal URL that you want to add.

This parameter should be limited to the protocol scheme, host name, and port number portions of the URL. It should not contain any other portions of an URL. You can map multiple internal URLs to the same URL zone.


Any one of the following values:

  • Default

  • Intranet

  • Internet

  • Extranet

  • Custom


One of the five zones with which the internal URL is associated.


A valid name, such as "Resource1"

No. However, a resource name must already exist before this parameter can be used. You can create a new resource name using the Addzoneurl operation.


If the resourcename parameter is used, then the url parameter cannot be used.


Specifies the external resource which the internal URL should be added to.

This parameter is equivalent to the External Resource Mapping user interface setting that is located on the Create External Resource Mapping page of the SharePoint Central Administration Web site.


A separate zone mapping for each Web application can be performed.

In Windows SharePoint Services 2.0, an internal URL was referred to as an incoming URL and a public URL was referred to as an outgoing URL.

For each Web request, Windows SharePoint Services 3.0 determines the protocol, host header, and port of the request and looks for a matching internal URL that was previously entered. If a matching internal URL is found, Windows SharePoint Services 3.0 then determines which zone will be used to format the hyperlinks in the response. A URL zone contains one public URL and one or more internal URLs.

Alternate access mappings enable a Web application that receives a request for an internal URL, in one of the five authentication zones, to return pages that contain links to the public URL for the zone. You can associate a Web application with a collection of mappings between internal and public URLs. Internal refers to the URL of a Web request as it is received by Microsoft Office SharePoint Server 2007. Public refers to the URL of an externally accessible Web site. The public URL is the base URL that Office SharePoint Server 2007 uses in the pages that it returns. If the internal URL has been modified by a reverse proxy device, it can differ from the public URL.

Multiple internal URLs can be associated with a single public URL. Mapping collections can contain up to five authentication zones, but each zone can only have a single public URL. Mapping collections correspond to the following authentication zones:

  • Default

  • Internet

  • Intranet

  • Extranet

  • Custom

For additional information about zones, URLs, and to view a corporate deployment scenario for each zone, see the Logical architecture model: Corporate deployment.

Host-named site collections cannot use alternate access mappings. Host-named site collections are automatically considered to be in the Default zone, and the URL of the request must not be modified between the end user and the server.


If a reverse proxy server or load balancer receives a request from the user as and forwards it to the server running Windows SharePoint Services 3.0 as, the administrator would configure the following URLs for a SharePoint Web application:

Internal URL:

Public URL:

For this example, https://sharepoint:1234 is already an AAM URL that is assigned to a Web application and the Internet zone is used.

To configure an internal URL, use the following syntax:

stsadm -o addalternatedomain -url https://sharepoint:1234 -urlzone Internet -incomingurl

To map the public URL to the URL zone, use the following syntax:

stsadm -o addzoneurl -url https://sharepoint:1234 -urlzone Internet -zonemappedurl


There can be only one public URL per URL zone. This is the URL used in Web pages or e-mail messages going from the Web server to the reverse proxy server or the client.

To confirm the change to the internal URL, use the following syntax:

stsadm -o enumalternatedomains -url

See Also