Comment 8 for bug 571858
Revision history for this message
| Ed S (edgar-b-dsouza) wrote Re: Gwibber does not receive twitter messages | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Great! :-) So now we know the reason for your Gwibber Twitter problem.
Well, I don't like OpenDNS either, because they redirect what should be NXDOMAIN replies to their own pages (and used to also grab my Google searches!!) so I understand your not wanting to use their DNS.
However, I now use a local installation of bind9 as my DNS - it is faster than using any DNS server on the Net - and have set Google's DNS as a forwarder (though this is not required). I have not encountered the Gwibber name lookup timeout error even once on my system, because of the local DNS. It also speeds up everything else that requires DNS on my system :) Perhaps you may want to try something like this yourself - you don't need to use OpenDNS at all.
The reason the errors come back when you remove OpenDNS may be that the timeout settings in Gwibber are too small to wait for replies from slow DNS servers... and some ISP's servers can get really slow :-(