maybe a dumb idea on how to fix the dns problems i don't know....
chris.paul at rexconsulting.net
Sun Aug 10 16:52:58 CDT 2008
list-nanog at pwns.ms wrote:
>> (I know; you old folks that created this wonderful thing didn't think of
>> that back then.... blah blah blah).
> If they had thought of it back then, they would have allowed for a larger TXID, not used TCP. TCP connection setup time is slow; TCP DNS is much slower than UDP DNS.
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.
How does TCP resolution work in most resolver libraries? A TCP
connection for each lookup? That is kind of dumb isn't it, speaking of
dumb.... I actually don't know. Not much of a coder, so I'll let you
coders check your code and get back to me on that...
well.. maybe i'll fire up snort or wireshark and check it out later with
some different dns libs....
Rex Consulting, Inc
157 Rainbow Drive #5703, Livingston, TX 77399-1057
email: chris.paul at 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.
More information about the NANOG