Maxim Cournoyer <maxim.courno...@gmail.com> writes: > l...@gnu.org (Ludovic Courtès) writes: > >> Maxim Cournoyer <maxim.courno...@gmail.com> skribis: >> >>> I've noticed the same (lack of DNS resolution) following a reboot for >>> some minutes and was also wondering what was causing this. I'm using >>> wicd as part of the %desktop-services, so that specific problem is >>> probably not related to NetworkManager. >> >> Our default nscd config caches lookup failures for 20 seconds by default >> (see ‘nscd-cache’ in the manual.) So if you look up a host before >> networking is up, and it fails, then there’s a window during which >> lookup will keep failing. >> >> I don’t know if that explains what you’re seeing. > > It can take much longer than 20 s upon a reboot to have the name > resolution working again (more than 5 minutes), so that doesn't seem to > explain it by itself.
Most of the time I have to restart my applications like icecat of emacs when my network settings change. I'm using wpa_supplicant and dhclient by hand rather than wicd. Something somewhere is caching network information longer than it should be.
