Thread: IP over hostnames?

When a new client signs up for hosting and their domain name isn't yet resolving, as a temporary URL/login, why are they often given the IP of the server, and not the hostname?

I find this strange for these two reasons,

1. If the IP of the server changes, the clients that haven't updated their (eg.) FTP settings since they first signed up will obviously have problems. You wouldn't have this problem with the hostname.

2. A few years down the line when the client forgets who their hosting company is, and they have the hostname from their old FTP settings, it'll help them out: server1.im-your-host.com (assuming they have their head fixed on).

I know IP's are need for some applications instead of hostnames, but surely hostnames are more useful.

Well some people use white label servers for resellers and so 2nd point isn't valid.

Also if the ip changes, then you notify any customers affected.

Giving them the IP allows them to know what to point their DNS to if they have externally hosted DNS, or if they want to edit their local hosts file, and it still gets them to the same place!

OK well I can understand it for DNS reasons and resellers, but the majority don't make DNS changes and aren't with resellers. Would have thought the hostnames gives them the extra helping out when they get lost.

Why?

They're going to remember the hostname, but not whom they're hosted with?

You're smoking some great stuff eh!

Not sure what you're saying here... If you're lost, often the clue to your web host (or ex web host) is in the hostname.

(Can't smoke, had 2 lung ops! :P )

Originally Posted by MH-Nick

Not sure what you're saying here... If you're lost, often the clue to your web host (or ex web host) is in the hostname.

(Can't smoke, had 2 lung ops! :P )

But you're saying they'll remember some obscure hostname as it's in their welcome email.. totally overlooking the fact their host will be plastered all over their welcome email.

Their host may also show up in a WHOIS..

I was simply saying of all the reasons to use a temporary hostname for the 24-48 hours it takes to move them over, 'remembering' who they bought from wouldnt be anywhere on my list.

You say that, but a host I used to work for, commonly had people asking if we hosted them (whether they found us through WHOIS, their welcome email, or looking at old configs (mail,ftp). The hosts name/website is usually in the hostname.

Also, when we moved several servers from the US to UK, we had A LOT of customers in that FTP situation, and cPanel login URLs. We even had people supplying IPs from over 5 years ago!

So they give you their domain name then?

there's a reason it's like it is, it's that your justifications suck

Originally Posted by MH-Nick

When a new client signs up for hosting and their domain name isn't yet resolving, as a temporary URL/login, why are they often given the IP of the server, and not the hostname?

I find this strange for these two reasons,

1. If the IP of the server changes, the clients that haven't updated their (eg.) FTP settings since they first signed up will obviously have problems. You wouldn't have this problem with the hostname.

2. A few years down the line when the client forgets who their hosting company is, and they have the hostname from their old FTP settings, it'll help them out: server1.im-your-host.com (assuming they have their head fixed on).

I know IP's are need for some applications instead of hostnames, but surely hostnames are more useful.

IP's can be used temporarily during dns propagation so point's 1 and 2 are not really relevant as it's only a short period of time. Once dns has updated customers can use the correct login details and as mentioned should an IP change, just communicate it to your customers.