blogger custom subdomain help

subdomain of blogger site on new server

[safin]

Guys need a bit of help to see if this is possible to do.
I run a site on blogspot with a custom url. I have the custom domain set up as per bloggers instructions here:
[help.blogger.com...]

Now i want to so something like this(an old question was asked here too: [webmasterworld.com...] )
I want to set up a subdomain on my own hosting(so obviously its not on blogspot) that will serve as an image host to the site.
What do i need to do, both at the registrars end and at my host end to set this up so that my setup looks like this

domain.com (main domain) still points to blogspot blog as its doing now

images.domain.com (the new subdomain) points to my own server(my dedicated server which hosts some other sites) and specifically to a directory where the image hosting script resides. Please note that this should be accessible via the url: images.domain.com

I am guessing that i have to set up an "A" record at the domain registrars end pointing to my image host server for the subdomain. What do i have to do at my server end, specifically at the whm level to get this to work?

thanks

[jtara]

I am guessing that i have to set up an "A" record at the domain registrars end pointing to my image host server for the subdomain.

You mean for the host images.example.com?

Please, please, please, everyone - please stop calling hosts subdomains. A subdomain is a different animal altogether, and is quite a bit more trouble to set-up.

I may sound like I am being picky, but the danger is that somebody stumbles across one of these threads and goes to the unnecessary trouble of actually setting-up a subdomain.

I'd guess that 99% of webmasters here have no need for a subdomain.

What do i have to do at my server end, specifically at the whm level to get this to work?

What is "whm"?

You will need to have a hosting plan that can host multiple domains. You will need to configure your server for virtual hosts. You need to create a virtual host for your images.example.com host. It will have it's own home directory.

Since you say you are already hosting several domains on this server, presumably you already have virtual hosting set-up, and just need to add a new host. You can probably just look at your existing configuration files and it should be fairly obvious what to do.

If you mention what web server you are using, we can probably help you with more precise details.

[safin]

You mean for the host images.example.com?

Please, please, please, everyone - please stop calling hosts subdomains. A subdomain is a different animal altogether, and is quite a bit more trouble to set-up.

ok then host. Although i used the word subdomain as it looked to me that the main domain is example.com and i am setting up a subdomain images.example.com on a different host :P point noted though :)

What is "whm"?

You will need to have a hosting plan that can host multiple domains. You will need to configure your server for virtual hosts. You need to create a virtual host for your images.example.com host. It will have it's own home directory.

webhostmanager.
while it might look fairly obvious to you, its not that obvious to me. Before this we just could set up the domain on our server by adding the domain via webhost manger and it would set things up. (server: servint vps, webhostmanger, cpanel) The only issue this time is that its not a full domain(or should i treat images.example.com as an independent domain?) and set things up like normal. Even if this is the case, since one part(example.com) is pointing to blogspot, how do i set up the(images.example.com) to point here.

Hopefully thats more clearer.

[jtara]

should i treat images.example.com as an independent domain?)

Yes. Independent host, but I'm being picky about words again.

how do i set up the(images.example.com) to point here

Simply create an A record within the domain example.com for images.example.com, pointing to your images server.

You should have 3 A records:

example.com 1.2.3.4
www.example.com 1.2.3.4
images.example.com 4.3.2.1

1.2.3.4 = your blog host
4.3.2.1 = your images host

Now, it sounds like your VPS setup may include DNS as well. (NOT a real good idea, IMO. This could be problematical but probably won't be.

One of the disadvantages of using a control panel is that they typically have one way of doing things, and it can be difficult to break out of the mold. They don't always make it easy to manually edit config files, sometimes overwriting whatever changes you have made.

Unfortunately, it's hard to give concrete advice for a specific hosting company. But, generally, you can just ignore the fact that it's creating some DNS records on your internal DNS server that you will never use. (Because you are using the registrar's DNS servers in the case of this domain - e.g. example.com.)