|
Hello everyone. I've had dyndns working fine for a while now, but since yesterday (and I don't think that I changed anything) I have the following problem. I have a dyndns account, say http://mydynnick.home.com. The router supports dyndns, and it is configured properly. Internally, I have
Now, if I try to access http://mydynnick.home.com using the proper protocol and port combination from outside of my lan, all works fine (ie, the requests are correctly forwarded to the proper service hosted by the qnap). On the other hand, if I try to access http://mydynnick.home.com using the proper protocol and port combination from inside of my lan, they aren't forwarded to the Qnap, but they are handled by the router itself (ie, ftp and mysql time out, and the web server request gives me the router's web configuration page rather than the qnap webserver page). Obviously, if I use the internal ips rather than the dyndns alias from inside* of my lan, all works flawlessly. Why is this happening? Most of all, why did the dyndns alias work just fine from inside* of my lan too, at least till yesterday? Thanks everyone, Rob |
|
The only thing that will have made it work before was your router, so if it doesn't work any more then the problem must relate to the router. I assume you didn't put an entry in your local hosts file to map the hostname to your LAN IP?
No idea - if it turns out to be the problem you'd have to ask your router manufacturer. |
|
No I didn't have anything in the hosts file before. I do have the qnap ip - dyndns alias in the hosts file now tho, so it is somewhat working again, at least from that single pc, the others would require the same change, and that change I can't necessarely do on every terminal that I use inside the lan (smartphones etc). The only thing that I changed was disabling my router's dnla server, used to stream files from the router's usb port, which I'll never use. I can try turning that back on, but how can it have influenced this? |