QUOTE(weikee @ Mar 25 2012, 11:04 PM)
You try to use the same url for the local ip? I have not done this, but usually when using same fqdn, we translate to local ip, instead of using publicl ip.
because previously it works with tplink's 1043nd, but i can't seem to configure it to work in such a way on mikrotik. maybe perhaps the way 1043nd does is provide loopback?
other workaround i was thinking is.. would be putting a static dns on the router?
so from WAN it access via dyndns's mapped ip, and while in LAN it access via static dns on the router?
//the static dns workaround gives another issue, which i have several portmapping to other servers. 8060 to server1, 8082 to server 2, if use static dns.. there is no way to resolve to 2 different ip
solution found, its called hairpin NAT, so far the same URL works on LAN and WAN
This post has been edited by jinaun: Mar 26 2012, 12:24 AM