Re: FoRK Help.

Joe Touch (touch@ISI.EDU)
Mon, 14 Jun 1999 14:18:05 -0700 (PDT)

> From Mon Jun 14 14:03:16 1999
> Date: Mon, 14 Jun 1999 13:54:07 -0700
> To: Tim Byars <>,
> From: David Crook <>
> Subject: Re: FoRK Help.
> I don't think that its a apache issue, its a DNS one. When you set up a
> domain record, say for, you can specify different IP addresses for
> and for if you want to, but nobody does this because it
> cause a lot of confusion.

Lots of places do it - many do not have a,
or reserve as a mail relay only. Lots of
other places do it - even a quick check yields the following:

~ same?
toyota Y Y no
coke Y Y yes
ford N Y (no)
gm N Y (no)
pepsi N Y (no)
jvc N Y (no)
sony Y Y no

This is a survey of things in my office, or that I can see
out my window. Not positive proof, but sufficient to
refute the claim, I think. :-)

> So the easiest approach is just to map them to
> the same IP so that people can type "" or
> "" and both will go to your website.

Nope - easy as far as websites isn't easy as far as FTP, or
other sites. Keeping the addresses separate helps partition
traffic without requiring nasty snooping routers.

> An alternative strategy would be to tell the webserver to redirect requests
> from "" to "".

That requires running a webserver on, so it can
respond to connections and do the redirection.

> One last little bit thrown into the picture is that new browsers have a
> feature that will automatically try to resolve "" when
> someone types "" into the URL/Address line. But normally it will
> try to access "" first.

This is likely the primary problem. E.g., for,
It did try to access first. When that failed, it

> So to answer your question, that someone is correct. If you really wanted
> to be a annoying SOB you can define and to point to
> totally different IP addresses, these could represent two web servers
> running on the same computer or two two different computers. The one catch
> here is that if the computer listed at is down, your browser might
> try the server as an alternative. This behavior isn't
> specified by any RFC, but some do it anyways.

This is not happening in the DNS; it's outside the scope
of the DNS to retry with prefixes. The DNS does the right
thing - try it....