Summary: | net-im/pidgin cannot resolve dns names after changing network settings | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Laurento Frittella (mrfree) <laurento.frittella> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://sources.redhat.com/bugzilla/show_bug.cgi?id=984 | ||
See Also: | http://sources.redhat.com/bugzilla/show_bug.cgi?id=984 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Laurento Frittella (mrfree)
2007-05-07 08:44:58 UTC
This bug is strange, do we have anything special in our libc resolver configuration? Why would only pidgin be affected though? Is the reporter running any local dns or caching services like these? dnsmasq, bind, djbdns, nscd (In reply to comment #2) > Is the reporter running any local dns or caching services like these? > dnsmasq, bind, djbdns, nscd No, I haven't any of these packages installed. nscd comes with glibc, which you do have installed. When the switch happens, is /etc/resolv.conf still valid compared to the previous one? this is a "feature" of the glibc resolver which is "solved" by using nscd see: http://sources.redhat.com/bugzilla/show_bug.cgi?id=984 http://sources.redhat.com/bugzilla/show_bug.cgi?id=3675 SuSE has a patch for this which i'll merge since i agree this is a stupid feature So you don't want the dhcp clients to do ncsd -i hosts if they cannot do res_init then? i dont understand your question |