I went to MacWorld this year and attended a session called “Lucid Systems Administration“. It was a pretty good, though basic, overview of how to maintain sanity as a SysAdmin. A lot of it was pretty common sense stuff – use an organizer, don’t try to memorize everything, devote time to specific goals, prioritize, etc.
I say “common sense” knowing that there are a lot of people in my profession for whom “common sense” is elusive. They’re on “the spectrum,” the saying goes.
So I could see it being helpful for some of them…Lots of them, actually.
One thing that stuck with me was her final “tip”: Check DNS.
For any readers who don’t know what DNS is, it’s the service that translates human-readable domain names (like google.com) to machine readable (number) addresses. It’s easily one of the most critical pieces of the internet. When it fails, nothing works.
So, because it’s so critical, there are a few pieces of it that are designed to provide speed and reliability.
But when you’re troubleshooting DNS problems, those pieces become a huge headache. Primarily the one where changes don’t show up immediately. Sometimes they don’t show up for days. Literally. Fixing a problem is really frustrating when you don’t know if the change you just made has had any effect until the next day.
You know when you’re on an old computer or a slow connection and the text doesn’t show up until a second or two after you’ve typed it? Imagine that delay is 24 hours.
So instead of making a change, and immediately checking to see if it worked, you read and plan and re-read and come up with a plan B, and then consult some experts, and then make the change. Then you wait a day, see if it worked, and start reading again.
I’m not an expert on DNS, but I might be soon if this keeps up.