Troubleshooting

|


Recently I was reading a post from a developer who writes about his troubleshooting experience. In his post he writes that he was trying to change fonts in his website but the change didn’t take effect. After working for several hours, he decided to call it a day and revisit the problem again the next day. When he checked the next day, the problem was solved on its own. So what happened?

Recently, I was troubleshooting on a domain DNS MX record editing for an email setup, it was not working. I couldn’t figure out what was going on. The MX value setting was looked at by two tech support staff but the problem still existed. Then I decided to call it a day and went to bed with it to revisit the problem next morning.

I suddenly woke up in the middle of the night (which I normally don’t do) and watched a couple of troubleshooting video tutorials on MX record editing, then I noticed one small typo error in the MX record field. After the typo correction error, I tested with MXTools and noticed that it was correctly pointing to the email server. Then I went back to bed hoping that it would solve the problem. Indeed, it did!

Yet another troubleshooting experience!