jump to navigation

Preventing Future DNS Problems November 12, 2009

Posted by ismywebsite in general.

Any complex system that accepts dynamic input is subject to the possibility of wrong output. Any precautions would be to prevent the occurance, and improve the resolution.


  • Once this situation is resolved, build the solution into the system, so that any future cases are not subject to human error.
  • Not use the commercial control panel for DNS modifications.


  • Create an alert to be generated anytime to DNS regeneration has resulted in an error. It would mail me automatically with all applicable details. I would immediately know what and where the problem is.
  • Keep a log of the DNS launch sequence, which can be loaded among detection of the error, and contains full details.
  • Store DNS entries in alphanumeric order instead of by ID number. This will make it faster to find the problem zone among the thousands of entries that are currently active.

In 9 days, we mark the first anniversary of the most successful system implemented throughout our 3 year history. For many of our clients, this will be the first time they have ever experienced something like this.

On the plus side, I did get to meet quite a few of our clients today for the first time. I’d really like to thank everyone who took the time to let me know their little tidbit of information. That was all quite helpful to put together the full picture of what was going on, and I hope everyone will continue to provide feedback all the time, and not just when things go horribly wrong.



No comments yet — be the first.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: