Domain Names Pointers

zimmo

Verified User
Joined
Apr 29, 2005
Messages
8
I wonder if someone can tell me how to do the following:

1: We have our domain name with space and email etc etc.. but we want to create another domain to point to this one. Okay I know you can use domain pointers, but the problem is that we cannot then change the mx records which we need to do?

How can we set this up so that we can point the domain to the other one and have the ability to change the MX records.

I wonder is someone could please tell me how this is done, or if there is a workaround.

Thanks
Barry
 
What I would do is create the second domain seperately as a different account and then install a new index.html with a redirect or refresh in it. That way you can have email at both domains.

or am I missing something here....

-drmike
 
Hi I thought of doing this, but on our old server here in the UK, we could have lots of domains pointint to the same location:

Here is an example of what we used to do:

1: We add the domain to the nameservers
2: We then add the domain to our account
3: Then we can point lots of domains to the same location, and have email etc.. for each one, and also change the mx records for each one.

I cannot believe this is not possible on my server using directadmin.

I do not really want to create another account and use a redirect as for one this is very poor and two people will move away from the domain. Is there not a way of just creating a new account and then pointing this to the webspace of the other account? Very simple and a must for us really.

Domain pointers are great, but only do half of the job from my experience.

Any help grateful.

Thanks

Barry
 
If the account has unlimited domains, you don't need to create a new account, you just need to add the domain to the current account.
 
ballyn said:
If the account has unlimited domains, you don't need to create a new account, you just need to add the domain to the current account.

I thought of that as well but from the way the question was worded, it sounded like the seperation of domains was important. Maybe I just went for overkill. *shrug*

-drmike
 
I did see that one. So how does this work then. I have unlimited domains set up for the account.

At present there is one domain, so if I add another domain will that point to the same webspace? I know that you have to log in to each domain which I dont mind when you go into the account, but will it point to the same space I set up for the previous one.

Thanks

Barry
 
No it would point at seperate web spaces. Since the original poster made it sound like that he or she wanted to keep the mail records seperate (and maybe have seperate mailboxes for each domain) I suggested this route.

- Create the main domain and place the site there.

- Create the second domain with the forwarding domain address.

- Within that second domain, create an index.html file with the following in the header:

<META HTTP-EQUIV="refresh" CONTENT="0;URL=http://www.therealdomain.com">

That way the visitor gets forwarded onto the first domain but you still have access to email and whatnot on the backend.

-drmike
 
This is a very poor solution and is no good to my client, I switched over to my new provider in the hope things would be fine.

The site has over 100 listings within search engines and for me to do it this way would not work at all.

I am just trying to find a way of pointing the same domain to the same webspace.

On our old server we could do this no problem, and have as many domains pointing: here is an extract from my http conf file on the old server:

<VirtualHost>
ServerName guitarschool.co.uk
ServerAlias www.guitarschool.co.uk
ServerAlias www.anotherdomain.com
ServerAlias anotherdomain.com
DocumentRoot /www/vhtdocs/guitarschool/public_html
ScriptAlias /cgi-bin/ /www/vhtdocs/guitarschool/cgi-bin/
</VirtualHost>

So the way the above worked was that any domain I added as an alias would point to this space, but I still had the ability to change the MX records and also sort out email etc..

Thanks Urgently

Barry
 
The thread has been moved to "General Technical Discussion & Troubleshooting" as the HowTo secion is strictly for HowTos, not for requests.

This has been discussed previously.

It can be done easily enough at the admin level by creating a modification to the httpd.conf container using ServerAlias.

If you're not an admin, but rather a site customer or reseller, you'll need to ask your provider to do it for you.

Jeff
 
Back
Top