Domain Routing
There are a number of different ways to make your domain display the content located at another hosting provider. These three different ways are dependent on the configuration of the hosting provider. If you are unsure of which method to use, usually providers will have instructions on what method to employ.
- Forward your Domain Name to another Domain Name
A domain name is an identification string that defines a realm of administrative autonomy, authority, or control on the Internet. Domain names are formed by the rules and procedures of the Domain Name System (DNS).. If you have another domain name to forward your domain to, choose this option. - Utilize Webnames' Name Servers and our DNS Advantage service to control your own DNS The Domain Name System (DNS) is a hierarchical distributed naming system for computers, services, or any resource connected to the Internet or a private network. It associates various information with domain names assigned to each of the participating entities. A Domain Name Service resolves queries for these names into IP addresses for the purpose of locating computer services and devices worldwide. By providing a worldwide, distributed keyword-based redirection service, the Domain Name System is an essential component of the functionality of the Internet. records. If you have been given 'A records' or 'CNAME' etc. then use this option.
- Utilize the Name Servers of another party to control the routing of your Domain Name. If you have been given two or three new name servers to assign to your domain (e.g. ns1.yourhostingprovider.com etc.), utilize this option.
This is the simplest of the three options, and is free to do. If you have another domain name to forward your domain to, choose this option.
- 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 destination URL In computing, a uniform resource locator (URL) (originally called universal resource locator) is a specific character string that constitutes a reference to an Internet resource.
Both www.webnames.ca and www.webnames.ca/domain are examples of a URL that you would like to forward your source 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.
HTTPS
Please note that while HTTPS HTTPS: Hypertext Transfer Protocol Secure is an extension of the Hypertext Transfer Protocol (HTTP). It uses encryption for secure communication over a computer network, and is widely used on the Internet. In HTTPS, the communication protocol is encrypted using Transport Layer Security (TLS) or, formerly, Secure Sockets Layer (SSL). The protocol is therefore also referred to as HTTP over TLS, or HTTP over SSL. destination URLs are fully supported with URL Forwarding, in order for the initial domain to also be accessible via HTTPS, our Advanced DNS or Premium DNS Hosting is required.
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 |
Troubleshooting
Blank Page when Gripping is Used
If, after applying forwarding with gripping, a blank page is displayed instead of the intended destination, it could be that your destination page is coded in such a way as to prevent it from being loaded within an iframe. This specific issue can further be confirmed by temporarily disabling the Gripping feature, and then confirming that the issue is no longer present. An iframe is the technology which is used to accomplish the Gripping feature.
Please see the following link for more information and for possible solutions: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options
This is the most flexible of the three options, but does require the purchase of our add-on DNS Advantage Service. If you have been given 'A records' or 'CNAME' etc. then use this option.
*Please note that if the domain in question already has a hosting package (though Webnames), then DNS records A DNS Record is the basic data element in the domain name system. Each record has a type (A, MX, etc.), an expiration time limit, a class, and some type-specific data. DNS Records provide resolution or translation of domain names to IP address. for the domain may be added without requiring our Advanced DNS service. In this case DNS records can be managed from within your current hosting Control Panel
To Purchase Advanced DNS
- Log into your Webnames.ca account
- Navigate to Account > Domain List
- Click on the domain in question, leading to Domain Management
- Under the Domain Configuration heading, click the Purchase button beside DNS Advantage
- Proceed through the Shopping Cart.
This service will yield you an Advanced DNS tab within Domain Management, whereby you can create all the DNS records required for the operation of your domain.
See Also: Creating DNS Records
|
NOTE: When updating the functionality of your domain using any of the options above, the changes are committed immediately, however the changes will take time to propagate across the Internet to you. If you have visited your domain recently prior to making changes, you will be seeing a cached version of your site for 6 to 24 hours - even after making the changes. This is referred to as DNS propagation delay. Upon making changes to the functionality of your domain, you will need to wait the 6 - 24 hours it takes for the changes to 'reach' you, or alternatively you can try accessing your site via a device which has not visited your domain recently, such as your smart phone. Once you have visited the site, that instance is what becomes cached for the next 6 - 24 hours. |
Assign third party Name Servers
If you have been given two or three new name servers to assign to your domain (e.g. ns1.yourhostingprovider.com etc.), utilize this option.
| NOTE: This option affects the routing of all services for your domain. Ensure that all services for your domain (website, email etc.) are accounted for on these new name servers before switching. If you have email services with Webnames.ca and would like to retain them, please see this page before updating your name servers |
- 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 select Apply Name Servers
- Click the Configure button
- Enter in the name servers to assign to the domain.
- Note a minimum of two different name servers need to be assigned to your domain.
- Click Apply to save your changes