Very Computer

> > I have a friend who has a page at xxx.tripod.com

> > she is having immense problems with NameSecure.com who now is supposed
> > to be forwarding requests from xxx.com to xxx.tripod.com

> > i run my own dns, can (and how) do I set it up to resolve requests for
> > xxx.com to xxx.tripod.com.

> It depends if xxx.tripod.com has a unique IP address, or is doing
> name-based hosting. If it is a unique address, it would be as simple
> as setting up an IN A record along the lines of

> xxx.com.    IN A  192.168.1.1

> assuming that xxx.tripod.com has an IP address of 192.168.1.1

> If xxx.tripod.com is doing name-based hosting, you have to be a bit
> more creative. The most sure-fire (albeit a bit complicated) way of
> doing this is to build a small webserver in your own IP space, point
> xxx.com to its address, then have your server re-direct all requests
> for xxx.com to xxx.tripod.com. It chews up some bandwidth and resources,
> but is (as far as I know) about the only way to pull it off. Apache
> used as your httpd for this scenario provides all this functionality,
> and will not cause serious overhead on your server if you tweak the
> configuration a bit.

> There are commercial load balancers that could probably be set up to
> do what you need, but you're talking about a pretty serious inverstment.

> > (you can ignore the INTERNIC stuff)

> I wish...

> JS

>> > I have a friend who has a page at xxx.tripod.com
>> > she is having immense problems with NameSecure.com who
>> > now is supposed to be forwarding requests from xxx.com to
>> > xxx.tripod.com
>> > i run my own dns, can (and how) do I set it up to resolve
>> > requests for xxx.com to xxx.tripod.com.
>> It depends if xxx.tripod.com has a unique IP address, or is doing
>> name-based hosting. If it is a unique address, it would be as simple
>> as setting up an IN A record along the lines of
>> xxx.com.    IN A  192.168.1.1
>> assuming that xxx.tripod.com has an IP address of 192.168.1.1
>> If xxx.tripod.com is doing name-based hosting, you have to be a bit
>> more creative. The most sure-fire (albeit a bit complicated) way of
>> doing this is to build a small webserver in your own IP space, point
>> xxx.com to its address, then have your server re-direct all requests
>> for xxx.com to xxx.tripod.com. It chews up some bandwidth and resources,
>> but is (as far as I know) about the only way to pull it off. Apache
>> used as your httpd for this scenario provides all this functionality,
>> and will not cause serious overhead on your server if you tweak the
>> configuration a bit.
>> There are commercial load balancers that could probably be set up to
>> do what you need, but you're talking about a pretty serious inverstment.
>> > (you can ignore the INTERNIC stuff)
>> I wish...
>> JS
>Thanks Bill, John:
>It looks as if tripod.com is doing name based virtual host stuff.  I was
>trying to find a way to make her site world accessable  (not just from
>here) without depending on my machine's availability by having DNS
>provided here and at the secondary sites so neither solution will do it
>- so far.

> >> > I have a friend who has a page at xxx.tripod.com

> >> > she is having immense problems with NameSecure.com who
> >> > now is supposed to be forwarding requests from xxx.com to
> >> > xxx.tripod.com

> >> > i run my own dns, can (and how) do I set it up to resolve
> >> > requests for xxx.com to xxx.tripod.com.

> >> It depends if xxx.tripod.com has a unique IP address, or is doing
> >> name-based hosting. If it is a unique address, it would be as simple
> >> as setting up an IN A record along the lines of

> >> xxx.com.    IN A  192.168.1.1

> >> assuming that xxx.tripod.com has an IP address of 192.168.1.1

> >> If xxx.tripod.com is doing name-based hosting, you have to be a bit
> >> more creative. The most sure-fire (albeit a bit complicated) way of
> >> doing this is to build a small webserver in your own IP space, point
> >> xxx.com to its address, then have your server re-direct all requests
> >> for xxx.com to xxx.tripod.com. It chews up some bandwidth and resources,
> >> but is (as far as I know) about the only way to pull it off. Apache
> >> used as your httpd for this scenario provides all this functionality,
> >> and will not cause serious overhead on your server if you tweak the
> >> configuration a bit.

> >> There are commercial load balancers that could probably be set up to
> >> do what you need, but you're talking about a pretty serious inverstment.

> >> > (you can ignore the INTERNIC stuff)

> >> I wish...

> >> JS

> >Thanks Bill, John:
> >It looks as if tripod.com is doing name based virtual host stuff.  I was
> >trying to find a way to make her site world accessable  (not just from
> >here) without depending on my machine's availability by having DNS
> >provided here and at the secondary sites so neither solution will do it
> >- so far.

> So I went and looked this up. I see tripod has 'member' sites, and
> that it is on the exodus network. How does someone access the site
> she has now? xxx.tripod.com is non-existant, and returns errors from
> lycos/tripod. . So I guess the xxx was to 'protect the innocent'.
> Make helping a bit harder too.

> I think you need to be more descriptive of your problems as
> 'immense problems' does leave quite a few possibilities.

> Defining the actual problem might have helped.  Depending on what
> the problem is, the answer could be to move from 'namesecure.com'
> who appears to be the registrar, or the move from somone other
> than 'tripod.com'.

> --