I'd almost say, try to install the old hard drive for a bit and see if the BOINC there still works. If it does, what's different? A cc_config.xml file, perhaps?
Thinking about that, could you otherwise make a cc_config.xml file in your BOINC Data directory (where client_state.xml lives) and add into it the following:
Edit... Damn, I see you did that already.
Nope. No clue. Really nothing.
Back in the beginning -- It's simply and clearly Boinc's fault, more specifically cURL (c-ares) bug. (http://www.mail-archive.com/c-ares@cool.haxx.se/msg00527.html) Some year ago many people had that problem and I'm unfortunately recreated that in some way (I of course tried recommendation in that article -- DNS Server: 68.94.156.1, Search Domains: sbcglobal.net -- no help). I completely disabled IP6.
Summary -- 1) all other network protocols work, I can use 3 different browsers, FTP, torrent, Skype & windows RDP.
2) I completely reinstalled Boinc (6.10.58).
3) I have checked every possible settings & I have tried every approach found in internet.
4) Seems, that I would make Boinc work, when I could write every needed DNS address resolve to /etc/hosts...
The c-ares issue you reference is the one that we worked around as of BOINC 6.10.45 by reverting to the older version of c-ares. The problem with the newer c-ares is that it only tries IPv6 and does not fall back to IPv4 when the IPv6 lookup fails. Disabling IPv6 on your system would only make the problem worse.
But since you have upgraded to BOINC 6.10.58, that issue is not relevant in your case. I tried using your DNS servers (194.126.115.18, 194.126.101.34) on my Mac, and BOINC resolves the host names with no problem. By the way, according to my whois lookup, those DNS servers are registered in Estonia (!) though that does not necessarily mean the servers are actually located in that country.
So I am at a loss to understand why you are having this problem. I've asked the other BOINC developers to take a look at this thread and see what they suggest.
Disabling IPv6 on your system would only make the problem worse.
But since you have upgraded to BOINC 6.10.58, that issue is not relevant in your case. I tried using your DNS servers (194.126.115.18, 194.126.101.34) on my Mac, and BOINC resolves the host names with no problem. By the way, according to my whois lookup, those DNS servers are registered in Estonia (!) though that does not necessarily mean the servers are actually located in that country.
Yes, I guessed so much, but I can't find any solution or workaround, I know little bit about UNIX and networking, but not so deep.
And yes, I'm living in Estonia. Those servers are my service providers, Estonian Telecom's DNS servers. (But I tried also with Google DNS servers.)
I'd almost say, try to
)
I'd almost say, try to install the old hard drive for a bit and see if the BOINC there still works. If it does, what's different? A cc_config.xml file, perhaps?
Thinking about that, could you otherwise make a cc_config.xml file in your BOINC Data directory (where client_state.xml lives) and add into it the following:
Edit... Damn, I see you did that already.
Nope. No clue. Really nothing.
RE: Back in the beginning
)
The c-ares issue you reference is the one that we worked around as of BOINC 6.10.45 by reverting to the older version of c-ares. The problem with the newer c-ares is that it only tries IPv6 and does not fall back to IPv4 when the IPv6 lookup fails. Disabling IPv6 on your system would only make the problem worse.
But since you have upgraded to BOINC 6.10.58, that issue is not relevant in your case. I tried using your DNS servers (194.126.115.18, 194.126.101.34) on my Mac, and BOINC resolves the host names with no problem. By the way, according to my whois lookup, those DNS servers are registered in Estonia (!) though that does not necessarily mean the servers are actually located in that country.
So I am at a loss to understand why you are having this problem. I've asked the other BOINC developers to take a look at this thread and see what they suggest.
RE: Disabling IPv6 on your
)
Yes, I guessed so much, but I can't find any solution or workaround, I know little bit about UNIX and networking, but not so deep.
And yes, I'm living in Estonia. Those servers are my service providers, Estonian Telecom's DNS servers. (But I tried also with Google DNS servers.)