Re: crest.d.o and m68k.d.o
Following up on the crazy idea:
> > Correct. So the IP numbers will have to change sometime, once we have new
> > hosting, but I wont promise that this will be possible this year...
> Either way, let's fix the DNS - and keep the TTL low so a change will be
> I'm just wondering if there is a way to redirect DNS queries for crest to
> a dyndns service without the debian.org DNS getting involved in dynamic
> DNS itself ...
Having thought about that for a while, I am sure that a CNAME redirect
would work, but would obviously not allow for transparent ssh or http
access (do we also need smtp??).
Currently, the debian.org entries still point at their old addresses in
Duesseldorf (only the local DNS entries have been deleted by me, and
debian.org DNS obviously did not use CNAME). So instead of changing the IP
addresses, we could perhaps route traffic to crest and kullervo to
Christian's DSL at the router/firewall in Duesseldorf, or set up a VPN
tunnel to Christian's router?
Re: Christian's question on Debian dynamic DNS - there is no such thing
for debian.org, but it is not required if you have an entry in the zone
file like this:
crest CNAME crest.cts.dyndns.org.
(mind the trailing dot :-)
That should redirect DNS queries to the dyndns.org server, which needs to
be up to date, of course.
Routing/VPN off Duesseldorf would give you a quasi static address (we
would need to put a similar mechanism in place to update the route entry,
whereas for VPN you would just have to reopen the tunnel after an IP
I assume iptables can be tweaked to redirect port 22 for crest to port
2622 or whatever on sol, with similar tricks for http and smtp. I would
have to look at some example rules to pull it off, though.
Note that I will have to clear any of this with the biophys IT guys, and
it would take a while to set up. Pointing crest.d.o and m68k.d.o to
Christian's dyndns would be quicker but less functional.
P.S.: new disk for kullervo? When did the old one die, then?