ATTBI just changed DNS servers

[John Abreau]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Content-Type: text/plain; charset=us-ascii


> Probably true.  But you can do a  lot  better  if  you  use
> non-random nameservers.
> 
> The problem is finding them.  I've  never  found  a  better
> approach  than asking friends and then testing the response
> times.   It  seems  like  there  should   be   a   way   to
> systematically   search   your   network  neighborhood  for
> nameservers and pick a few that work well.

The thng about nameservers is that *everything* depends heavily 
on them. The nameservers are the biggest factor affecting your 
perceived response time for every interactive use you make of the 
Internet. 

Even if the external server you choose is highly responsive, the 
latency of the DNS lookup going out through your cable or dsl modem
(or worse, your 56K dialup modem) is a bottleneck. While I can't speak
for everyone, I find the latency very noticeable, especially for 
web access.

Running a nameserver internally gives you much better perceived 
response time. There's no real maintenance involved, either, 
once it's set up. I've had mine running for about a year and a 
half, and the only times I've had to touch it were to add new 
machines to my local domain or new zones to mask banner-ad domains.


- --
John Abreau / Executive Director, Boston Linux & Unix
ICQ 28611923 / AIM abreauj / JABBER jabr at jabber.org / YAHOO abreauj
Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9
PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iQCVAwUBPcw6iVV9A5rVx7XZAQIHuAQApY55Pj0X9fzOYyW1XRaGXtwvDS3Z3ONm
Jc0gZdnbBK2pqArvLk7+XpH10r0DUa/HY9VPIOzHg0CzZanHkpzxYMGc02hyfITM
FVMRWCDtoKd8ubOTpqr2wvJwapgXVzPjIOzp7Frja1D3OSDceDmR3srOn6Fievzs
B06TCeeqdEU=
=cTSu
-----END PGP SIGNATURE-----