Firefox Loses DNS in F10

I've been seeing a weird problem on F10 in Firefox on a fresh install onto my daughter's machine. Frequently, after using Firefox for a bit, it seems to lose its ability to do DNS lookups. Every URL reports not found. Shutting it down and reopening solves the problem. So it's just Firefox, no

Re: Firefox Loses DNS in F10

On Mon, 2008-12-01 at 09:45 -0500, Richard Heck wrote: > I've been seeing a weird problem on F10 in Firefox on a fresh install > onto my daughter's machine. Frequently, after using Firefox for a bit, > it seems to lose its ability to do DNS lookups. Every URL reports not > found. Shutting it dow

Re: Firefox Loses DNS in F10

On Mon, 01 Dec 2008 09:45:22 -0500 Richard Heck <[EMAIL PROTECTED]> wrote: > > I've been seeing a weird problem on F10 in Firefox on a fresh install > onto my daughter's machine. Frequently, after using Firefox for a bit, > it seems to lose its ability to do DNS lookups. Every URL reports not

Re: Firefox Loses DNS in F10

Mike Chambers wrote: On Mon, 2008-12-01 at 09:45 -0500, Richard Heck wrote: I've been seeing a weird problem on F10 in Firefox on a fresh install onto my daughter's machine. Frequently, after using Firefox for a bit, it seems to lose its ability to do DNS lookups. Every URL reports not foun

Re: Firefox Loses DNS in F10

Richard Heck <[EMAIL PROTECTED]> writes: > I've been seeing a weird problem on F10 in Firefox on a fresh install > onto my daughter's machine. Frequently, after using Firefox for a bit, > it seems to lose its ability to do DNS lookups. Every URL reports not > found. Shutting it down and reopening

Re: Firefox Loses DNS in F10

Tom Horsley <[EMAIL PROTECTED]> writes: > https://bugzilla.redhat.com/show_bug.cgi?id=459756 I'm seeing lots of sites that have bind EDNS problems (in addition to simply having broken DNS servers.) queries and or sites that have records tend to require bigger packets, causing lots of h

Re: Firefox Loses DNS in F10

Patrick O'Callaghan wrote: On Mon, 2008-12-01 at 09:11 -0800, gary artim wrote: seems there is a ipv6 slowdown with comcast's dns servers. if you use firefox you can stop ipv6 lookups by opening a tab in firefox and typing: about:config type: network.dns.disableIPv6;false set it to true and

Re: Firefox Loses DNS in F10

"gary artim" <[EMAIL PROTECTED]> writes: > if you use ssh, create an alias for ssh that looks like: alias > ssh='ssh -4' in your > .bash_profile, this will force using only ipv4 dns lookups. I don't > like passing on these workarounds because you may forget what you did > when the it is fixed, but

Re: Firefox Loses DNS in F10

On Mon, 2008-12-01 at 16:31 -0500, Jim wrote: > Patrick O'Callaghan wrote: > > On Mon, 2008-12-01 at 09:11 -0800, gary artim wrote: > > > >> seems there is a ipv6 slowdown with comcast's dns servers. if you use > >> firefox > >> you can stop ipv6 lookups by opening a tab in firefox and typing: >

Re: Firefox Loses DNS in F10

Hi, On Mon, Dec 1, 2008 at 13:19, Tom Horsley <[EMAIL PROTECTED]> wrote: > On Mon, 01 Dec 2008 09:45:22 -0500 > Richard Heck <[EMAIL PROTECTED]> wrote: > > > > > I've been seeing a weird problem on F10 in Firefox on a fresh install > > onto my daughter's machine. Frequently, after using Firefox f

Re: Firefox Loses DNS in F10

Andre Costa wrote: Hi, On Mon, Dec 1, 2008 at 13:19, Tom Horsley <[EMAIL PROTECTED] > wrote: On Mon, 01 Dec 2008 09:45:22 -0500 Richard Heck <[EMAIL PROTECTED] > wrote: > > I've been seeing a weird problem on F10 in Firefox

Re: Re: Firefox Loses DNS in F10

On Mon 1/12/08 9:41 PM , Jim [EMAIL PROTECTED] sent: > <...snip...> > I would file a bug on it. > I have FC10 Firefox-3 and it does the same thing, It can't find server > to Linuxtoday.com and lxer.com, > but it will find yahoo.com, redhat.com etc. > If I get on my FC8 box and Firefox, it has no

Re: Re: Firefox Loses DNS in F10

On Mon, Dec 1, 2008 at 8:45 AM, Steve <[EMAIL PROTECTED]> wrote: > On Mon 1/12/08 9:41 PM , Jim [EMAIL PROTECTED] sent: >> <...snip...> >> I would file a bug on it. >> I have FC10 Firefox-3 and it does the same thing, It can't find server >> to Linuxtoday.com and lxer.com, >> but it will find yah

Re: Re: Firefox Loses DNS in F10

On Mon, 2008-12-01 at 09:11 -0800, gary artim wrote: > seems there is a ipv6 slowdown with comcast's dns servers. if you use > firefox > you can stop ipv6 lookups by opening a tab in firefox and typing: > > about:config > > type: > network.dns.disableIPv6;false > set it to true and your dns looku

Re: Firefox Loses DNS in F10 (also: UDP checksum errors for DNS queries)

2008/12/2 Andre Costa wrote: > Actually, is this a problem at all or can I safely ignore this? > As Wireshark suggested, this is happens the NIC calculates the checksums for the packet. Since the HW is doing this, the SW doesn't bother, hence the wrong value that appears to be in the outgoing pac

Re: Firefox Loses DNS in F10 (also: UDP checksum errors for DNS queries)

Hi, On Mon, Dec 1, 2008 at 20:51, Andre Costa <[EMAIL PROTECTED]> wrote: > Hi, > > On Mon, Dec 1, 2008 at 13:19, Tom Horsley <[EMAIL PROTECTED]> wrote: > >> On Mon, 01 Dec 2008 09:45:22 -0500 >> Richard Heck <[EMAIL PROTECTED]> wrote: >> >> > >> > I've been seeing a weird problem on F10 in Firefo

Re: Firefox Loses DNS in F10 (also: UDP checksum errors for DNS queries)

Hi Paul, On Tue, Dec 2, 2008 at 10:10, Paul Black <[EMAIL PROTECTED]<[EMAIL PROTECTED]> > wrote: > 2008/12/2 Andre Costa wrote: > >> Actually, is this a problem at all or can I safely ignore this? >> > > As Wireshark suggested, this is happens the NIC calculates the checksums > for the packet. Si

Re: Firefox Loses DNS in F10 (also: UDP checksum errors for DNS queries)

On Tue, 2008-12-02 at 15:33 -0200, Andre Costa wrote: > I bet this is why no local DNS cache can help with Google addresses > since they expire so quickly. Weird thing is that, on this short > monitoring I did (a couple of minutes only), none of the Google sites > (aside from the main sites such as

Re: Firefox Loses DNS in F10 (also: UDP checksum errors for DNS queries)

> I bet this is why no local DNS cache can help with Google addresses > since they expire so quickly. Ah, but I'm running bind (named) as a local cache and added the -4 option in /etc/sysconfig/named to make it only do IPv4, and all my problems disappeared. Seems to be the best work-around for now