Neat trick - adding aliases to subdomains

[antic]

Hi. I've been battling with this for a week now but finally got one over on old HPhere.

I added a subdomain to my main domain - sub.domain.com

I wanted to create an alias for the main domain, and also I wanted an alias of the subdomain, as follows:

domain.com
sub.domain.com

with aliases:

alias.com
sub.alias.com

Now HSphere let me create the domain alias, but when I went to create "sub.alias.com" it said "domain already taken" - meaning I couldn't add the subdomain alias because "alias.com" already existed as an alias for the main domain name.

So I fiddled around with CNAMEs and such, with the good help of the MR support guys, but to no avail.

Then I tried deleting the main alias first, THEN adding the subdomain alias, THEN re-adding the main domain alias:

Deleted "alias.com"
Added "sub.alias.com" - it now let me do this of course.
Re-Added "alias.com"

It added "alias.com" successfully, even though "sub.alias.com" already existed.

They both work sweeeet now. If I want to add another subdomain alias, I just need to delete and then re-add the main domain alias so it doesn't chuck a sad.

Hope this helps anyone else who has wanted to achieve the same thing!

Or you could just setup CNAME records under alias.com that point sub.alias.com to sub.domain.com... One step rather than 3

[antic]

Like I said I tried that, which was the first support suggestion. It didn't seem to work properly, which is why I tried it this way.

[Brangwyn]

Did you leave things long enough to propagate with the CNAME ?

[soky]

Originally posted by Brangwyn
Did you leave things long enough to propagate with the CNAME ?

That has been my mistake... I have been wanting instant gratification and have learned to be patient when dealing with domain names. It takes a while.

Documentation is the key!

I have learned to keep notes, try something, write it down + a plan for next action then give it a day to settle. This is helping in more ways than one... it helps me more clearly understand how the name server works and my frustration levels lower (along with my blood pressure) exponentially.

Another advantage has been, once I document what I did that worked, I have a record so I don't have to repeat the same ts steps. One key area that I have learned is new domains... I have learned to create the domain and use the instant access URL if I just gotta hang something out there now... by morning everything seems to be working (including email).

Hsphere is a good tool, (sep for the Windows NTFS user issue that is driving me batty) and once played with it for a while, it is quite manageable.

[antic]

Sounds like a new FAQ in the making there soky! I seriously can't find much that's useful in the current FAQ.

[soky]

Originally posted by antic
Sounds like a new FAQ in the making there soky! I seriously can't find much that's useful in the current FAQ.

For managing aliases, subs, root domains and the methods to the madness... I agree.

Yo, admin... if you were to say offer a dedicated windows system with @mail and terminal access... I might want to barter with you.

(Should I hold my breath? --- well... was worth a try. {insert blue smiley here} )

Frankly, I think Matrix's time would be better spend ironing out the frame issues with the new trouble ticket system It seems very useful if configured a little more.

If I had my rathers' all Matrix resources would be dedicated to solving the windows permissions issues... but hey, that's just me.

[jmbeach]

sadly, Matrix does not control HSphere, it's PSoft you have to pounce on there.

If they did control HSphere, I'd bet things would get done more quickly, and perhaps in a more open source kinda way, so that we could all help in its improvment.

[antic]

What are the windows permission issues? Is this something I (as a newbie) should be aware of to avoid particular probs?

[jmbeach]

subFTP, password protecting directories - I'm guessing he meant both of those.

I don't think it was meant as a security issue, just user access permissions. No need to worry

[soky]

Originally posted by jmbeach
sadly, Matrix does not control HSphere, it's PSoft you have to pounce on there.

If they did control HSphere, I'd bet things would get done more quickly, and perhaps in a more open source kinda way, so that we could all help in its improvment.

I agree... in my short time with Matrix I have been most pleased with their willingness to assist and flexibility. The limitations I have identified have been with the producers of the supporting software ie: H-Sphere(Psoft) and @Mail.

BTW Mr. Beach... well done on the securing a page solution!


(unrelated)
I did have a thought regarding someone's issue with @Mail attachment sizes... does the Matrix license cover collocated boxes? If so: I wonder if one could lease a box for custom @Mail??? I just hate to see people loose accounts.

[jmbeach]

Thanks - ASP 101 stuff that most users need at some time or another. Granted it's not as easy as a protected directory, it's an easy enough way to get the job done in a pinch.

(re: unrelated)
I doubt they'd be able to colo a box for any of us that ties in with the existing @Mail. I think they only colo users who have completely independent servers that are unattached from the HSphere cluster.

Would be a great solution, though. A bit pricey just to get email (I think that's why they were still hoping to find a shared environment without the size limitations), but a good idea nonetheless.