On 6-Aug-2007, at 16:31, Peter Dambier wrote:
John L wrote:
Um, unless I seriously misunderstand the client DNS cache wants to
know which server is closest. So it sends DNS queries to all
three NS at the same time. Then it waits for the answers.
Whichever one answers first is the clos
John L wrote:
Um, unless I seriously misunderstand the client DNS cache wants to know
which server is closest. So it sends DNS queries to all three NS at the
same time. Then it waits for the answers. Whichever one answers first
is the closest. What am I missing?
The bind_garbadge_col
On Mon, 6 Aug 2007, Patrick W. Gilmore wrote:
first I agree that in most cases the 'RTT to client cacheresolver'
probably works well enough. That said though...
> Owen said it worked well for his customers (in a past life), and he
> has operational experience with this. Can anyone give a ser
On Aug 6, 2007, at 1:47 PM, John L wrote:
Why would they ping rather than just sending the query to all of the
NS and see which one answers first? It's an IP round trip either
way.
If you have sites in San Fran, London, and Tokyo, and you launch a
ping from
all 3 and see which one gets t
On Aug 6, 2007, at 10:21 AM, John Levine wrote:
Sounds like one of the global-scale load balancers - when you do a
(presumably) recursive DNS lookup of one of their hosts, they'll
ping
the nameserver from several locations and see which one gets an
answer the fastest.
Why would they pin
On Mon, 6 Aug 2007, John Levine said:
Why would they ping rather than just sending the query to all of the
NS and see which one answers first? It's an IP round trip either way.
ping targets are of the caching nameserver type, not the authoritative
nameserver type.
Duane W.
On Mon, 06 Aug 2007 17:21:49 -, John Levine said:
>
> >> Sounds like one of the global-scale load balancers - when you do a
> >> (presumably) recursive DNS lookup of one of their hosts, they'll ping
> >> the nameserver from several locations and see which one gets an
> >> answer the fastest.
>
>> Sounds like one of the global-scale load balancers - when you do a
>> (presumably) recursive DNS lookup of one of their hosts, they'll ping
>> the nameserver from several locations and see which one gets an
>> answer the fastest.
Why would they ping rather than just sending the query to all of
8 matches
Mail list logo
