Anyone can forward their names to any site they wany. There is nothing stopping them.
What's il/legal about forwarding a domain name to a website, danidan? What.
Do you have in mind?..
I would think you would like to have the added traffic? What is the problem?..
In a nut shell if he's causing you problems it's not allowed.
There are plenty of reasons you wouldn't want someone to forward traffic to your site. How would you like to get kicked out of every PPC programme simply because someone forwarded a name with lots of unacceptable traffic to your site?..
Folks, what about making a fake PR?.
Good or bad, I would not allow. There could be other implications such as users associating that particular domain name to your site but then later on that traffic is used for fradulent reasons or what ever. JMO.
You could ban reffers from his site using htaccess and catch the traffic and put affiliate links on it, I have done that in the past...
Can you explain a little bit more on how it is done?.
I am no .htaccess guru, and someone may come-up with a better way to do this Let's asume you have two sites you don't want referring to yours (and we shall call them "badguys.com", "badgirls.com", & "spammers.com"), you would use the following to block their referred links: Note, in the above, that the last "RewriteCond", that it does not end in "[NC,OR]". If you only have one referrer being blocked, put it at the end of the line. If you have more than one, put it on the end of each "RewriteCond" statement except the last. You'll also note a "\" before the "." in the domains - leave it, as it is syntax.
The above will give a 403 error (the commonly called "Forbidden" error), if the user's browser actually returns a referrer header from the listed domains or any subdomains on them. An example of a 403 error can be seen here. The line that says "# Options +FollowSymlinks"...remove the "#" if your are not sure rather or not your server has FollowSymLinks enabled, and put the "#" back, if you get a "500 Internal Error".
You could change the last line to read "RewriteRule .* http://yoursite.com/bad.html [R,L]" , which would show a customized page telling them of the bad referrer's nasty actions, instead of the 403 error which most users would wonder why they were denied-access for.
Their are many sites that explain the above in more detail. I suggest you look at www.doriat.com or just do a search for "mod_rewrite" and ".htaccess".
If this doesn't help, let me know..