I have not set something like this up before, but yes those would be the 3 possible ways I would approach it.

In terms of SEO, options two and three should give you the best results, I am unsure with option1 if a search engine will be able to index the various languages.

Regarding implementation, first question I would ask is how big the site is likely to grow?  Will there be any advantage to using portals in DotNetNuke?  personally, if I am creating a site with subdomains, or even multiple domains I tend to create the sites with separate DotNetNuke installations.

The main reasons for this are that if a DotNetNuke installation has a problem the other URLs can display while we fix the problem. I also find it easier to backup and maintain separate installations.

You may want to have a read of this tutorial:
Portal Considerations (When to use Multiple Portals / Parent / Child or create a new DotNetNuke installation)

I will be interested to hear how you go about setting this up, keep us posted with your progress, thanks,

Hi,
the main reason that I'm choosing to create one installation is that I'm using some commercial module (listX) and the license is only for one installation, and also the hosting. I know the fact that an error on one site could have an impact on the other site, but I'll try.

Regarding the site, I hope that only the databse will grow (it means that I will have many subcriber )

Actually I've implemented the first solution, because is more simple to develop one site then duplicate a site for each language.

I've read the tutorial, but I don't have find what I need.

A question, but if I will create different child portal in a single installation, How can i setup dns of my hosting to have 3 domains like the previous mail?

I will post the site when It will be live.

Thanks
Vincenzo

Hello,

If you are setting up multiple portals, have a look at these tutorials:

• DotNetNuke and Multiple Portals
• How to create DotNetNuke Portals (Parent and Child)
• Portal Considerations (When to use Multiple Portals / Parent / Child or create a new DotNetNuke installation)
• DotNetNuke Portal Aliases
• DotNetNuke Portal Templates and the Site Wizard
• Managing and Configuring Portals as a Host Super User

Hope this helps, thanks,