I have an existing domain. I wanted to start using DNN for it so I created a portal and did all of the page creating and editing.

I now want to take www.myolddomain.com and point it my DNN portal site.
Under Host>Portals I selected  www.myoldomain.com and put a portal alias in to www.myolddomain.com
In IIS Manager I change the home directory to point to C:\DNN\Website.
When I go to www.myolddomain.com it doesn't show the correct page/portal it shows only the default portal for DNN.
I have 3 other www.maindomain.com sites and they all go to the correct portal.
What am I missing that it will only go to the default portal?

You IIS website should point to the physical directory that holds your DotNetNuke installation.

Your portalalias table should refer to the site's domain name.

The final piece is that you need to adjust your DNS settings so that your domain name points at the IP address serviced by your IIS.

You may have to adjust the http headers in IIS, but this is the point where I usually ask for help from someone who knows that he is doing.

You can put an index.htm file in the root directory. Then requests to www.myolddomain.com should result in that file being served up. This should show that IIS is pointing at the right place.

Next, put an app_offline.htm file in the directory (after removing or renaming index.htm). Now, that file should be served. This will show that ASP.NET is working with IIS, independently of DotNetNuke.

Finally, removing index.htm and app_offline.htm should result in your DotNetNuke site being served.

The the first step doesn't work, it's an IIS problem.

If the first step works and the second doesn't, then it's usually and ASP.NET problem.

Hi,

I have got a new DNN solution working on our new server. To resolve this in the browser, i wast just using the server name. http://ent-intranet01.entplc.net/dotnetnuke/.

We are now looking at releasing this live so I wanted a more meaningful URL. I created a host entry in IIS called IntranetDNN. Had our infrastructure create a DNS record called the same. I could then type the new URL in the browser and it would work (http:\\IntranetDNN). However once the site is hit, the URL changed back to the original one. I thought this might be because i hadnt added IntranetDNN into the portal alias table.

So i edited the existing portal alias using the host account added a new one in by clicking 'Add new HTTP Alias'. The site now resolves and keeps the IntranetDNN URL, BUT...everything is messed up on the site, the content is there, but it looks like its not picking up the style sheet, it cant find the images there are errors on the page.

Does anyone have any ideas why this might be, feel like im 95% there.

Thanks

Kevin.

hello,

Did you find a solution to this problem? Have a look at one of the URLs for your images and see if it is still referencing the old domain.

For problems like that (in the Text / HTML module) you may want to have a look at this tutorial:

Find and Replace SQL queries for DotNetNuke
(To fix problems after transferring a localhost database to a live website and other useful functions)