Thank you Alan. Are you suggesting that via DNS records I have DomainA.com "live" in the same place as DomainB.com, and then host the .htaccess on DomainB.com's hosting space?

So somebody requests DomainA.com, the DNS points to the hosting for DomainB.com, and then the .htaccess for DomainB.com can process the original DomainA.com request?

Thanks, but does this help with 301s for inner pages?

Thank you. I'm actually not understanding. How do I Park A on B. What is "explicit .htaccess"?

Howdy.

I have just read this QA thread, so I think I have my answer. But I'm going to ask anyway!

Basically DomainA.com is being retired, and DomainB.com is going to be launched.

We're going to have to redirect numerous URLs from DomainA.com to DomainB.com. I think the way to go about this is to continue paying for hosting for DomainA.com, serving a .htaccess from that hosting account, and then hosting DomainB.com separately.

Anybody know of a way to avoid paying for hosting a .htaccess file on DomainA.com?

Thanks!