Paychex Can’t Set up DNS Correctly
Tuesday, July 21st, 2009
Major company can’t get domain names to resolve without www.
Last week I went to payroll processor Paychex’s web site, typing Paychex.com into my internet browser. After a few seconds I got an error message “Network Timeout. The server at paychex.com is taking too long to respond.”
The problem? I didn’t type in www. before the domain name, and the company hasn’t set up its servers and DNS correctly to handle this. It’s a simple thing and only takes five minutes. But by not setting it up correctly, customers think the web site is down. For a transaction oriented web site such as PayChex, this is a major no-no.
I sent a message to Paychex via Twitter and received a response that it would “pass that suggestion to our web department”.
Thanks, but calling it a “suggestion” is the wrong term. Someone on the web team should have fixed this yesterday. Pick up the phone, call the CTO, and get him to fix it. It’s still not fixed at the time I’m writing this.
Do you know of other major web sites that haven’t set up their servers/DNS to resolve correctly?
















