For a description of this service, see our Domain Forwarding page , located here.
Domain Forwarding allows visitors to your domain name to be forwarded to another existing domain name. Domain Forwarding is Free with your registration or renewal.
Domain Forwarding Example:
- You have registered domain names such as sandwiches.ca and soups.ca
- You also have an existing website at xyzrestaurant.com
- By enabling Domain Forwarding on your registered domain names, when someone types sandwiches.ca or soups.ca into the address bar of their Internet browser, they get directed to oyour existing website at xyzrestaurant.com
To apply forwarding to your domain, perform the following steps within your Webnames.ca account
- Log into your Webnames.ca account
- Navigate to Account > Domain List
- Click on the domain in question
- Under the Domain Configuration heading, scroll down to Domain Value Bundle and Apply Domain Forwarding
- Click the Configure button
- Enter in the URL that you would like to forward your domain to (e.g. http://www.otherdomainname.com or http://www.otherdomainname.com/yoursite ).
- Click Apply to save your changes
Gripping
- Optionally, the Gripping option can be applied, which results in your source domain name staying in your visitor's web browser address bar while the content being displayed will be that of the destination. With this option unchecked, the forwarding will result in the address bar updating as the visitor is forwarded from your source domain to the destination site.
- Note that subdirectories/subpaths of the source domain will not be appended to the destination URL when gripping is enabled.
Examples
| Configured Destination | Client Browses To | Client is Redirected To | Notes |
|---|---|---|---|
| http://destination.com | http://source.com | http://destination.com | Basic domain forwarding; no path or query in the client requested URL |
| http://destination.com | http://source.com/ | http://destination.com | Basic domain forwarding; no path or query in the client requested URL |
| http://destination.com | http://source.com/sub/path/doc.htm?param=val#anchor | http://destination.comsub/path/?param=val#anchor | Request path and query always appended, even if destination URL already has them; will cause 404 not found due to lack of trailing slash causing invalid domain name |
| http://destination.com/ | http://source.com | http://destination.com/ | Basic domain forwarding; no path or query in the client requested URL |
| http://destination.com/ | http://source.com/ | http://destination.com/ | Basic domain forwarding; no path or query in the client requested URL |
| http://destination.com/ | http://source.com/sub/path/doc.htm?param=val#anchor | http://destination.com/sub/path/?param=val#anchor | Destination URL had a trailing slash, so client sub paths are appended properly |
| http://destination.com/dest/path | http://source.com | http://destination.com/dest/path | Basic domain forwarding; destination URL path preserved |
| http://destination.com/dest/path | http://source.com/ | http://destination.com/dest/path | Basic domain forwarding; destination URL path preserved |
| http://destination.com/dest/path | http://source.com/sub/path/doc.htm?param=val#anchor | http://destination.com/dest/pathsub/path/?param=val#anchor | Request path and query always appended, even if destination URL already has them; probable 404 not found depending on web server folders/routing |
| http://destination.com/dest/path/ | http://source.com | http://destination.com/dest/path | Basic domain forwarding; destination URL path preserved |
| http://destination.com/dest/path/ | http://source.com/ | http://destination.com/dest/path | Basic domain forwarding; destination URL path preserved |
| http://destination.com/dest/path/ | http://source.com/sub/path/ | http://destination.com/dest/path/sub/path/ | Request path and query always appended, even if destination URL already has them; possible 404 depending on web server folders/routing |
| http://destination.com/dest/path/ | http://source.com/sub/path/doc.htm?param=val#anchor | http://destination.com/dest/path/sub/path/doc.htm?param=val#anchor | Request path and query always appended, even if destination URL already has them; possible 404 depending on web server folders/routing |
| http://destination.com/dest/path/?param=val | http://source.com | http://destination.com/dest/path/?param=val | Destination URL includes a query (the part after the "?" character). Path and query still appended, but target web server will usually ignore |
| http://destination.com/dest/path/?param=val | http://source.com/ | http://destination.com/dest/path/?param=val | Destination URL includes a query (the part after the "?" character). Path and query still appended, but target web server will usually ignore |
| http://destination.com/dest/path/?param=val | http://source.com/sub/path/doc.htm?param=val#anchor | http://destination.com/dest/path/?param=valsub/path/doc.htm?param=val#anchor | Destination URL includes a query (the part after the "?" character). Path and query still appended, but parameter value corrupted due to lack of trailing "&" character; possible 404 not found |
| http://destination.com/dest/path/?param=val& | http://source.com/sub/path/doc.htm?param=val#anchor | http://destination.com/dest/path/?param=val&sub/path/doc.htm?param=val#anchor | Destination URL includes a query (the part after the "?" character). Path and query still appended, but parameter value preserved due to trailing "&" character |
| http://destination.com/? | http://source.com/sub/path/doc.htm?param=val#anchor | http://destination.com/?sub/path/doc.htm?param=val#anchor | Same as above, but the single trailing "?" character will cause most web servers to ignore the path |
See Also