Hi Terence:
Again thank your for the detailed response.
I forgot to leave that step out. Yes I do then also set up a Parent Portal in the DNN installation.
The server I have domains on uses PLESK (don't know if you're familiar with that). Anyway at present I have to add the domain alias myclientdomain.com.au under my domain e.g., yourdomain.com.au in order for DNN to display the appropriate web site. The limitation here on having aliases on my hosting domain is that you cannot then add email address accounts.
If I then ad a new dmain to my host account on my server using the PLEASK control Panel, www.myclientdomain.com.au so I can generate emai accounts for this domain, however I cannot add this domain if my own domain where the DNN installation is (yourdomain.com.au) has a domain alias the same as what I'm trying to create a new domain as it just doesn't accept it and rightfully so.
I can do the following as your suggesting in your last paragraph:
1) Create a Parent Portal in DNN (www.myclientdomain.com.au)
2) Create a new domain account on my PLESK server (www.myclientdomain.com.au)
3) I can then set this domain to forward to a URL.
However I do not know with Parent Portal setups in DNN on how to resolve the URL. I can if it's a child portal, but cannot work it out if it's a Parent Portal. Assume the Parent Portals alias is www.myclientdomain.com.au and the Portal ID is 25, what woul dbe the URL to resolve to theis web site?
Also on another topic, if DNN in architecture only really has 1 web form 'Default.spx' and the content is provided via the database, then is this any good for indexing with search engines? For example if a web site in a traditional sense has a About Us page which would resolve in the following URL: 'http://www.example/aboutus.aspx' then this can be indexed for search engines, but how does DNN handle this if there isn't 'really' a physical 'About Us' page?
I can't even get Google to recognise my main DNN installation in it's search. I have verified the site but the robots just keep throwing a 404 Not Found Error.
Thanks,
Josh