maybe a dumb idea on how to fix the dns problems i don't know....

Sun Aug 10 22:36:26 UTC 2008

list-nanog at pwns.ms wrote:
>> But we only care about TCP connection setup time in *interactive* 
>> sessions (a human using something like the web). If you have a 
>> persistent connection to your dns server from your dns resolver on your 
>> browser machine, you just send the  request.... no TCP setup there at 
>> all. You can even pool connections. We do this stuff in LDAP all the time.
>>     
>
> Again, if we can change the DNS protocol, then it's easy to solve.

Wait a min... This isn't changing the DNS protocol to have or allow
persistent dns/tcp connections is it? or is it?

Yikes, yes the DNS protocol should be changed then, right now, to allow 
persistent connections, at least from the interactive client (websurfing 
machine) resolver to caching name server.

CP
-- 
Chris Paul
Rex Consulting, Inc
157 Rainbow Drive #5703, Livingston, TX 77399-1057
email: chris.paul at rexconsulting.net
web: http://www.rexconsulting.net
phone, direct: +1, 831.706.4211
phone, toll-free: +1, 888.403.8996

The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of,
or taking of any action in reliance upon, this information by persons
or entities other than the intended recipient is prohibited.
Rex Consulting, Inc. is a California Corporation.

P Please don't print this e-mail, unless you really need to.