Just to clarify -- I didn't mean to imply that you have to use the IP to access DNN. In my setup:
- GoDaddy (Registrar) -- Domain primary and secondary nameservers are set to those assigned by ZoneEdit
- ZoneEdit (DNS) -- Allows adding/deleting/modiying DNS entries for a domain with a browser.
For all my DNN portals, I have IIS setup with one IP and one instance of DNN. IIS has two host headers for each portal (www.domain.com and domain.com). DNN has the same two aliases for each portal in the Alias field.
Whenever I register a new domain that I want to have as a DNN portal, I do the following:
- Add the domain to ZoneEdit which immediately assigns me two nameservers. I add entries for www.domain.com and domain.com pointing to my one IP.
- Register the domain at GoDaddy using the ZoneEdit-assigned nameservers.
- Add www.domain.com and domain.com as host headers to my single instance of DNN.
- Login as host in DNN and add a new portal. Set the portal aliases to www.domain.com and domain.com
As soon as the WhoIs database is updated with the new domain info, the portal goes live. If I ever need to redirect temporarily, I login to my ZoneEdit account and make the IP change to direct traffic to a different server and revert back when the maintenance or whatever is done.
BTW, it makes no difference where DNN is installed. As long as the portal alias matches the URL path, DNN will detect the portal correctly.
Nik
Nik Kalyani
Speerio, Inc.
[DotNetNuke and ASP.Net solutions
here]