Ok…I'm going to preface this article by saying I am not a fan of GoDaddy. My feelings for this company are based solely on my own personal experiences with this company as the result of using their web hosting services. I no longer set up any client sites with GoDaddy hosting at all. . . With one exception: for a purely static HTML site. My reasons are primarily driven by my experience with their customer service, not the product, and it’s a pretty safe bet that I don't have to deal with their customer service for an HTML site. If something does happen, it would be fairly easy to have to deal with. On the contrary, tracking down and troubleshooting issues with a DNN site can be more complicated. . . And again, my personal experience has concluded that for me, this is just not an option for me.
But, let's face it, GoDaddy is cheap. Pay for the hosting services and the domain names are $1.99, not a bad deal. And even without hosting services, you can pick up domain names for as low as $6.99. Put that together with DotNetNuke and you've really got no reason not to have more than one website, right? Sure…one for you, one for the spouse, one for the kids and one for grandma is all too easy to make happen. . . If you know how.
In the scenario above, I'm hosting domain names at GoDaddy but hosting my website somewhere else. Not a big deal, but you do have to make some adjustments in order to make the situation work. Before you begin, you'll need to make sure you have some information on hand.
- From your web hosting company, you'll need to know the Nameservers. For example, NS1.myhost.com, NS2.myhost.com, NS3.myhost.com. You should be given at minimum two (2), but most likely three (3) Nameserver addresses. You can usually find this information in your "welcome" e-mail as well as in the hosting account control panel. But, if you can't find it, just contact your host for the information.
- OR -
- You'll need the static IP address from you web hosting company IF you have one. (This is usually an add-on service that you'll pay for, so you shouldn't really have one and not be aware of it)
Now that we have the required information, head over to GoDaddy.com and login to their site. Throughout this article, I am going to use the domain I just bought ( thebamafan.com) for my husband who is a wild Alabama football fan (Roll Tide) and I’m going to point it to a pre-existing DotNetNuke website. Oh, and I’m also assuming that you have already purchased the domain name.
On the left side of the screen, you should see your menu (until they change their website that is)…and click on “Domains”. From here you will be taken to a screen that lists all of the domains that you are hosting with GoDaddy. Select “Manage Domain” for the domain that you would like to point to your DotNetNuke website.
On the Domain Management screen, you can see all the details about your domain. What we are interested in is changing either the Name Servers section, or the Forwarding section.
IF YOU ARE USING NAMESERVERS
If you are using Name Servers and not a static IP address then, click on the Nameservers icon 
. On the Nameserver management screen, you should select Custom Nameservers and then enter the nameserver information that you collected at the beginning of the article. After you have made the changes, it will take a few minutes for the GoDaddy servers to update their DNS record information and you will not be able to make any changes during this time.
One the information has been updated, you can see the changes back on your management screen:
IF YOU ARE USING A STATIC IP ADDRESS
Click on either the “Domain is not forwarded” link or the Forward icon near the top 
Check “Enable Forwarding” and then type in the static IP address of your website. Then, you will need to select either a 301 or 302 redirect. If you are interested in Google Search ranking, then a 301 redirect will make the search engine powers more happy.
According to a Google article here:
301 redirects
If you need to change the URL of a page as it is shown in search engine results, we recommended that you use a server-side 301 redirect. This is the best way to ensure that users and search engines are directed to the correct page. The 301 status code means that a page has permanently moved to a new location.
301 redirects are particularly useful in the following circumstances:
- You've moved your site to a new domain, and you want to make the transition as seamless as possible.
- People access your site through several different URLs. If, for example, your home page can be reached in multiple ways - for instance, http://example.com/home, http://home.example.com, or http://www.example.com - it's a good idea to pick one of those URLs as your preferred (canonical) destination, and use 301 redirects to send traffic from the other URLs to your preferred URL. You can also use Webmaster Tools to set your preferred domain.
- You're merging two websites and want to make sure that links to outdated URLs are redirected to the correct pages.
Now, that’s it as far as GoDaddy is concerned. Your domains are ready to be pointed to your new DotNetNuke website. But, that’s only one part of it. To finish the process, you’ll need to let your DNN website know that it should be expecting traffic for the new domains.