I read a few posts which seemed unrelated except to mention the peculiarities with 1&1’s system.

My solution: try, try again. …which worked.

Updating DNS settings can be stressful. As soon as my domain resolves to the new server I breathe a huge sigh of relief. I figure the problem happened because this week’s updates were important to me.

This morning I had only one domain left to update, so I tried again, 1&1 served an error message, I tried again, error, tried again and it worked – all within less than a minute. [other attempts didn't work for hours but "try, try again" worked for each, eventually.]

I’ve used 1&1 webhosting for many years now and have quite a load of domains with them. Granted they have their own backend software which is unusual relative to a plesk or cpanel interface but all in all I haven’t experienced too many delays, problems or lack of response.

In 2008, I moved my hosting accounts from 1&1 to Hostgator.com for added features at the same cost. Hostgator allows wildcard DNS for WordpressMu sites.