[Bug 52744] New: resolving monopd server fails with KExtSocket

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=52744     
           Summary: resolving monopd server fails with KExtSocket
           Product: atlantik
           Version: 0.5.1
          Platform: Compiled Sources
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: [email protected]
        ReportedBy: [email protected]


Version:           0.5.1 (using KDE 3.1.0 (RC6))
Installed from:    compiled sources
Compiler:          gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-112)
OS:          Linux (i686) release 2.4.18-3smp

<Capzilla> chouimat: any reason why dns lookup is slow in kextsock->startAsyncConnect ?
<Capzilla> atlantik still resolving..
* Capzilla ponders feeding kextsock ip addresses instead of hostnames
<Capzilla> cap@kira:~$ telnet ranger.befunk.com 1234
<Capzilla> Trying 66.93.240.85...
<Capzilla> Connected to ranger.befunk.com.
<Capzilla> Escape character is '^]'.
<Capzilla> <monopd><server version="0.7.0"/><client playerid="1798" cookie="1798/324591497"/></monopd>
<Capzilla> atlantik is still resolving..
<Capzilla> ok, kextsock is crap :)
<Capzilla> Njoodle : I can reproduce your problem on some servers, it seems
<Capzilla> and it seems to hang out dns lookup
<Njoodle> I can resolve sanjose.ca.us.monopd.net on the console, but not with atlantik
<Capzilla> yes, it starts connecting, but it hangs at resolving