Domain Pointers

[Protollix]

Currently, when you add a domain pointer, it just redirects to the main domain.

Can we make this so it does not redirect, but just serves content from the same directory? There are some instances where the user does not want the URL in the address bar to change from what was originally input.

CPanel does it this way.

Maybe make it a on/off option so we can have it both ways?

[nobaloney]

A domain pointer is just that, a pointer, and it should point to the target domain. It also points email to the target domain as well.

And that is how it should be.

Perhaps DA also needs an automated way to install a domain alias, which would do exactly what you want.

Jeff

[Protollix]

Well ok. Either way, it essentially does the same thing ;)

ie: the mail would still be redirected but the web url would *look* different, but serve the same content.

Alias/Pointer, same thing to me :p

[blacknight]

The current way that DirectAdmin does this is really annoying.
A domainalias would make a lot more sense.
A lot of our clients were used to domain pointers being setup as aliases, which is the cleanest way of doing it.
The DA way at the moment is very reminiscent of RAQ4s (yeuch!):


<VirtualHost xxx.xxx.xxxxxx:80>
ServerName blah.com
ServerAlias blah.com www.blah.com
Redirect / http://www.otheerdomain.com/
User otherdomain
Group otherdomain
</VirtualHost>

Why can't it simply be a:


ServerAlias

inserted into the existing vhost, rather than adding another vhost entry

[apryan]

Not sure if this is the reason or not, but...

In thinking of this as far as code goes, it would be very easy for DA (the code) to simply add a variable into the conf rather then to search for the right one and add a alias line into it.

Also, the professional way to do redirects is by simply adding a new entry. Yes, annoying to a admin's eyes.... but very straight forward for the coder. Plus, it's how plesk does it too.

-anth

[blacknight]

This thing with the domain alias is becoming a real issue for a lot of our developer clients.

Many of them need to be able to setup a new hosting account for a client before it gets moved from the current provider or from a windows server. Although you can preview basic html sites using the ~username method this does not work so well when you have mod_rewrites etc., in the php code (or whatever)
Basically a developer would need to be able to setup domain.tld - as this would be the permanent "new home" for a site, but needs to be able to test it fully using something like clientname.developerdomain.tld

The current way DA handles this is a PITA

[ClayRabbit]

A lot of DA users aking for ServerAlias'es instead of Pinters many times and from long time ago.
ServerAlias is wanted by customers, is much more useful, and finally i suspect it's uses less memory in apache process cos it's not require additional virtualhost.

But still our suggestions has no effect. :)

[blacknight]

