DNS lookup in FC2 still slow.

Ben Vitale bsvitale at comcast.net
Thu Aug 5 15:40:44 UTC 2004


David Cary Hart wrote:

>On Wed, 2004-08-04 at 11:25, Jack Bowling wrote:
>  
>
>>On Tue, Aug 03, 2004 at 08:14:25PM -0400, Ben Vitale wrote:
>><snip >
>>    
>>
>>>Without any changes to kernel 2.6.6-1.435.2.3,
>>>
>>>[bvitale at vandelay ~]$ cat /proc/sys/net/ipv4/tcp_ecn
>>>0
>>>[bvitale at vandelay ~]$
>>>
>>>
>>>[bvitale at vandelay ~/ecncheck]$ ecncheck 68.48.0.6 53
>>>With ECN:    Connection accepted by ns02.rtchrd01.md.comcast.net 
>>>[68.48.0.6] at hop #7
>>>Without ECN: Connection accepted by ns02.rtchrd01.md.comcast.net 
>>>[68.48.0.6] at hop #7
>>>WARNING: Host doesn't support ECN but fails gracefully
>>>[bvitale at vandelay ~/ecncheck]$
>>>
>>>Not sure how to interpret that?
>>>
>>>      
>>>
>By some chance are you using conntrack? 
>
>
>  
>
I don't believe I am using conntrack - not even sure what that is.

At this point, I am inclined to think that I just didn't notice this 
occasional DNS slowdown when I was on FC1, and then when the hype about 
IPv6-related problems showed up in FC2, I noticed that I had similar 
problems.

Comcast probably just sucks every now and then.

Ben





More information about the users mailing list