Alias domain pointed to the sub domain

kspoosh

Verified User
Joined
Jun 21, 2005
Messages
22
Location
Honningsvaag, Norway
Hello,

I got a domainname (lets say domain.com hosted somewhere else).
On my DA server I got the domain domain2.com. And here I created an sub domain family.domain2.com.

Is it than possible to point domain.com to my DA server and make it work as an alias on family.domain2.com ?

I got domain.com setup as an CNAME for family.domain2.com, but in the DA it is only possible to add the domain as alias to domain2.com and not to family.domain2.com.

Thanks for your help!
 
Yes. Why are you continuing to host it on the other server? Because you need it there for some other services?

If you need domain.com itself hosted on your other server but need it's website on your DirectAdmin server simply do a redirect either with an .htaccess file or html redirection, on the other server.

Cleanest way would be to set it up as an alias to domain2 on your DirectAdmin server and just use the DirectAdmin server's IP# in your zonefile.

Jeff
 
Hello,

I need to keep the domain hosted on the old server due to some e-mail systems running there. And the client insist to keep the DNS management tool with the other provider.

.htaccess would not work as an alias. That will be a redirect, and the client wants to keep the original domain as URL in the web browser.

On domain2 there is already running a big site. That is why I would need to connect the domain1 to a sub-doman of domain2. :(

Thanks so far!
 
You write that you need email on the old server, but I asked something different: do you need (for example) www.example.com to point to the old server? If not, the answer is to simply use an A record for www.example.com which points to the new server. If yes, then use an .htaccess redirect to redirect example.com on the old server to www.example.com, and luse an A record to poing that to the new server. The client probably won't care if example.com is redirected to www.example.com.

Then on the new server create a custom user-level httpd.conf file to point it to a subdirectory (you'd have to chattr the file immutable so you'd lose the flexibility of using DirectAdmin to manage the file) or do something else creative (I'm not taking the time now to figure that out; I'm just too busy).

This is probably the best I can do.

Jeff
 
Back
Top