Move it, move it (a.k.a. “Screw it up the IBM way”)

I work with web sites for a living. I give them a place to live, I trash them when they’re no longer needed and I also move them. And believe me, moving a site is the trickiest of the jobs. But in all of my professional life, I’ve never ever seen a blunder like this (output shortened for brevity):

crow:~$ dig developer.lotus.com
; <<>> DiG 9.6.0-APPLE-P2 <<>> developer.lotus.com
;; QUESTION SECTION:
;developer.lotus.com.		IN	A

;; ANSWER SECTION:
developer.lotus.com.	127	IN	CNAME	192.147.106.27.
192.147.106.27.		0	IN	A	67.215.65.132

Really. Did they outsource the last thinking person in their networking department? Ok, maybe they fixed it and the change just hasn’t trickled down. So let’s try a different approach (again, shortened:)

{openx:6}
First, let’s find the name servers responsible for lotus.com

crow:~ $ dig lotus.com ns

; <<>> DiG 9.6.0-APPLE-P2 <<>> lotus.com ns
;; ANSWER SECTION:
lotus.com.		200	IN	NS	cmtu.mt.ns.els-gms.att.net.
lotus.com.		200	IN	NS	cbru.br.ns.els-gms.att.net.

;; ADDITIONAL SECTION:
cbru.br.ns.els-gms.att.net. 59899 IN	A	199.191.128.105
cmtu.mt.ns.els-gms.att.net. 59899 IN	A	12.127.16.69

And now let’s check what they’ve got to say:

crow:~$ dig @199.191.128.105 developer.lotus.com

; <<>> DiG 9.6.0-APPLE-P2 <<>> @199.191.128.105 developer.lotus.com
;; QUESTION SECTION:
;developer.lotus.com.		IN	A

;; ANSWER SECTION:
developer.lotus.com.	300	IN	CNAME	192.147.106.27.

crow:~$ dig @12.127.16.69 developer.lotus.com

; <<>> DiG 9.6.0-APPLE-P2 <<>> @12.127.16.69 developer.lotus.com
; (1 server found)
;; global options: +cmd
;; Got answer:

;; QUESTION SECTION:
;developer.lotus.com.		IN	A

;; ANSWER SECTION:
developer.lotus.com.	300	IN	CNAME	192.147.106.27.

crow:~$

Well. Close, but no cigar. So for the record, let’s check whether they can do anything right.

crow:~$ dig @12.127.16.69 www.lotus.com

; <<>> DiG 9.6.0-APPLE-P2 <<>> @12.127.16.69 www.lotus.com
;; QUESTION SECTION:
;www.lotus.com.			IN	A

;; ANSWER SECTION:
www.lotus.com.		300	IN	A	129.42.16.103
www.lotus.com.		300	IN	A	129.42.17.103
www.lotus.com.		300	IN	A	129.42.18.103
crow:~$ 

Finally. What a difference A dot makes. But you’ve got to have an I for it. Or so it says. (I hope they’ll find at least the obvious error in their setup without external help).

Update: Another day passed and it’s still not fixed. I have to agree with Jan-Piet. Un.Be.Lieve.Able.

Update II: Another day in paradise. Or whereever the folks responsible for fixing the lotus.com DNS are right now.

9 thoughts on “Move it, move it (a.k.a. “Screw it up the IBM way”)

  1. Jan-Piet Mens

    It’s not just the dot. The problem is the CNAME to an IP address which, without the dot, would resolve to a crazy 192.147.106.27.lotus.com. With the dot it sucks anyway. ;-)

  2. Stefan Rubner Post author

    That’s why there’s a capital A in that sentence with the dot ;)

  3. Pingback: Jan-Piet Mens » How to bugger up your site and keep it that way

  4. Martin Böhm

    “Did they outsource the last thinking person in their networking department?”

    You get what you pay for. Of course nobody is going to estimate the actual costs of this idiocy, and put it into proportion against employing even a half-smart network guy. My guess is you could pay a decent salary for several years.

  5. Stefan Rubner Post author

    That’s the problem with paying by LOC. There’s already a line of code present there. (scnr)

  6. Pingback: vowe dot net

  7. Pingback: Jan-Piet Mens » Doof.Nicht.Schlau

  8. Pingback: Jan-Piet Mens » 168 hours and no change: When marketing is faster than technology

Comments are closed.