Multisite domain management

If you have a multisite Sitefinity CMS instance and you have configured more than one site in a your Sitefinity instance, you have to further configure the domains of the frontend for both the Sitefinity CMS application and the .NET Core Renderer.

NOTE: If you have a single site in your Sitefinity instance, then no further configuration is required.

Case: Sitefinity CMS is hosted on IIS

If the Sitefinity CMS instance is hosted on IIS and the domains are placed on the Sitefinity CMS application, you must remove these bindings and place them on the .NET Core Renderer application. These domains must be placed on the Renderer app, regardless of whether it is hosted on the same IIS on the same machine or on a different machine.

EXAMPLE: If your Sitefinity has the following to domain configuration:

Sitefinity CMS application:


When you configure a .NET Core Renderer, these domains must look like this:
.NET Core Renderer application:


Sitefinity CMS application:
One of the following:

  • If hosted on the same IIS - localhost:8080 (port of your choosing)
  • If hosted on a different IIS – yourcustomdomain
  • If hosted on a different machine – the IP address of the machine where Sitefinity CMS is placed.

In general, place all the public multisite domains on the .NET Core Renderer app and reserve a single non-public domain for the Sitefinity CMS app.

Case: Sitefinity CMS is behind a proxy (CDN, Reverse Proxy, Load Balancer)

In this case, the domain management is already placed on the proxy itself and the proxy forwards the specified Host header to Sitefinity CMS. You only need to redirect the proxy to forward the traffic to the .NET Core Renderer app.

Want to learn more?

Sign up for our free beginner training. Boost your credentials through advanced courses and certification.
Register for Sitefinity training and certification.

Was this article helpful?