On Oct 16, 2:26 am, Eggert Ehmke <egg...@nickname.berlin.de> wrote:
> Hello,
It's really hard to follow what you're saying because your terminology
is so bad.
> We have a domain (i.e.www.orig.de) on a server where I don't have
Presumably
www.orig.de is a hostname in the orig.de domain. What does
it mean to "have a domain" on a server? Do you mean there's an A
record for
www.orig.de that points to an IP address assigned to that
machine?
> root access. We want to host the web contents on another server in a
> subdomain (i.e. orig.second.de) and redirect all requests for www.orig.de to
> orig.second.de. The redirection is no problem, but on
How is "orig.second.de" a subdomain? That just sounds like the name of
another server in the "second.de" domain. If "orig" is a sub-domain,
then how is it "another server"?
> the second server I want to create some rewrite rules to the effect
> that the users still see the original domain. Is this possible at all?
If I understand what you're asking, and I'm not really sure, this
sounds like a reverse proxy. Squid can do this.
> On the second server, I have root access and can configure apache to
> my liking. We want to avoid a domain transfer because the domain owner
What do you mean by a "domain transfer"? Do you mean just pointing
that one host name to another A record? That is neither a transfer nor
is it really a change to a domain. Normally a "domain transfer" means
a domain (like 'microsoft.com', not a host like 'www.microsoft.com')
is moved to another registry or the name servers are hosted by another
provider. It's very, very non-standard to call changing the A record
on a host a "domain transfer".
This makes me think I don't know what you're talking about and my
answer is completely wrong.
> wants to keep it on his server (but still wants me to host the website
> on my server).
What is the "it"? The thing you keep calling a domain that's actually
a host? I know what it means to host a website on a server, but why
are you on about transferring domains?
DS