On Tue, Feb 08, 2000 at 12:38:20PM +0100, Glynn Clements wrote:
> This won't help if most of your accesses come from a few networks
> where all of the clients use the same caching DNS servers.
I was wondering about this so I quickly did a test:
---------
[hq:~]$ for i in . . . . . . . . . . . . .; do ping -c 1 www.altavista.com | grep
PING; done
PING altavista.com (204.152.190.71): 56 data bytes
PING altavista.com (204.152.190.11): 56 data bytes
PING altavista.com (204.152.190.21): 56 data bytes
PING altavista.com (209.162.76.5): 56 data bytes
PING altavista.com (204.152.190.63): 56 data bytes
PING altavista.com (204.152.190.70): 56 data bytes
PING altavista.com (204.152.190.63): 56 data bytes
PING altavista.com (204.152.190.60): 56 data bytes
PING altavista.com (204.152.190.70): 56 data bytes
PING altavista.com (204.152.190.62): 56 data bytes
PING altavista.com (209.162.76.5): 56 data bytes
PING altavista.com (204.152.190.14): 56 data bytes
PING altavista.com (204.152.190.63): 56 data bytes
----------
So it appears that the caching DNS server also randomizes.
--
------------------
Sarel Botha
[EMAIL PROTECTED]
------------------
99 little bugs in the code, 99 bugs in the code,
fix one bug, compile it again...
101 little bugs in the code....
-====---====---====---====---====---====---====---====---====---====---====-
to unsubscribe email "unsubscribe linux-admin" to [EMAIL PROTECTED]
See the linux-admin FAQ: http://www.kalug.lug.net/linux-admin-FAQ/
