On Mon 1/12/08 9:41 PM , Jim mickeyboa@sbcglobal.net 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 problems of finding those same Servers.
Just adding a "me-too" here, like mike I assumed it was something on my end (didn't bother investigating).
Jim could you please send over the bz number so that we may all pitch in with information ?
thanks, - steve
-- Linux Centric Marketplace: http://www.tuxcompatible.com
On Mon, Dec 1, 2008 at 8:45 AM, Steve steve@lonetwin.net wrote:
On Mon 1/12/08 9:41 PM , Jim mickeyboa@sbcglobal.net 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 problems of finding those same Servers.
Just adding a "me-too" here, like mike I assumed it was something on my end (didn't bother investigating).
Jim could you please send over the bz number so that we may all pitch in with information ?
thanks,
- steve
-- Linux Centric Marketplace: http://www.tuxcompatible.com
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
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 lookups will take off.
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 maybe log it somewhere so you can undo when this is fixed.
-- Gary
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 lookups will take off.
Interestingly, my FF has this set to True already, and I'm sure I never touched it.
poc
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 your dns lookups will take off.
Interestingly, my FF has this set to True already, and I'm sure I never touched it.
poc
THANK YOU, THANK YOU, THANK YOU, THANK YOU. Patrick O'Callaghan
That change in Firefox about:config did it. I have pulling my brains out since last Tue. over that frustration.
Poc, I don't think we can trust you to get into ABOUT:CONFIG
THANK YOU.
"gary artim" gartim@gmail.com 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 maybe log it somewhere so you can undo when this is fixed.
You can always pass around the fix to do a "yum install bind". ;-)
There really isn't a good reason to use someone else's broken nameserver.
-wolfgang
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:
about:config
type: network.dns.disableIPv6;false set it to true and your dns lookups will take off.
Interestingly, my FF has this set to True already, and I'm sure I never touched it.
poc
THANK YOU, THANK YOU, THANK YOU, THANK YOU. Patrick O'Callaghan
That change in Firefox about:config did it. I have pulling my brains out since last Tue. over that frustration.
Poc, I don't think we can trust you to get into ABOUT:CONFIG
Huh?
poc