> > > I've been watching the discussions recently regarding IP and IPless hosting. > > > While I think name based hosting is nice, I don't like the idea that I > > > cannot access my sites by their IPs if something happens to my DNS records. > > > Plus it give our clients immediate access to their sites even if the DNS > > > records haven't propagated yet. > > > > You actually dont need that on a Cobalt: If you give your client the IP under > > which the site is hosted, the http://.../siteamin will put them to the right > > spot to start setting up the site, as well as ftp, telnet, ssh and so on. 3h > > later the DNS should have anyway propagated. > > Don't want to burst any bubbles here, but DNS propogation is a > non-issue. As soon as you enter the records and restart your nameserver > (that's what happens when you press the button <smile>), your new domain > becomes available everywhere on the Internet. Propogation is only an > issue with changes to old domains. Except it the "non-resolved" status is cached already on one of the name servers. That can happen if your client browsed there before the update of the DNS. (Sorry to beat further this dead horse...)
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature