On Wed, Oct 13, 2010 at 6:38 AM, daid kahl <[email protected]> wrote: >> On 10/11/2010 11:38 PM, daid kahl wrote: >> >>> However, I noticed that logins, su, and sudo are all responding >>> slowly. This was all fixed and fine once I updated my configuration >>> files, but this week it's acting up again. Before it was just su and >>> sudo that I noticed as slow (authentication takes around 20 seconds). >>> But now even logins are delayed (xdm or command line). > > On 13 October 2010 07:12, walt <[email protected]> wrote: >> >> Whenever I see something that eventually works, but only after a long >> delay, I think of DNS problems. >> >> Who might be doing a nonsensical DNS lookup, I have no idea. But you >> might consider running a packet sniffer (wireshark, etc) while logging >> in or doing an su. Are you running your own local name server? > > Very very intersting!! > > The main correlation I've seen so far is with dhcpcd. Sometimes at my > work I get a 192. IP (which doesn't work), and other times I get a > 133. IP (which is correct). In fact, sometimes dhcp is giving me an > IP address and resolv.conf related to a university I was visiting like > a month ago.
It sounds like someone at your work might be (accidentally) running a rogue DHCP server... -James
