[Webkit-unassigned] [Bug 18455] New: DNS resolves fail in Webkit even though they work for FireFox and ping

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=18455

           Summary: DNS resolves fail in Webkit even though they work for
                    FireFox and ping
           Product: WebKit
           Version: 526+ (Nightly build)
          Platform: Macintosh PowerPC
        OS/Version: Mac OS X 10.5
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: hahn.seb at web.de


I have a domain which was newly connected, so when I first tried to visit it,
the resolve failed, I couldn't ping, just what is expected. But after a while,
ping succeeded and FireFox could access the website.

Webkit still insisted the server cannot be found, even after restarting Webkit
this didn't work.

Catfish_Man was nice and provided the command "sudo dscacheutil -flushcache"
which "fixed" the issue for me, but still this might be a larger problem? Here
is an IRC discussion about it:

<sebastian> How is it possible that webkit cannot find a URL that is pingable
and Firefox can connect to it?
<sebastian> Webkit tells me it cannot find the server
<sebastian> Does it cache DNS requests even after I close it?
<sebastian> Because it is a newly connected domain
<Catfish_Man> sebastian: sounds like it could indeed be dns caching. I've seen
issues with that before, although with Adium+MSN, not Safari
<sebastian> I wonder what I could do to reset that cache
<sebastian> "emptying the cache" doesn't do the trick
<Catfish_Man> sebastian: try sudo dscacheutil -flushcache 
<sebastian> works now
<sebastian> is this expected behaviour or a bug? I think it shouldn't cache
when the browser is closed inbetween... hm
<Catfish_Man> sebastian: the cache is at the OS level, so it doesn't know
anything about browsers
<Catfish_Man> but, I'd assume it's a bug
<sebastian> how do ping and firefox get it right, then?
<sebastian> ok
<Catfish_Man> probably by using APIs that don't use the cache
<Catfish_Man> although I don't know the details, just guessing there
<cpst> yeah I've seen this bug before
<cpst> an easy way to reproduce it is when you go between net connections
<cpst> and the first is wireless with a login screen that every name resolves
to
<cpst> sometimes it won't forget it very easily
<cpst> well, it is probably more than likely an OS bug


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.