- Contact Us
Hello: I am puzzled. I have a home network (Windows & Macs hosts) plus a Synology Linux file server. Two external links to internet for testing & easy redundancy: A. A fast not too reliable: for all Windows & Macs, they are pointing to a Linksys WRT54G router using 126.96.36.199 as gateway itself pointing to 192.168.0.1 then to internet through a cable modem router Netgear CG3100. External IP address 188.8.131.52 (dynamically managed by ISP VOO-Brutele). The Linksys WRT54G router has its ddns service disabled. I think that my PC is not running another ddns client (I may have loaded this by accident? I don't know how to check for sure, does not show in Windows task manager). B. A slow quite reliable: for Synology Linux file server (192.168.1.45), it is connected to internet by an ADSL modem router Linksys AM200 with local address 192.168.1.241. The gateway specified in Synology is router 192.168.1.241. The external IP address is 184.108.40.206 dynamically managed by ISP Belgacom. Please note that Synology is running a ddns client connecting to DynDns and these internal & external address show correctly in Synology systems parameters. Note also that I saw that the AM200 router is also set up to run a ddns client to DynDns. After reading some posts here, I think that I should only keep only the ddns on Synology (otherwise potentially to many polls. Right? Then, which should I keep?). The AM200 has port forwarding set to 192.168.1.45 for port 5000. NB: The DMZ is disabled; it does not change if I enable it to allow only 192.168.1.45. All worked well, until 2 days ago & I don't know what I did wrong. No conscious material change except adding 2 alias names on Dyndns to give access to two other people with own names. When creating an alias, I don't understand why I need to specify my external public address as the Synology Server will provide it to DynDns, I guess? Do I create a potential problem here? Both ISPs are not blocking the 5000 port used by the Synology Linux box (DynDns offers a tool to check this). Also, when I look at connections log on DynDns, it looks allrigth. I am not a specialist but I see the Synology server making itself known to DynDns daily. Previously, when entering my dyndns alias http://paul.dyndns-at-home.com/, it was redirecting correctly to 192.168.1.45:5000/webman/index.cgi which is the Synology server login screen. Connection was slow but it worked flawlessly. I could also test it at home having two external internet links. Now, it is either not redirecting (no server found using any DynDns alias name) or more usually redirecting to the local 192.168.1.1 (the gateway router for the PCs), so it shows the Linksys router setup window if I enter the ID & PwD requested, not the Synology window! There was no portforwarding at all on the Linksys WRT54G (192.168.1.1). I put on it also a port forwarding to the Synology just to test but with no change. How can I make sure http://paul.dyndns-at-home.com/ points back again to the server 192.168.1.45:5000/webman/index.cgi and not to the wrong router 192.168.1.1. having a different public address than one specified at DynDns for this link? I can't figure out what can go wrong here as I re-checked everything (portforwarding, Synology setup, etc). Not a DynDns problem probably & likely to be a home set up one but I would appreciate if anyone has a clue at what could go wrong now & how could I debug methodically. Paul Brussels
Answer by DNS_GURU · Aug 26, 2012 at 12:22 AM
Everything seems to be good with hostname.. However,I suggest you to configure webhop with different port configuration. That shall solve the issue. In case you still face the issue. Please do not hesitate to contact me... skype: mujju_mirza Cheers, Mirza Mujeeb Baig. GVT India.
Answer by RotBlitz · Aug 24, 2012 at 10:36 PM
Your service on port 5000 currently responds, and
http://paul.dyndns-at-home.com:5000/ correctly redirects to
http://paul.dyndns-at-home.com:5000/webman/index.cgi. I cannot see any problem.
You're thinking about that you should connect from outside or at least via your other gateway, and that you have to specify the non-standard port unless you have a webhop configured, do you?