Routing: Resolve dynDNS hostname internally to local ip

is the following problem easy to solve?

I’ve got some git repos and added a remote. From outside there is a repository address git@my.externhostname.com/~/git/ …

  • Why is my Github-hosted site responding with HTTP 302 instead of 200?
  • Let git / go get use proxy domains
  • Custom Domain Github Pages
  • How to point domain to site hosted on github pages?
  • Error on WordPress Admin URL after moving from localhost to remote
  • TSVN DNS error: The requested name is valid, but no data of the requested type was found
  • From inside it is
    git@192.168.1.10/~/git

    is there any way to configure it dynamically, i.e. when I am within my personal network I want to resolve the adress my.externhostname.com to above mentioned ip.

    But if the address isn’t reachable (I am outside the network) I want to use a basic DNS server to resolve it.

    Any ideas?

    Thanks a lot!

  • Undo git push to Assembla
  • clone succeeded but checkout failed
  • Any benefit keeping old branches on GitHub?
  • Backing up open source gems in case they go away
  • A colleague has committed over my commit - how?
  • Create an offline version control for R Studio
  • One Solution collect form web for “Routing: Resolve dynDNS hostname internally to local ip”

    You need to configure a split DNS which pretends to own the zone for externhostname.com if it responds to queries on the ethernet interface going to 192.168.1.10. In other words, if you are on the private network, your DNS should never forward to DynDNS.com.

    Git Baby is a git and github fan, let's start git clone.