|
So I have done everything in the Guide here regarding setting up port forwarding in my router (Ozenda AR4505GW) etc. I have entered into the DDNS page of my router (which allows me to choose from http://DynDNS.org or http://TZO.com) the following: - Dynamic DNS: ENABLE Provider: http://DynDNS.org Domain name: http://www.myfreehostname.webhop.org Acccount: my DynDNS account name Password/Key: my DynDNS account password Everytime I enter that hostname into my browser when working remotely from my Synology (i.e. on the WAN not the LAN), e.g. http://www.myfreehostname.webhop.org it returns a message saying 'Link broken', or 'server cannot be found'. I am very frustrated as it has taken hours of messing about only to find it will never work. What is the secret? Does it actually work for anyone out there??? |
|
There is no secret, as your hostname is not www.myfreehostname.webhop.org, but just myfreehostname.webhop.org. You would need to upgrade to DynDNS Pro to allow for so called wildcard CNAMEs, i.e. *.myfreehostname.webhop.org. Therefore, to reach the network from remote, you have to enter just myfreehostname.webhop.org into the browser's address line. In case you want to connect to another port than 80 or another protocol than HTTP, you have to specify the port number and/or protocol too, e.g. myfreehostname.webhop.org:8080 or https://myfreehostname.webhop.org or ftp://myfreehostname.webhop.org:2121. The www is totally irrelevant here and has nothing to do with the browser functioning or not. A DNS entry of www.myfreehostname.webhop.org simply does not exist, so cannot be used. In case you do not want to enter the protocol and/or port (other than HTTP and/or 80), there is a solution too. Just set up a WebHop redirection, i.e. a second hostname as WebHop like: Now, when entering myfreehost.webhop.org into the browser, it goes to myfreehostname.webhop.org using HTTPS over port 55443. If this helps, don't forget to click the check mark, so that we know, and the thread is marked as answered.
Mar 06 at 08:44 PM
RotBlitz ♦
Thanks for your answer RotBlitz. There is some missing information here though....what exactly do I enter into my browser URL when I want to access my router from a remote (WAN) connection? If I do not enter 'www.' before 'myfreehostname.webhop.org' then the browser will fail to locate my router won't it? So what do I enter into the browser?
Mar 07 at 11:06 AM
cobalt19
See my edited message answering your question. Really, this www is and was pretty irrelevant all the time, see https://ssl.scroogle.org/cgi-bin/nbbwssl.cgi?Gw=www+prefix+url - not sure why people would insist in it...
Mar 07 at 02:34 PM
RotBlitz ♦
Thanks again RotBlitz. Now it works - but I dont know why it does work without www as I thought every URL had to have one in. One of the posts on that scroogle page you referred me to suggests that I might be open to a 'browser hijack' if I do not use www in the browser URL. IS that correct? What is a browser hijack anyway?
Mar 07 at 06:29 PM
cobalt19
No, that www isn't a holy cow in any way. Either the website owner has configured it with an A or CNAME record in DNS, so it's there for a certain website, or he didn't, so it's not. A browser hijack is something redirecting your browser to a website you didn't intentionally want to visit. There are so many methods, but the www one I would think of at last...
Mar 07 at 09:37 PM
RotBlitz ♦
|
