name resolution internal and external?

Hello,

I'm not sure where to ask this question, but here is my problem.
I have OMV with owncloud behind my router at home. When at home, I access OMV through internal IP. So for owncloud to sync on my notebook, I use 192.168.100.137/owncloud

However, when I'm at work (external) I have to use mydyndns.org/owncloud
This works correctly because I have proper port forwarding.

However, I don't want to have to change my owncloud account address every time I move in/out of the house. I'd like to just use mydyndns.org and have it resolve correctly with port forwarding.

This isn't just an owncloud issue, but it gives a good example of the problem.

thanks

Zitat von "tekkbebe"

Uh, save 2 links in your browser. Don't make me say more on this.

The problem is that the owncloud client does the syncing, I'm not using the browswer. So each time I move locations, I have to modify the address in the client. It's not a huge deal. I just figure there must be a way around it.

Zitat von "ryecoaaron"

I would think the external address should still work on your home network, no? If not, you could add an entry to your hosts file or static lease to your router using the dyndns hostname.

I've already tried adding an entry into the hosts file. However I think I may have made a mistake with https. I'll test and report back.

Okay, so I handled the https incorrectly. Hosts file does work inside. I'll test the external later.

Yeah, what am I thinking. The hosts file will screw up when I'm outside the home. My notebook will be looking for 192.168.100.137, and obviously it won't find it.