Seems the likes of MCHOST do not give you I.P addresses to each of the accounts you set up for clients.

On the whole, do clients want their own I.P and is being able to offer this a plus side for resellers?

And if there is not I.P address, how does a client upload and access their account while their domain name is in the DNS change process?

you don't :bawling:

The only reason you'd want a dedicated IP is to have your own virtual anonymous FTP server and/or SSL. A client can upload and access their account through their shared IP address, and they can access their site at http://yourdomain.ext/~theirusername/

Unless you actually need a dedicated IP address (like a secure server) name based hosting works fine.

As far as waiting until the DNS resolves, there are several ways to get around this. You can create some rewrite rules so they can get at the site (a lot of people with RaQ's do that). You can change the DNS or hosts file on the local machine to point at your DNS/your ip.

Just some thoughts.

Frank

That's the biggest drawback of going non-IP. You have to wait until the DNS propagation takes over.

Does anyone know of a way around that? I know it seems there isn't a way, but wondered if anyone else knew.

Originally posted by pgrote
Does anyone know of a way around that? I know it seems there isn't a way, but wondered if anyone else knew.

It's a pain to do (because most end users don't know how to d this) but is very simple.

On my NT box, I just put an entry in the local hosts file (windows\system32\drivers\etc\hosts) for the new server.

Then go ahead and browse way. Just remember to delete the entry once DNS is updated.

I used this last week. My IP's changed, but they were still cached on my ISP.

Frank

Originally posted by Ben ozric
Seems the likes of MCHOST do not give you I.P addresses to each of the accounts you set up for clients.

On the whole, do clients want their own I.P and is being able to offer this a plus side for resellers?

[SNIP]

Some companies can offer IP-based accounts for the accounts created by their resellers. Price will be around $1 per IP per month.

We find most of our clients want their own IPs. IP-based accounts can make bandwidth tracking easier. But I guess it is some kind of reassurance that they can FTP into their space the instant their sign-up is setup.

Originally posted by voxtreme - philip
But I guess it is some kind of reassurance that they can FTP into their space the instant their sign-up is setup.

We just find it easier all round to offer a dedicated IP address, especially during signup. Just send out their login details along with an IP address saying to use this till the domain resolves. To date I can't remember anyone ever having an issue with it.

Makes it very easy to get an automated personalized index page with a login link up and running too :D

Greg Moore

Originally posted by akashik


We just find it easier all round to offer a dedicated IP address, especially during signup. Just send out their login details along with an IP address saying to use this till the domain resolves. To date I can't remember anyone ever having an issue with it.

Makes it very easy to get an automated personalized index page with a login link up and running too :D

Greg Moore

What a waste... Its because of people like this that it is getting harder and harder to obtain IP's :(

We now make it optional, rather than standard for new customer on our higher plans to choose IP's rather than automatically be assigned one. I think it is quite selfish to just give them away like halloween candy.

Originally posted by voxtreme - philip
But I guess it is some kind of reassurance that they can FTP into their space the instant their sign-up is setup.

You can perfectly FTP into your website even if you don't have a dedicated IP address.

Originally posted by Haze


What a waste... Its because of people like this that it is getting harder and harder to obtain IP's :(

We now make it optional, rather than standard for new customer on our higher plans to choose IP's rather than automatically be assigned one. I think it is quite selfish to just give them away like halloween candy.

The European rule for assigning IPs works but is sometimes too restrictive.....maybe something in-between the free-for-all and the european method is the best way forward

Yep, I never understood why every site wants their own IP. Name based hosting works fine. As long as accounts are setup correctly, you can ftp in with no problem.

Yes, it is a very short tem problem as the name server update/proprogate, but that just does not seem like a real good reason to use up the very limited supply of IP addresses.

I know of a lot of hosts that do it just so they can more easily track the transfer by IP. There just has to be a better way.

Frank

It is really not that difficult to make shared IP hosting work. I know we simply create a subdomain in the form of username.servername.atlantawebhost.net. It works quite well and we have not had any customers who have issue with the system. It is going to be neccesary to update the protocols so that a unique IP is not needed for each website even for SSL.

Best regards,
Frank Rietta

Originally posted by AtlantaWebhost.com
It is really not that difficult to make shared IP hosting work. I know we simply create a subdomain in the form of username.servername.atlantawebhost.net. It works quite well and we have not had any customers who have issue with the system. It is going to be neccesary to update the protocols so that a unique IP is not needed for each website even for SSL.

Best regards,
Frank Rietta

We do the same thing, HSphere creates a stop-gap domain that is a subdomain of the server name (or anyother domain we want for that matter) that customers can use to view there site.

Even CPanel makes it so customers can view their site without the DNS resolving - however if the site uses absolute paths for images, included scripts etc. then it won't work so well.

It'll be a long time before they get round SSL not needing it's own IP due to the way that the standard works and the fact that all browsers need to be replaced then.

By far the simplest thing to do is take advantage of mod_userdir and let them access their account using the syntax http://11.22.33.44/~username. The Apache docs are really helpful in setting this up.

CPanel uses mod_userdir - the only thing about that is that it doesn't work when you want multiple domains on one useraccount or if you want to test subdomains out.