Multiple same-aliased hosts. Attn: Barry M

[Barry Margolin]

In article <_USo4.23679$3b6.98073 at ozemail.com.au>,
Glen Jarret <gjarret at tyndale.apana.org.au> wrote:
>Hi Barry,
>
>Thanks once again. I shall take the plunge and see what happens (which will
>be measured by the (nocturnally batched) resolved names of visitors).
>
>> As an inexpensive solution, I think your plan may work.  The only caveat
>is
>> that your assumption that clients will always use the closest DNS server
>> may not be as valid as you expect.
>
>Surely their ISP will run its own DNS and use the nearest upstream DNS as
>its secondary? Expense is not a consideration, my client is a multi-national
>travel group. I suffer from hereditary perfectionism and want to minimise
>the gap between clicking and rendering of the page.

My point was that the ISP's caching servers don't know which of your
DNS servers are closest to them.  Over time they get a history of response
times and choose the best ones, but when they start out they'll pick one of
your servers at random, so it may not be the closest one.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.