Herald, I can't think of anything rather than the way the said browsers communicate with the dns. Since they all keep printing "waiting for..." There shouldn't be anything in the kernel, because nothing else seems to be affected.
Recently I also noticed that I am not seeing the issue when I am on the ethernet connection. From time to time it may also be working OK when on wireless with ath5k driver - go figure. If it is the driver issue, it is still very strange to me.
Herald, I can't think of anything rather than the way the said browsers communicate with the dns. Since they all keep printing "waiting for..." There shouldn't be anything in the kernel, because nothing else seems to be affected.
Recently I also noticed that I am not seeing the issue when I am on the ethernet connection. From time to time it may also be working OK when on wireless with ath5k driver - go figure. If it is the driver issue, it is still very strange to me.