From: RobertB 

In article ,
 John Beckett  wrote:

> RobertB  wrote in message
> news::
> > > That procedure will NOT work if the client sends request:
> > >   GET http://www.robert.com
> >
> > Oh, but that's what I want people to enter into their browser address
> > line.
>
> Hmmm ... I'm not sure if you digested the info that I rather carefully
> provided.
>
> Your choices are:
> 1. Use the URL that your ISP provides (bad).
> 2. Use a DNS/HTTP redirection service (works but slightly dodgy).
> 3. Use a proper web hosting service (you get one IP).

Yeah, I pretty much followed that. I assume one would use 2 in conjunction
with 1, however, unless I just wanted to use the cumbersome ISP+myname
address, which I don't.

>
> In (3), you can use any domain name that you can register. You would set
> the A record for www.robert.com to be the IP of the web site.
>
> Good: Best reliability; fast; very little can go wrong go wrong.
> Later, you can change the web service and simply change the A record for
> the new IP.
>
> Bad: Pay serious money (but my guess is less than $500/year).

There are less expensive solutions available. I'm not expecting high
traffic and it'll be a small site in terms of size.

>
> Re (2): It is just amazing how much stupid traffic is generated by systems
> these days. On one Linux FC6 system I'm playing with, whenever you resolve
> a name to an IP, it sends two DNS queries for an IPv6 address. After that
> it figures it may as well try IPv4 (just in case!). I've seen Windows do
> much morre silly things.
>
> So, I don't think the extra work of a redirection would be noticable,
> provided the network and server providing the redirection are reliable.
> For example, if it's free or under $10/year, I don't see how it could be
> reliable - hence Geo's question about whether you mind if it goes offline
> for two weeks.

Yeah, well 2 weeks is a long time in Web time.

--- BBBS/NT v4.01 Flag-5