On May 29, 2007, at 23:02, Thomas Harold wrote:
> Ryan Schmidt wrote:
>> On May 28, 2007, at 03:35, Holger Schulz wrote:
>>> 2. Currently I have a G4 desktop which holds the repositories. I
>>> have a PowerBook which I you for work at home and from outside. At
>>> home I connect the desktop from the book via its Bonjour name
>>> <something>.local, to connect it within my local net. From outside I
>>> have to use a global name (in this case via dyndns). So the problem
>>> appears that the same repository might apear under two different
>>> names. How can I tell the working copy that its repository has
>> In the working copy:
>> svn switch --relocate $OLDPREFIX $NEWPREFIX
>> where $OLDPREFIX and $NEWPREFIX are the parts of the URL that
>> changes. For example, if you're relocating from svn://foo.local/
>> repo to http://foo.dyndns.org/repo then you could issue
>> svn switch --relocate svn://foo.local http://foo.dyndns.org
>> However, I highly recommend that you set up a single hostname
>> under which you can access the repository regardless of where your
>> laptop is located. You will find this much easier, and if you want
>> to use svn:externals, this is the only way it will work
>> everywhere. For example, if you have a DNS server on your local
>> network at home, you could set up foo.dyndns.org to be a CNAME to
>> foo.local there, and for the rest of the world it will still be
>> your machine's public IP.
> Wait, I can setup a CNAME on a DNS server for a domain that I'm not
> authoritative for? How's that work? You've hit upon something
> that I've been meaning to fix for a while for our users.
> Folks who are rarely in the office are accessing the repository via:
> Where svn.example.com maps to the public IP address of our
> firewall, and we DNAT (port-forward) 22/tcp (ssh port) to the
> internal machine at address 192.168.0.5. The SOA servers for
> svn.example.com are outside the firewall at a public service
> Folks inside the firewall can use svn.hq.example.com, which points
> at 192.168.0.5. And the hq.example.com. is not exported outside of
> the firewall.
> We've been having users edit their C:\Windows\System32\Drivers\Etc
> \hosts file and add a manual mapping for svn.example.com to point
> at 184.108.40.206 for the weeks when they're in the office.
> Is this a special feature of a particular DNS server (i.e. BIND) or
> is it something that can be accomplished via almost any DNS server
> software? (Pity that all of my BIND books are packed away in boxes.)
Ok, I admit I haven't tried this setup myself. The setup I have
myself experienced involved a domain that we did own. Our public/DMZ
server at the office was the primary DNS server for the domain, and
it was (somehow -- don't ask me how -- I didn't do the DNS
administration) set up so that within our intranet, when we asked for
www.example.com, it would deliver the server's internal IP address,
but when someone from out on the Internet requested that same name,
it would deliver its public IP address. End result: it "just worked"
no matter where you were.
I assume you could do this with any domain, even those you don't own.
For those you don't own, obviously nobody else will be asking your
DNS server about that domain. However, machines on your network will,
since those machines are configured to ask your DNS server for all
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu May 31 09:47:16 2007