Perhaps I am the one not understanding...

If you have your own servers (NameServers, IIS) [or a hosting service that does...] you have the control to point Domain1 anywhere you want and Chris Hammond's video shows you how.  [GoDaddy domain console lets you set external NameServers, etc.]

I was just trying to explain that you cannot expect Domain1 to point two (or 3) different places;  to the host root, (to the folder in which DNN resides if not root), AND to the ultimate destination (portal1). [DNN is smart enough to get you to portal0 by default if you at least land in the DNN folder]   You said Domain1/dotnetnuke/portal1 was the path, so that is what I took, literally.  

Domain Forwarding lets you point Domain1 [what the user knows] to a Domain2/PATH anywhere [which you, not they, know].  [GoDaddy Hosting (IIS) also lets you point Domain1 directly to Domain2/PATH within their walls w/o forwarding, via the Hosting Console].  

Domain Forwarding is kinda like trading a single-part (non-stop) ticket for a two-part ticket; part 1 gets you to the DNN instance and part 2 tells DNN where to send you ultimately.  You can't go from Paris to London to NY if all you have is a ticket from Paris to London...  A ticket from London to NY doesn't do you any good if you can't get to London.  This presumes you can't afford a non-stop ... (the direct control NameServers/IIS gives you)

You got stuck in the London airport with no ticket to nowhere, and they told you "go wait over there..."  If you had made it to the DNN Airlines gate they at least would have shuttled you off to portal0 for free.

Sorry if I took you too literally.

Bob

Bob, thanks for your explenation I didn't want domain1.com to point to 2 or 3 different places I just want this to go to 1 particular portal hoping that DNN is "smart: enough to figured out base on aliases which portal to display in similar fation when you have multiple websites on single IIS and you use domain name in bindings and IIS is smart enough to get you right website base on user reguest per domain anme bindings, I guess since portals are virtual dir this cannot be done in same straight forward fasion.
Anyways following you GoDaddy forwarding I was able to get this to work it is not ideal but works and I'm not sure how my setup is different from yours but somehow it is i.e. right now I get to home page by typying just domain1.com which is good but I noticed 2 things as I navigate thru website different tabs URL always display only domain1.com I donot see /contacts.aspx or home.aspx which is fine but I also notice that if someone dig and right click on the menu tab and do properties you will see xxx.com/dotnetnuke/portal1/tabname.aspx again not a deal breaker but I found this different when looking at your websites as an examples

thanks again for shearing this info

as far your latest post with refresh meta tab this is similar to my redirect.html page I had which was on the root of domain1.com and redirecting to domain1.com/dotnetnuke/portal1 problem with this is that it is displaying full path and I do not want this

first solution will work thanks