Masters i need your help about Domain usage

Here is my story

i succesfully installed DNN 4.3.1 to a virtual directory at Godaddy

here is the link : http://www.mikroproje.net/mp

and i have an old domain registered at another company (IHS)

i want to use my existing domain with my new site

can i point my existing domain to go directly my virtual directory? if so how can i do this

if not can u tell me how can i point my existing domain to my root

i tried a few things but couldnt make it work

Can someone tell me step by step how can i configure my existing domain to work with the new one?

---

Or-Rouge Team Or-Rouge
Personally recommend Hostgator for hosting single or multiple DotNetNuke Websites.
DotNetNuke Tips and Tutorials
Install DotNetNuke to Godaddy root
DotNetNuke Türkçe Hakkinda Hersey

Please read...

there is a problem with the install to the root on GoDaddy, the Events module fails to install.

I have checked this by installing both ways, to a virual directory and to the root.

the install to a virual directory is good and has the Events module there and working.

the install to the root looks like a good install, but for some reason the Event module fails to install completely. not sure what it is yet, the database looks to have the entries and the files look to have been put in place. but there is a string missing or wrong permissions set on folders for the module to work.

if someone would like to chime in...................

Hi,

I need some help.  I believe I've followed the posted instructions, but I am not getting very far.  I started with a fresh database and added the required directories with appropriate permissions.

But when I load the sire, this is all I get.

My website, is www.pokerzealots.com

Any help would be appreciated.

Chris

Server Error in '/' Application.

---

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>