Biondo wrote:This worked for me!
...
Sorry, Sunrise if I almost ignored your advice, but I usually don't do something I don't understand. When Téquila shows the reason behind that and says it's safe to forget about the added line, for me it's a good reason to try.
Well, I said it's safe to forget as I understood you needed such sentence to do the step
I wouldn't have say that without your complain
Btw it's really safe to forget until the ip changes and you still using the current binary. New binary will only use smokin-guns.org domain and we will be able to forget that lethal effect
So yes, we need a new release...Btw, Biondo, can you confirm if you can connect to my servers with that hosts file line disabled ?
This question because I only believe the
smokin-guns.net reason is only a side effect of something else. The fact is related to the following message on the console:
- Code: Select all
Resolving update.smokin-guns.net
Sys_StringToSockaddr: Error resolving update.smokin-guns.net: No address
associated with hostname
Couldn't resolve address
The DNS resolution takes too much time and so your initial server challenge may have been forgotten during the elapsed time. If your problem doesn't exist with my server, we could think the challenge is kept until your client manages to connect. If you still have problems, then you may better have a problem in the DNS resolution...
To check the DNS resolution, guys, can you report the time it tooks ? Under linux, you can try "time host update.smokin-guns.net" and "time host update.smokin-guns.org". Here are my results:
- Code: Select all
[tequila@smokinguns ~]$ time host update.smokin-guns.net
;; connection timed out; trying next origin
Host update.smokin-guns.net not found: 3(NXDOMAIN)
real 0m13.751s
user 0m0.010s
sys 0m0.019s
[tequila@smokinguns ~]$ time host update.smokin-guns.org
update.smokin-guns.org has address 91.121.39.115
real 0m3.138s
user 0m0.003s
sys 0m0.010s
So, 13 seconds for the .net and 3 seconds for the .org ...
Generally speaking, DNS resolution problems are sometime the last stuff to check but this is often critical not only for playing Smokin'Guns...
@Mope: np, but I'm also the guy to blame as I enabled in the code the "update server requests" to a sucking server with missing DNS record... Btw I blame Joe Kari to have release 1.1 without fixing the hard-coded update server DNS definition...
Generally speaking I also blame DNS resolution as this is often a problem for my job...
Edited: 13s & 3s !!! This sucks and this tells me I have problems with my own DNS resolution... I upgraded my system to Fedora 18 recently and now I discover I'm another DNS resolution victim