RealNames said:
In other words, we want the browser window to say webwhiz.net and NOT the actual site name, which in her example is highrankings.com, the real website.
.
You're trying to make something complicated out of something simple. You don't need javascript, forwarding, frames, masking, cloaking, redirects, etc. You just need one website that is either IP-based (rather than host-based) OR a host-based website that allows multiple host names or aliases. If you have an IP-based website, anything that resolves to the IP, regardless of domain name, even the IP itself, goes to the website, and whatever the user typed in the browser address bar to get there, stays there. Just be sure to use relative links (as mentioned earlier in this thread) for other pages within the site. If it's a host-based website, you'll have to configure it for every possible host address you want to work.
Some website hosting plans are not going to work well with this approach, since they are geared to single domain names with separate web space for each domain. But what you want is very simple with the right hosting plan.
I like the simple approach and don't like to do much configuration of parked domain names. I have one dedicated server (not all that expensive these days) that runs DNS, web server, and database server. The DNS is set up as wildcard DNS (matches any domain) and the web server is set up as IP-based. ANY domain name I point at the DNS of that server automatically gets pointed to the website there. No configuration required.
I went a step further and wrote a simple script (currently ASP on a Win2k3 box, but I did the same thing in the past with Perl, Apache, and Linux) that extracts the domain name, checks it against the database, and customizes the web page for the domain, if found in the database. Currently the database has a field that specifies which PPC provider to use for each domain name, and the script outputs a frame page filled with the results from that PPC program. If I want to change PPC for a domain, I just change that field (remotely using Access on my PC). Controlling the server means catching all traffic, even error traffic with custom error pages. My ISP (EV1) even provides an Urchin license, which I use for stats. A custom Urchin filter means I can track over 2000 domain names on one website. Nothing I have done is very difficult. It's just the end result of solving one little problem after another over a four year learning period.
I would recommend first to decide if you need to run your own DNS. If not, figure out what DNS you will use. Some registrars provide it free. Make sure you can set it up to match odd host names like 123.abc.456.domain.com so you don't lose any traffic. Once you have DNS find a simple hosting plan that gives you your own dedicated IP address. Point all your domain names at that IP with simple A or CNAME records. Don't use URL forwarding. You can use the same website for any number of domain names. Then get a page up. Set up custom error pages so you can catch non-existent URL's like
www.domain.com/123/abc/456. Then make it a little better every day.