The TechSurgeons web & email server will be moved to our new facility March 9th, starting at 11PM Arizona time. Client sites will not be impacted by this move – just * sites and services.

Estimated downtime is 4 hours. Status will be updated as we can at and on Facebook.

If the email server move goes well, we may update the web servers and reboot them. Estimated downtime is 10 minutes each, and would affect client sites.

All the details:

We’ve been dissatisfied with the Phoenix facility we’ve colocated our servers at for a while. The original company we chose had been acquired, and the new company has not been performing. Which is why we’d been putting almost everyone on servers at our Quebec facility. (Which we still like for sites where most traffic goes to the UK/Europe.)

On October 7th, we started moving into our new Phoenix facility with all new servers. Since then, we’ve migrated over 350 sites from the old facility to the new Phoenix one, and an additional 100ish sites from Quebec.

All of these migrations have been done one at a time, by hand, completely behind the scenes to minimize any impact on you or your site’s visitors. While incredibly time consuming, it was more successful than we expected, with only a few sites having issues. (Early on, we kinda overloaded the network connection on a couple servers, and had to bump them from a gigabit connection to a ten gigabit connection.)

One of the advantages of the new facility is that we can add additional ISPs for network redundancy. Almost all sites now have multiple “phone numbers” split between two providers – “multi-homed” in geek speak. If someone tries to connect to a site on one, and it’s not working right, browsers are smart enough to try the second.
This has worked amazingly well, but confuses some monitoring tools (sorry Pingdom) which don’t know how to deal with “multi-homed” sites.

Now that all the production web sites have been moved, we’re down to the stuff that can’t be moved without downtime.

The primary goal for Thursday’s maintenance window is of our original infrastructure server. It’s been 711 days since that server has last been rebooted. That’s been too long, but we had a bad experience last time, and are wary of rebooting it unless we’re physically there. The poor thing has been a little flaky the last couple weeks, but we’ve been keeping it going until Thursday.

This server is responsible for:


We will start the shutdown process at 11PM. It will take about 30 minutes to shut the server down and disassemble it. Then 30 minutes to drive it to the new facility. Once we get it there, figure 45 minutes to reassemble and mount it. And then something between 15 minutes and 2 hours for it to come back up.

Yes, we’ll drive carefully, have a fresh backup of the server, and have extra hardware on hand in case the server doesn’t come back up correctly. Those should mitigate the worst case scenarios. (In a future maintenance window, we’ll upgrade the server itself.)

During the downtime, mail destined for us should just queue up. The email protocol says that sending mail servers should retry sending mail for at least 3 days.

If the mail server move goes well, there’s some other maintenance we’d like to do, but nothing is as urgent.

Please understand that we won’t be very reachable during this time. We’ll put up a status page at the soon to be created, and try to post updates on FB to keep folk informed.

Wish us luck!


Hi all,

We’ve updated all hosted sites with the NextGen Gallery plugin installed to the latest version. There was a significant security hole in older versions, which would have allowed an attacker to retrieve info from the site’s database.

More here:




Howdy all,

The latest update to Yoast SEO will break sites running on PHP 7.0 – our default version. We’ve (hopefully) disabled updates for that plugin by changing permissions on the folder to “read-only”.  As soon as we hear of a fix, we’ll change its permissions back, so it can be updated.




This is the first in a series of posts designed to help explain how computers and the Internet work in plain English. This series was inspired by our friend Mercedes M. Yardley.

Have you ever wondered how your web browser can find a website like Google automatically?

You can’t just key a name into your phone if they’re not a contact, your TV won’t find the latest episode of “Bones” automatically. (Yes, your Tivo/DVR might but they’re computers too.) How can your computer do it?

The answer is a near-magical background service called “DNS” (Domain Name Service). Its purpose is to save you from having to remember that is really That number is called an “IP address.” (I’ll explain IP Addresses fully in a future post.)

So DNS is a Rolodex for keeping track of computers. Yes, sometimes us computer geeks do make things easier for everyone.

When DNS is broken, you’ll see an error similar to this:

DNS is elegantly simple in how it works.

Every domain (,, etc.) declares a few servers that definitively know the names and numbers for all the computers that belong to that domain. These are “authoritative name servers”. An authoritative name server can handle DNS for many domains.

A bunch of large Internet companies manage special servers to keep track of every domain and their respective authoritative name servers. These are “root name servers”.

For each root name server, there are thousands of authoritative name servers. Imagine the root name servers as the point of a pyramid and the authoritative name servers as the pyramid’s base.

That’s pretty much how the server side works. On to the client (your!) side.

Your ISP (usually your phone or cable company) manages servers for their clients to use for doing DNS lookups. Don’t worry, it’s a lot of trouble to try and track what sites you visit. Yes, your router (that device that connects your computers to the internet) might also run a DNS lookup server and if so, it would go between Steps 2 and 3 below.

Let’s go over what happens when you enter the name of a web site in your browser.

Step 1) You enter “” into your web browser.
Step 2) Your browser asks your computer if it knows our IP address. If so, you’re off and surfing.
Step 3) If not, your computer asks your ISP if they know it.
Step 4) If not, the ISP’s name server asks any root name server the name of our authoritative name server. It then gets the info from our authoritative name server and answers your computer’s query. In case you ask again, your ISP will save the info for a while.

So instead of everyone needing ginormous servers to keep track of every device on the Internet, this system allows for lots of little servers to pass each other only the information needed. The only big servers needed are the root name servers.

So what do you think, was that sufficiently educational without being too confusing? Your feedback will guide the depth of these articles.

And if there is anything you’d like us to write about, let us know.


I was talking with my friend Mercedes M. Yardley a few days ago about all the spam she receives and when I asked if her ISP used any tools to block some of it, she didn’t know and said that “computer talk is Greek to me”.

Now she’s a brilliant author that could master Greek Geek speak if she wanted. Really, she already knows a lot about technology. However, she really liked it when I offered to “translate Geek speak” for her instead of trying to make her learn the tech terms.

Our conversation helped me put to words exactly how I want everyone at TechSurgeons to act with our less-technically inclined clients. For those that want to learn more about technology, we’ll teach. For those that don’t, we’ll translate!

So we’re going to start “DeGreekifying” technology with a series of articles and want to hear what mysteries you’d like us to “translate”.


PS. As of the time of this post, the word “DeGreekifying” returns exactly zero results on Google. I look forward to its inevitable inclusion in the dictionary.

Welcome to the new Techsurgeons Site


Thanks for taking the time to visit us. After helping many of our customers implement websites of their own, we figured that we should redo our archaic site.  The new site is pretty basic.  We’re using WordPress with the wonderful Thesis theme.  We chose WordPress and Thesis because we needed a simple solution, we’re far […]

Read the full article →