680484 - ssh to 'people' from SF office suffers 25s delay, needs reverse-DNS?

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: NetOps, task)

Description

[Brian Warner [:warner :bwarner]]

When I slogin to people.mozilla.com from the new San Francisco office,
there's a long delay before I get to the actual shell. The same is true for
other operations over ssh, like git pushes to a personal repository, or
'scp'.

It smells like the usual reverse-DNS-lookup-timing-out problem that sshd
suffers when it tries to log a name for the connection's source address. When
I connect, my source IP is 173.247.198.2, and indeed 'people' cannot find a
reverse lookup for that address:
  
  76:warner@Brian-Warners-MacBook-Pro% time ssh people whoami
  bwarner
  
  real    0m25.387s
  user    0m0.009s
  sys     0m0.006s
  77:warner@Brian-Warners-MacBook-Pro% slogin people
  Last login: Thu Aug 18 18:34:04 2011 from 173.247.198.2
  [bwarner@dm-peep01 ~]$ host 173.247.198.2
  ;; connection timed out; no servers could be reached
  [bwarner@dm-peep01 ~]$ 

I'm guessing the new connection that we switched over to doesn't have
reverse-DNS set up yet.. could we get them to add an entry for our
outwards-facing IP?

Comment 1

[matthew zeier [:mrz]]

Webpass is missing DNS for the netblock allocated to San Francisco.  I put in a hack on people but stuffing the address into /etc/hosts.  That'll fix the delay to people.

I've asked netops to get webpass to fix.

Comment 2

[matthew zeier [:mrz]]

All done:

mrz-air11:~ mrz$ host 173.247.198.2
2.198.247.173.in-addr.arpa domain name pointer 2.198.247.173.mozilla-sfo1.web-pass.com.