But I am hoping you've addressed this in one of your tutorials.

I need to have a subdomain/child portal(?) to my www.pwcparks.org website.  I need it to be:  report.pwcparks.org, or something like that.  Have you done a tutorial that shows how to create  or mess with Host Headers?  If you have, which tutorial would I use?  I do have the #17 issue, but it shows how you've already created Host Headers?

Thanks....btw, Joe...Mitchel Sellers is proving to be a godsend in help.  Thank you for referring me to him.  He is worth every penny,  just like DNN Creative is worth every penny.

Lee, I hope everything is going well with you.  Cheers!

Mark,

All that you need to do is create the second site, and it can be either a child site or a parent site.

You then have your DNS set up so that report.pwcparks.org will point to the same IP address as your other site. Finally, add a portal alias for report.pwcparks.org in your new site.

That should do it ...

----------
I'm glad my other recommendation is working out, too!

Hi Joe,

That's where I'm being thrown for a loop...setting up the DNS.  I'm with the county and do  not have access to their DNS server.  Am I going to need to have them do this?  If so, what exactly should I be telling them to do?  I only have access to my IIS Server.

Thanks,

Mark

Yes. If they manage your DNS, they are the ones with whom you will have to deal. Tell them that you want the new domain to point to the same IP address as the existing domain. On your end, all that you have to do is add the portal alias entry for your new site. You can do that now, leaving the existing alias. Then, you'll know that they've done their part when the new domain works.

OK, but where do the Host Headers in IIS come in?

I've contacted the county and they are going to add the pointers to the urls I want.  So that's going smooth. 

Or do I even bother with the Host Headers in IIS if DNS is updated?

No, I think that will break things. The requests should be forwarded to the DotNetNuke installation, and DotNetNuke then uses the Portal Alias entries to send the responses. This is ALL handled within the single DotNetNuke installation.

Right on. Thanks, as always, for your help! :-)