OK.  I have a site up and running inside my work domain. 

The portal alias table has a single entry for my site and the alias is testbox/myDNNSite

We have recently configured for SSL and the cert is for *.myWorkDomain.com.  

My site is now throwing up a cert error because "testbox" does not match the SSL cert wildcard.  I can load the site with testbox.MyWorkDomain.com/myDNNSite, but the next page load reverts back to just testbox/myDNNSite.

I thought I could update the portal alias to testbox.myWorkDomain.com/myDNNSite, but this is not working.  In IE, the page loads for a while and then times out.  In Firefox, I get a circular redirect error (or something like that).

My question: How do I make portal alias work with a fully qualified domain name? 

(I have tried searching forums for this problem, but I have not found other problems similar to this).

Thoughts?  Words of advice?  Please? ;-)

Thanks

-Sean

Did you setup DNS on your internal network to point to the install?  Typically I do something like this...

1. Setup an internal DNS entry on the DNS Server under MyWorkDomain.com such as DNNTest and point it to the server that is hosting the portal (i.e. testbox.MyWorkDomain.com).
2. Make sure that DNS is refreshed -- i.e. on the DNS Server I clear the resolver cache (IPCONFIG /FLUSHDNS).
3. Using the URL for the Host portal go to the website and add an alias to the appropriate portal using the fully qualified domain name (i.e. DNNTest.MyWorkDomain.com).

This has always worked for me but I don't use SSL for the portals I have setup so I'm not sure how that may be affecting things.

I hope this helps