Our helpdesk is flooded with requests for them :(

[mike_p]

wouldn't the quick workaround be to set up the account in DA then use your local hosts file to point the domainname at the server for testing?

[nobaloney]

Originally posted by blacknight
Our helpdesk is flooded with requests for them :(
Here's the solution, all from the DA control panel; no shell access required:

Implementing Server Aliases (http://www.directadmin.com/forum/showthread.php?s=&threadid=4908).

Jeff

[blacknight]

Originally posted by jlasman
Here's the solution, all from the DA control panel; no shell access required:

Implementing Server Aliases (http://www.directadmin.com/forum/showthread.php?s=&threadid=4908).

Jeff

That doesn't address the issue at all, as it's just a manual hack which can be easily implemented via the httpd conf additions section. It doesn't address mail either.

As other people already said the issue is that DA uses "Redirect" instead of "ServerAlias" in the httpd.conf when you add a pointer.
The pointer has the mail setup correctly so that multiple alias domains receive mail correctly.

[nobaloney]

My how-to addresses specifically exactly what Sean wrote about in the original post that started the thread, and in fact it answers your point in the fourth post (the third reply) to the thread, as well.

It also specifically answers your next post to the thread, and explains how you can set up DA so your client can test their installations before they can switch their DNS.

So, since the How-To addresses the original question that started the thread, and several of your concerns as well, what's your point?

Jeff

[blacknight]

Originally posted by jlasman
So, since the How-To addresses the original question that started the thread, and several of your concerns as well, what's your point?

My point is it only addresses the site preview type situation or the client who doesn't want mail for the other domains.

As I've already stated I cannot see why DA cannot use ServerAlias in the httpd.conf for domain pointers as this would resolve both mail and web, both for previews and live sites.

[Protollix]

Actually, I was thinking more of "parking" domains so no, it doesn't fully help, but it does help in the case when you need something up soon.

The redirect is a PITA because if a user wants say:

www.somefunkydomain.com

and also wants www.sfd.com to point to the same place, but doesn't want the domain name in the URL bar to change, he's SOL.

It would be so much easier to just copy the vhost from the main domain, with the domain name part changed but keep the homedir, etc.

Or just use a serveralias.

A redirect is just silly.

[blacknight]

Originally posted by Protollix
A redirect is just silly.

Exactly my point.

It reminds me of the RAQs!

[davidb]

let's bump this thread.. for one or two customers it is fine to have the admins do this work for utilizing serveralias.. it becomes rather support heavy when the admin is doing it for hundreds or even thousands of domains.. Honestly, is this something that would be that difficult to code into a plugin or a patch release of the code?

From a customer perspective, the redirect does not address their desire to have multiple domains display the same information. If I had the source and the the 2 hours to change the functionality and test it, I would. For now, I am considering writing some custom scripts to let my customers make this happen.

[nobaloney]

Originally posted by blacknight
It reminds me of the RAQs!
Actually RaQs don't use redirect; they do use ServerAlias.

But they also rewrite the URL.

Jeff

[blacknight]

Originally posted by jlasman
Actually RaQs don't use redirect; they do use ServerAlias.

But they also rewrite the URL.

Jeff
It has exactly the same effect which is what I was talking about.

[RealNames]

Originally posted by Protollix ........not want the URL in the address bar to change from what was originally input.

I have also asked this question too in other threads at several different forums, but never got a satisfactory reply, I think due to confusion on the issue. An example again is this thread where is apppears some are misunderstanding.

We both seem to be asking how we can use so called 'Masked Forwarding' where the address bar url does NOT change to the url of the site forwarded or domain pointered to but stays the same? That way the user thinks their is an actual website for the name without realizing it was forwarded or sent by a domain pointer to another domain.

P.S. I know some registrars like GoDaddy offers that service but want to do it myself using DA and not need to rely on the registrar. Also do not want to set up a new site, only do masked forwarding of the domain name(s).

[nobaloney]

I've already posted on how to emulate what Plesk and others call masked forwarding, in this thread (http://www.directadmin.com/forum/showthread.php?s=&threadid=3293).

That's the only way I know of doing it using DirectAdmin.

Jeff

[blacknight]

Originally posted by jlasman
I've already posted on how to emulate what Plesk and others call masked forwarding, in this thread (http://www.directadmin.com/forum/showthread.php?s=&threadid=3293).

That's the only way I know of doing it using DirectAdmin.

Jeff
That's a different concept entirely.

[davidb]

I think the point is being missed to some extent. The whole purpose of a control panel is so that the user can manage their own account. All we are really asking is for DA to change a few lines of code (surely not more than 20 or 30 total) to make this happen.

[rushost]

See here:

http://www.directadmin.com/features.php?id=460

But I think it should be not instead of pointers but as extra features
because is is 2 different options

And sometimes it should be privelege of admin (only) to modify ServerAlias in Admin Panel

[nobaloney]

Originally posted by davidb
I think the point is being missed to some extent.
I haven't missed the point at all, David. I'd welcome the feature.

But I'm not coding DirectAdmin.

So my only choice is to either stay silent or to point out how you can do it until DA staff add it.

Since I believe that's more helpful than staying silent, that's what I did.

Jeff

[blacknight]

Originally posted by jlasman
I haven't missed the point at all, David. I'd welcome the feature.

But I'm not coding DirectAdmin.

So my only choice is to either stay silent or to point out how you can do it until DA staff add it.

Since I believe that's more helpful than staying silent, that's what I did.

Jeff
Aye, I just wish the people who were coding it would read this thread :D

[blacknight]

Well I for one am now happy :)

The domain alias/pointer/insert your term here option now works the way our users want it.

[Joe Noon]

After reading this long thread, I noticed similarities in what I was seeking. I need to be able to add domain B for the purpose of email, while having an existing domain (domain A) have a ServerAlias to domain B. This way, domain B functions fully in the control panel, while the web site portion of it is actually hosted on domain A.

Here is my proposed solution, please let me know if this covers all ends:

- Add domain B as normal to directadmin
- Have the ability to comment out domain B's <VirtualHost> block through the control panel.
- Add the ServerAlias to domain B in domain A's Domain Pointer section (the new 1.233 version that uses ServerAlias)

The thought here is, if you could comment out the <VirtualHost> block on domain B, it would still function for email, ftp, etc, but its httpd configuration would be handled by domain A.

This could be done manually, but Im not sure what would happen when changes were made to directadmin (would it rewrite the httpd config thus removing the commented lines?)


Maybe Im on to something?

[blacknight]

The latest version of DA includes a domain alias option for pointers, so it's pretty much covered.

[Joe Noon]

Yes, the version update takes away the need of adding the custom ServerAlias manually.

After thinking about my above solution, I think its really much simpler: Be able to create a domain that DOESNT have web.

This way the domain can be ServerAliased elsewhere, but still function fully.

As far as Im aware of, this is not possible as of now, correct?