Hi Guys
I was going to put this in the Feature Request, but I guessed that having some general discussion about it first might be an idea
Using DirectAdmin, on Apache 1.3.37 I am attempting to create a Sub-Domain (sub) for a Primary Domain (domain.com) that has a Domain Pointer (domain.net). The final goal is that the sub-domain should exist for all of the primary domain Domain Pointers (sub.domain.com -> sub.domain.net)
DirectAdmin does not currently support this. (AFAIK)
How I overcome this is by adding the sub-domain as an additional primary domain (sub.domain.com), DirectAdmin allows this (I dont know is this in fact a bug that has worked in my favour or what
)
Would it be possible for DirectAdmin, when adding a sub-domain or domain pointer, to create the relavent records so that sub.domain.net will point to sub.domain.com, or is the standing to use the work-around that I have mentioned?
To be honest, the work-around is fine for me, it gives more room to play with the sub-domain (possibility of creating unique emails for a support desk for example, and the ability to use Installatron on the sub-domain). However for new users of DA, this workaround may not be apparent.
What does everyone/anyone think?
I was going to put this in the Feature Request, but I guessed that having some general discussion about it first might be an idea
Using DirectAdmin, on Apache 1.3.37 I am attempting to create a Sub-Domain (sub) for a Primary Domain (domain.com) that has a Domain Pointer (domain.net). The final goal is that the sub-domain should exist for all of the primary domain Domain Pointers (sub.domain.com -> sub.domain.net)
DirectAdmin does not currently support this. (AFAIK)
How I overcome this is by adding the sub-domain as an additional primary domain (sub.domain.com), DirectAdmin allows this (I dont know is this in fact a bug that has worked in my favour or what
)Would it be possible for DirectAdmin, when adding a sub-domain or domain pointer, to create the relavent records so that sub.domain.net will point to sub.domain.com, or is the standing to use the work-around that I have mentioned?
To be honest, the work-around is fine for me, it gives more room to play with the sub-domain (possibility of creating unique emails for a support desk for example, and the ability to use Installatron on the sub-domain). However for new users of DA, this workaround may not be apparent.
What does everyone/anyone think?