Suzanne — Sat, 04 May 2002 04:37:29 +0000

definitely good to know there are alternatives, thank you! I'm still a little fuzzy on the details, but it's always good to know other ways to do things.

Good to know, good to know, thanks.

Mike Feury — Sat, 04 May 2002 04:03:45 +0000

Hi Suzanne,

Quote: if you have a registrar with good free services

That's a big IF.

Oh agreed for sure, but a bit of research will easily find one - eg enom.com or their resellers, plus others.

Quote: I think that's a little more difficult and likely to cause problems, isn't it?

Maybe, but would normally be an automatic part of the host setup process.

Quote: I'm not sure what the combined extra services are that a good host wouldn't also have

This isn't an issue of course if your host has all the services you want, or will want in the future.

Quote: If I put their nameservers in the DNS information, I have the same amount of control.

No, not unless your host's control panel allows you to fix any DNS issues - you can do this directly thru your Registrar's CP. I often see posts in hosting forums from customers with DNS issues, which then have to be investigated and resolved by the host techs. It's not a big deal or anything, but can save 'wear and tear'

Quote: I don't see how the host wouldn't have to know your domain name?

The host would indeed have to know your domain name.

Quote: It's a different approach

Yes, that's all it is. Your way is fine for probably 95% of people, but there may be advantages for those who like to keep on top of things and crank out every extra mile they can

Suzanne — Sat, 04 May 2002 03:11:35 +0000

Quote: Originally posted by Mike Feury
[...] if you have a registrar with good free services [URL forwarding etc][...]

That's a big IF.

Quote: Originally posted by Mike Feury
[...]That's sufficient for your site to be found. Of course, if you didn't get a dedicated IP address from your host [and you probably didn't, they're scarce], you should make sure your host updates hir server config file [httpd.conf I think] to point to your hosted domain name.

I think that's a little more difficult and likely to cause problems, isn't it?

Quote: Originally posted by Mike Feury
[...]You control the DNS yourself thru your Registrar account - no more problems with hosts having to fix anything;
You get to use the combined extra services offered by both Registrar and host.

I'm not sure what the combined extra services are that a good host wouldn't also have (email perhaps being in a place that wouldn't be interrupted with a change of hosts?), but I don't see how you gain any more control by using url redirection as opposed to entering the nameservers of the host.

When I sign up for hosting, the host has to enter information into their nameservers, regardless. If I put their nameservers in the DNS information, I have the same amount of control. When I change hosts, I go to the domain registrar and change the name servers. The host knows nothing, needs to change nothing.

It's a different approach, and thank you for clarifying there are other ways to do it, but I don't see how the host wouldn't have to know your domain name? At some point, the nameservers for the host would have to be updated? Or at least some sort of server side manipulation would have to be done?

Mike Feury — Sat, 04 May 2002 02:15:52 +0000

Quote: Originally posted by Suzanne
The nameservers have to be with the host. They are how the host knows where to point visitors. The new host will also give you a static or virtual IP. You must change everything except the actual domain name itself.

Hi Suzanne,

I don't think the above is correct.

You can leave your nameservers with your domain registrar. In fact, if you have a registrar with good free services [URL forwarding etc], you are probably better off not changing to your host's nameservers.

What you do need to do is change your domain record at the registrar by creating an (A)ddress record to point to the IP address of your site.

That's sufficient for your site to be found. Of course, if you didn't get a dedicated IP address from your host [and you probably didn't, they're scarce], you should make sure your host updates hir server config file [httpd.conf I think] to point to your hosted domain name.

There are 2 benefits to this approach:
You control the DNS yourself thru your Registrar account - no more problems with hosts having to fix anything;
You get to use the combined extra services offered by both Registrar and host.

mjames — Sat, 13 Apr 2002 13:56:27 +0000

May I recommend this incredibly useful article? http://www.webmasterbase.com/article/30

Suzanne — Sat, 13 Apr 2002 01:55:43 +0000

Oh, and yes, if you have the files on both your old host and your new host, when you change the nameservers for your domain (that is what tells the browser where to go), then no one will see a downtime.

Suzanne — Sat, 13 Apr 2002 01:54:54 +0000

The nameservers have to be with the host. They are how the host knows where to point visitors. The new host will also give you a static or virtual IP. You must change everything except the actual domain name itself.

For the domain name, you will change the namservers only.

For yourself, any references in your code that are IPs should be changed to relative or your domain name instead of IPs. And your files will have to be uploaded to the new host.

ThomasAJ — Sat, 13 Apr 2002 01:39:50 +0000

Wil

Yes I have been given a new IP by the new host.
Changing Domain Name Servers is not enough is it. I have to change the IP somewhere.

The actual name server can be anywhere can it not. I mean the NS1.a.com and NS2.a.com entries can be with the registrar and not with the host.

I don't actually take an IP address with me from one host to another do I. Or do I.

I guess I don't understand the relationships well.

Gadget Girl

So eventually when I do set it up correctly when someone goes to xyz.com they will get my site from my old host and later from my new host but I will NOT be off air.

Being off air is my concern, not how long the propagation takes.

Thanks

DC_Sara — Fri, 12 Apr 2002 21:53:23 +0000

Once you point the DNS to the new host, with your domain, it can be anywhere from 24-72 hours before it is totally propagated/resolved. *Is that how you spell propagated?*

I have a friend in the UK that tells me when I can be seen. I know that I will be able to see it the next day.

Sara

Wil — Fri, 12 Apr 2002 11:59:52 +0000

Hm. You've been given an IP address from your new host to acces your site until you change the DNS over you mean?

You need to find out your new host's DNS server names and change where your domain points to.

Thus assuming that you do have a domain name, right?