I have DNN installed for a website that uses SSL and is hosted on an intranet site. Before we were granted a domain name within the intranet, we browsed to the site by using the server name e.g. https://servername/dotnetnuke. Now that we have the domain name (lets call it mysite.com) we can get to the splash page by browsing to https://mysite.com/dotnetnuke, but as soon as we click login, I'm sent to the certificate error page for a name mismatch. Once I click continue to this website, I'm taken to https://servername/dotnetnuke/login.aspx instead of https://mysite.com/dotnetnuke/login.aspx. I do have mysite.com/dotnetnuke in my portal alias table. In fact, if I remove servename/dotnetnuke from the portal alias table then try to browse to https://mysite.com/dotnetnuke, I'm taken to the DotNetNuke error page That begins with "DotNetNuke Error - Domain Name Does Not Exist In The Database" as if it's immediatelly looking in the DB for servername.

Can anyone tell me why the I'm being redirected to https://servername. Someone also suggested to me that the URL may be getting rewritten, but I don't know how that would be the case. Either way, can some shed some light on this situation.

BTW, I'm using DNN 5.6.6, but this has been an issue for us since we were using 5.6.0.

So I went into IIS and changed the host header to my new URL. I also changed the hosts file to contain the url instead of the server name. Still, when I click the login link, it redirects me to https://servername/dotnetnuke. I noticed that if I type in the url https://domainname/dotnetnuke/login.aspx, I do not get redirected. I can even navigate through the site without being redirected, that is until I click the logout link. I suspect that the issue has something to do with the javascript that is called when clicking the login and logout links. I'm just not sure how to correct this issue.