Forum Stats

  • 3,741,009 Users
  • 2,248,356 Discussions
  • 7,861,579 Comments

Discussions

WebHops and Redirects in Dyn Remote Access

Michael.R.Taylor-Oracle
Michael.R.Taylor-Oracle Posts: 255 Employee
edited Feb 7, 2019 4:26PM in Dyn Community

General Redirection

Redirecting a Remote Access (Dynamic DNS/DynDNS Pro) host to a different location is a fairly simple process. When creating or editing a host, select the WebHop Redirect option under Service Type. Under the WebHop section, enter the full URL (including http://) of the desired destination. Optionally, you can cloak the redirect by selecting Yes, cloak this page and entering a cloaked page title. Finally, click Create New Host or Save Changes to complete the modifications. Barring caching issues, you should be able to visit the host and see the redirect within minutes.

How Does Cloaking Work?

When cloaking is enabled on a WebHop, frames are used to mask the address and title bars. The address bar will remain set to the original URL and the title bar will be replaced with the desired text. For example, if you create a WebHop for <a class="jive-link-external-small" href="http://yourhost.oneofdynsdomains.org/" rel="nofollow">http://yourhost.oneofdynsdomains.org</a> which redirects to <a class="jive-link-external-small" href="http://some.otherdomain.com:8898/really/~long/url.html" rel="nofollow">http://some.otherdomain.com:8898/really/~long/url.html</a>, the address bar will only show <a class="jive-link-external-small" href="http://yourhost.oneofdynsdomains.org/" rel="nofollow">http://yourhost.oneofdynsdomains.org</a>.


Redirecting to an Alternate Port (e.g. 80 to 8000)

EXAMPLE

<a class="jive-link-external-small" href="http://yourhost.oneofdynsdomains.org/" rel="nofollow">http://yourhost.oneofdynsdomains.org/</a> redirects to <a class="jive-link-external-small" href="http://yourserver.oneofdynsdomains.org:8080/" rel="nofollow">http://yourserver.oneofdynsdomains.org:8080/</a>

Some Internet service providers block common ports, such as 80 (HTTP) and 25 (SMTP). Using our WebHop redirection service, you can circumvent this port blocking by redirecting to your server on an alternate port.

To create an alternate port redirect, you will need two hosts:

Visitor Host: This is the host that visitors will access when trying to reach your server.

Destination Host: This host will be assigned to your network’s IP address.

For example, you want visitors to use yourhost.oneofdynsdomains.org to reach your website, but your webserver uses port 8000. The visitor host in this case is yourhost.oneofdynsdomains.org. You need to create a destination host, such as yourserver.oneofdynsdomains.org, and assign this to your webserver’s IP address.

Once yourserver.oneofdynsdomains.org has been created, you will need to change yourhost.oneofdynsdomains.org into a WebHop host record. The WebHop URL will be:

<a class="jive-link-external-small" href="http://yourserver.oneofdynsdomains.org:8000/" rel="nofollow">http://yourserver.oneofdynsdomains.org:8000/</a>

Visitors to yourhost.oneofdynsdomains.org will now be redirected to yourserver.oneofdynsdomains.org, and the :8000 will tell their web browser to use the alternate port.

Remember, your visitor host yourhost.oneofdynsdomains.org must remain assigned to the WebHop server’s IP address. You should only update the destination host yourserver.oneofdynsdomains.org, so make sure your update client is only configured to update yourserver.oneofdynsdomains.org.


No Need to Enter a Port Number

EXAMPLE

<a class="jive-link-external-small" href="http://yourserver2.oneofdynsdomains.org/" rel="nofollow">http://yourserver2.oneofdynsdomains.org/</a> redirects to <a class="jive-link-external-small" href="http://yourhost.oneofdynsdomains.org:8080/" rel="nofollow">http://yourhost.oneofdynsdomains.org:8080/</a>

Many users do not want to enter a port number when entering a URL. Using our WebHop redirection service, you can circumvent this by redirecting your URL to an alternate URL that includes the port number.

To create a redirect, you will need two hosts:

WebHop Host: This is the host visitors will enter when trying to reach your server.
IP Address Host: This host will be assigned to your network’s IP address.

For example, you want visitors to use yourhost2.oneofdynsdomains.org to reach your website, but your webserver requires a port number as in this example:  <a class="jive-link-external-small" href="http://yourserver.oneofdynsdomains.org:8080/" rel="nofollow">http://yourserver.oneofdynsdomains.org:8080</a>.
When we are done, you will have (1) the IP Address host: yourserver.oneofdynsdomains.org assigned to your webserver’s IP address and (2) yourhost2.oneofdynsdomains.org (your WebHop host) redirects to yourserver.oneofdynsdomains.org:8080 (your URL with port number)

To Add a WebHop Redirect:
1. In the Add Hostname page on account.dyn.com, enter a new hostname for your visitors to use. Example: yourhost2.oneofdynsdomains.org
2. Select Service Type: WebHop Redirect (URL forwarding service).
3. Enter the URL with the port number into WebHop Settings (Redirect URL)  Example: yourserver.oneofdynsdomains.org:8080
4. Click Create Host to add the new hostname into your account.

Visitors to yourserver2.oneofdynsdomains.org will now be redirected to yourhost.oneofdynsdomains.org:8080.

Caution: Remember, your IP Address Host yourhost.oneofdynsdomains.org must remain assigned to the WebHop server’s IP address. You should only update the original URL yourserver.oneofdynsdomains.org, so make sure your update client is only configured to update yourserver.oneofdynsdomains.org.

This document was generated from the following discussion: WebHops and Redirects in Dyn Remote Access

Comments

  • I cannot seem to get the redirect to work with remote desktop client and the alternate port. The redirect seems to redirect, but it cannot connect through remote desktop. I have example.dyndns.org as my Destination Host and is updated with my current IP address (which I have been using for years). I access my home computer using example.dyndns.org:3399 with remote desktop just fine. I am trying to create a Visitor Host, visitorexample.dyndns.org, to access my home computer without needing the port number. I have created this with a WebHop to example.dyndns.org:3399, but the connection always fails. If I enter visitorexample.dyndns.org into a web browser it will error out saying that the page cannot be displayed and make sure http://example.dyndns.org:3399 is correct. So I can see that it is redirecting to the right address in the error (and it shouldn't be able to do anything in a browser, this was just a test to check on the redirect), but it errors out with remote desktop. I think part of the problem is that the WebHop contains the entire address including the http:// which is not used in remote desktop. If I use my Destination Host with the http:// included (http://example.dyndns.org:3399) in remote desktop, it gives me an error stating that I cannot use certain characters (:) in the computer name I am connecting to. Every time I try to have my WebHop address not include the http:// it is automatically entered. Is there a workaround to have the WebHop redirect not include the prefix? Is there something else I am missing with getting this to work with remote desktop?

    Thanks,
    Kevin

  • RotBlitz
    RotBlitz Member Posts: 149 Red Ribbon
    edited May 15, 2019 3:20PM

    I cannot seem to get the redirect to work with remote desktop client and the alternate port. The redirect seems to redirect, but it cannot connect through remote desktop. I have example.dyndns.org as my Destination Host and is updated with my current IP address (which I have been using for years). I access my home computer using example.dyndns.org:3399 with remote desktop just fine. I am trying to create a Visitor Host, visitorexample.dyndns.org, to access my home computer without needing the port number. I have created this with a WebHop to example.dyndns.org:3399, but the connection always fails. If I enter visitorexample.dyndns.org into a web browser it will error out saying that the page cannot be displayed and make sure http://example.dyndns.org:3399 is correct. So I can see that it is redirecting to the right address in the error (and it shouldn't be able to do anything in a browser, this was just a test to check on the redirect), but it errors out with remote desktop. I think part of the problem is that the WebHop contains the entire address including the http:// which is not used in remote desktop. If I use my Destination Host with the http:// included (http://example.dyndns.org:3399) in remote desktop, it gives me an error stating that I cannot use certain characters (:) in the computer name I am connecting to. Every time I try to have my WebHop address not include the http:// it is automatically entered. Is there a workaround to have the WebHop redirect not include the prefix? Is there something else I am missing with getting this to work with remote desktop?

    Thanks,
    Kevin

    Webhops can be used only with HTTP, not with RDP or any other protocoL

Sign In or Register to comment.