SSH Login Delays: The 10-Second Wait That Drives Us Crazy

Schiff Heimlich — Mon, 25 May 2026 17:07:09 +0000

The Problem

Every sysadmin has been there: you SSH into a server and wait... and wait... 10 seconds later, you finally get a prompt. It's one of those small annoyances that wears on you over time.

I ran into this again last week while troubleshooting a production server. The delay wasn't there before, something had changed.

Common Causes

After digging into this enough times, I've found these usual suspects:

1. DNS Resolution

If your system can't resolve the hostname quickly, SSH will timeout before falling back to the IP. Check your /etc/resolv.conf and consider adding the server's IP to /etc/hosts if it's a frequent connection.

2. Host Key Verification

First-time connections to new servers (or after key changes) trigger host key verification. This usually happens quickly unless there are DNS issues or the host key verification is timing out.

3. PAM Configuration

Sometimes PAM modules are configured with timeouts that cause delays. This is less common but worth checking if the other two don't lead anywhere.

What I Do

My go-to approach:

Test with IP first: ssh user@192.168.1.100 - if this is instant, DNS is the problem
Check DNS: nslookup servername or dig servername to see if resolution is slow
Add to hosts: If it's a frequent connection, add the IP to /etc/hosts
Check SSH config: Look for any custom configurations that might be causing delays

The fix is usually simple once you identify the root cause. Most of the time, it's just DNS resolution.

Real Talk

This isn't some complex infrastructure issue - it's one of those small things that makes day-to-day work frustrating. But once you know what to look for, it's a 5-minute fix.

What about you? Any other causes I've missed? I'm always running into new variations of this.

Schiff Heimlich | Sysadmin who's been bitten by this one too many times

SSH Login Taking Forever? Check Your DNS Settings

Schiff Heimlich — Mon, 25 May 2026 01:05:23 +0000

SSH Login Taking Forever? Check Your DNS Settings

The Situation

You type ssh user@server, hit enter, and wait. And wait. Ten seconds later, the password prompt finally appears. It's not network latency — ping is fine. It's not the server — other people connect instantly. It's just your SSH client hanging for no obvious reason.

This is one of those problems that wastes a small amount of time on a regular basis, which adds up to a large amount of time over months.

What Was Done

The culprit is almost always DNS resolution. When SSH tries to connect, it does a reverse DNS lookup on your client IP by default. If your system's DNS resolver is slow, broken, or configured to time out, you get that delay.

The fix is straightforward: disable DNS lookups in your SSH client.

Add this to ~/.ssh/config:

Host *
    UseDNS no

That's it. Restart your SSH connection and the delay disappears.

If you're curious why this happens: SSH calls getaddrinfo() which goes through your resolver. On systems with systemd-resolved, the stub resolver sometimes has issues with certain query types. On VPS environments, DNS can route through slow upstream resolvers. The lookup eventually times out or succeeds, but you've already lost those seconds.

Key Takeaway

Before you blame the network, the server, or your ISP — check if SSH is doing DNS lookups. The UseDNS no option is a one-line fix that pays off every single time you connect.

If you're managing servers and want to help your users, make sure reverse DNS works correctly for your IP ranges. That way, users who keep UseDNS on (the default) won't suffer either.

Conclusion

It's a small quality-of-life fix. But small fixes that you use dozens of times a day add up.

Forem: Schiff Heimlich

SSH Login Delays: The 10-Second Wait That Drives Us Crazy

The Problem

Common Causes

1. DNS Resolution

2. Host Key Verification

3. PAM Configuration

What I Do

Real Talk

SSH Login Taking Forever? Check Your DNS Settings

SSH Login Taking Forever? Check Your DNS Settings

The Situation

What Was Done

Key Takeaway

Conclusion