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 18.104.22.168, 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 22.214.171.124 [bwarner@dm-peep01 ~]$ host 126.96.36.199 ;; 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?
Assignee: server-ops → network-operations
Component: Server Operations → Server Operations: Netops
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.
All done: mrz-air11:~ mrz$ host 188.8.131.52 184.108.40.206.in-addr.arpa domain name pointer 220.127.116.11.mozilla-sfo1.web-pass.com.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.