either use a page forwarding offered by the domain hoster or multiple DotNetNuke portals inside a single installation (log in as host user, go to host :: portals and click add).

If you want the domain or subdomain to direct to a landing page integrated with the main web site with few or no child pages, then creating a one-page portal to redirect back into the main web site structure seems a bit clunky. Page forwarding or redirection by the hoster would be the way to go if the hoster allows it.

I also wonder how search engines handle DotNetNuke redirects. I have read that using html or javascript redirects are not advisable because it negatively impacts search engine ranking. I have read that 301 redirects should be used instead; however, 301 redirects are not straightforward to the nonprogramming DotNetNuke administrator. So even if I go ahead with the clunky portal for each subdomain-specific landing page, I would be concerned about the impact on search engines. Do you know what kind of redirect the built-in DotNetNuke redirect is and how it impacts search engine ranking?