Re: DNS Isuue

From: John Smith (jsmith_at_macroshaft.com)
Date: 12/16/04 

Date: Thu, 16 Dec 2004 00:21:42 -0500

i found a work around for my issue..it looks like firefox/mozilla are
first attempting to resolve ipv6 addresses, which timeout most of the
time. to disable this BUG (NOT FEATURE), in either of those browsers,
type "about:config" in the url bar, and set to value true
'network.disable.ipv6' or something like that...
now if i can figure out the same work aroudn for downloading thru ports...

On Wed, 15 Dec 2004 21:35:35 -0500, John Smith wrote:

> this sounds similar to some things i've been seeing as well. I recently
> installed openbsd 3.6 w/ pf as a home based firewall... (on a comcast
> cable modem)...it seems to take FOREVER to resolve lookups.. i have not
> really investigated it fully since it is only a firewall.. I also
> recently installed Freebsd on my primary pc, it too acts very strangely w/
> dns queries...
> on both my openbsd and freebsd computers, when i install from ports, it
> seems to hang a long time before the downloads begin. w/ openbsd, lynx
> seems to hang forever as well.
> w/ my freebsd computer, at home opera web browser is the only one that
> responds right away (as opposed to mozilla, or firefox)..at work - all web
> browsers work equally fast. nslookups on either one seem fast though.
> also, at home, my windows (2003) server still is just fine w/ IE .
> i think the 512byte size thing sounds promising...
> have you heard anything else about this?
>
>
>
> On Wed, 15 Dec 2004 09:04:06 +0000, Keith Matthews wrote:
>
>> I'm having trouble with the DNS setup on a new installation.
>>
>> It answers queries for the root name servers correctly, likewise zones for
>> which it is the master, but other zones typically get a 'no servers could
>> be reached'.
>>
>> This is on 3.6 (but a repackaged version following application of patches 1
>> to 6). PF is in use but has the same rules as orginal issue 3.6 hosts that
>> work normally. named.conf in the duff setup is indentical to that for one
>> of the ones that work (apart from the zone file names, checked with diff).
>>
>> suggestions on comp.protocols.tcp-ip.domains included
>>
>> " Your firewall is blocking EDNS responsed that exceed 512 bytes.
>>         You don't have IPv6 connectivity.
>>
>>         AAAA records were recently added for A.GTLD-SERVERS.NET and
>>         B.GTLD-SERVERS.NET.  This caused EDNS referrals to the COM/NET
>>         servers to exceed 512 bytes.  It highlighted a bug in named.
>>
>>         Named recovers from both of these but not before applications
>>         time out.
>>
>>         If the firewall is blocking the EDNS responses you won't get
>>         a answer to the first query but you will to the second."
>>
>> niether of which seem very likely on 3.6.
>>
>> Anyone got any clues ?

Relevant Pages